[alari76]

Slice 1 of docs/JOE-REPO-COLLABORATION-MAINTENANCE-SPEC.md (§2–§5). Stacked on #698.

Talking to Joe in a repo session

• A leading @Joe, or the composer's Ask Joe action, addresses Joe. The composer shows "To Agent Joe — the coding agent won't see this" before you send.
• The request is recorded in the session transcript as "You → Agent Joe" and reaches Joe as a durable Session Request. It carries the repo, branch, request id, recent conversation and linked tasks.
• Joe answers in place with reply_in_session. Joe's exchanges never go to the coding agent.
• If Joe has no harness yet, the session says so ("choose one in Tasks") instead of failing silently.

Tasks, provenance and milestones

• Tasks record originSessionId / originRequestId.
• Milestones are posted back to the originating conversation as task cards: accepted, decision needed, blocked, ready for review.
• Cards read the live task, so a decision answered in chat or in Tasks resolves in both places. Stale answers still get a 409. Only the newest card for a task shows controls.
• New execution substate: running / queued / idle. A start request or an answer shows as Queued until an attempt is actually running.

Execution ownership

• Sessions have a revisioned controller (user / joe).
• The user can hand a session over to Joe. Joe can take over only with the requestId of an explicit @joe request in that session.
• Take back control bumps the revision. Joe's send_to_session with an older revision is refused. send_to_child / resume_child also refuse once the user has taken a child back.
• While Joe controls a session, a "Supervised by Agent Joe · Task: …" banner shows and ordinary messages pause (@joe still works).

Navigation

• The sidebar's Agent Joe chat entry is now Tasks, with the attention badge and a pulse when Joe waits on an approval.
• Tasks has a per-repo overview, sections for decisions / review / running / queued / to do / closed, New task, and first-run harness setup. There is no chat composer.
• Joe's transcript remains a read-only activity log (/joe), with its approval prompts and harness/model/permission settings.
• Joe's instructions are template v11, with a new "Working in Repo Sessions" section.

Verification

• New tests: bridge (requests, replies, milestones, handover fencing), task substate, InputBar addressing/lock, chat task cards, @Joe parsing.
• Full suite: 210 files / 4012 tests pass. Lint and tsc -b are clean.
• Ran an isolated instance (separate HOME, port 32399) in headless Chromium:
  • Tasks view and sidebar entry render.
  • @Joe shows the recipient chip and posts attributed messages.
  • Acting as Joe over REST: reply, task card with decision, and handover banner render.
  • Answering the decision from chat cleared the badge, and Tasks showed the task as Queued.
  • Server refused Joe taking back control, and refused a stale-revision instruction.

Not browser-tested against a live Joe process: the isolated instance had no signed-in harness.

🤖 Generated with Claude Code