Understand the code your agents write.

#184

Keep agent questions alive across disconnects

·Updated 8 minutes ago

Before

The website can enqueue a question while every author device is offline. Session transcripts stay on the machine that created them.

After

Exactly one connected device owns a question at a time, and a lost device returns its work after 45 seconds without losing the thread.

Questions asked from a change page now wait for the author’s coding agent instead of assuming that machine is online. A short lease lets any connected author device claim the work, while the original coding session remains the source of context.

3 changed files
Mconvex/agentQuestions.ts
2+38−7

Turns a best-effort queue into a leased handoff. Questions arrive with their session, a device claims one atomically, and expired claims become available again.

Mpackages/protocol/src/project-anchor.ts
+25−3

Makes anchor movement conservative. Exact blobs win; otherwise rename and surrounding-context candidates are scored, with close matches surfaced as ambiguous instead of silently attached to the wrong line.

Msrc/components/agent-question-status.tsx
+28−7

Shows which device is answering and turns a stale lease into a Reconnecting state instead of an empty row. The pill reads the lease the queue already stores, so it needs no extra query.