ForkMesh is being built in the same place it is meant to support: in public, across mirrors, with work moving between people and coding agents. This round has touched nearly every layer of that loop, from walking into the virtual Office to reviewing a pull request and handing a bounded task to a headless node.
Making the World feel continuous
The most visible work has been physical. The walkway and Office lobby now meet at one level, the doorway collider no longer leaves a hidden ledge, and entering the building does not wait for organization access to load. Team-floor authorization continues in the background while the person keeps moving.
We also tightened the less obvious transitions. Mobile movement no longer triggers a refresh, audio follows the sound button, compatible scene changes apply without reloading, and changes that genuinely require a new runtime ask before refreshing. The Office attendance board now uses bounded live heartbeats, expires abandoned visits, and shows the floor of each active occupant instead of treating an interrupted checkout as permanent presence.
Bringing repository work closer to the mirror
ForkMesh already separates coordination from repository custody. The current work pushes that model further: when a source-of-truth node is offline, an eligible online mirror can materialize a signed issue immediately and sync it back later. The repository header is also gaining a complete mirror view with endpoint, health, integrity, last-check, and capability details.
Pull-request review is becoming more familiar without giving up portability. The page now has distinct conversation, commits, checks, and files sections; a changed-files rail; persistent viewed state; read progress that follows scrolling; approval; and an owner-only path to merge into an eligible mirror for later source synchronization.
Agents that belong to the organization
The next agent layer is deliberately organization-scoped. Members will be able to start Claude Code or Codex sessions on eligible headless mirrors, see those sessions in the repository's Agents list, and send revisions or follow-up prompts. Each submitted prompt first passes a fast, structured intent check and fails closed if that check is unavailable or rejects it.
The World will make those sessions legible too. Claude and Codex will appear as moving bot presences and respond when mentioned in an authorized chat. When Codex completes a tracked task, its avatar will walk to the public task board and move that note into Done, tying the visible project state to the same audited completion event.
Operational details still count
Small operational fixes compound. Status histories now use consistent cell heights, non-green component emails include a bounded two-minute Cloudflare log tail when separately scoped credentials are available, taskboard controls remain readable in every theme, and completed or deleted work no longer clutters the live bulletin.
That combination—smooth local interaction, signed portable work, explicit mirror state, bounded automation, and visible progress—is the product direction. We will keep publishing these build notes as each piece lands.