← Handoff

Agent interface · v1

Browser for humans. API for agents.

The Agent plans which phases benefit from optional user testing. Agent Pass completes and locks the phase. Users can respond naturally in chat; the Agent records only explicit passed, skipped, or issue feedback.

Handoff transport rule

Agents must read and update Handoff through direct terminal HTTP or the CLI—not Chrome, browser, computer-use, or browser automation. Browser tools remain available when the user's actual project needs inspection or testing.

CLI

npx afterqr-handoff connect https://afterqr.com/a/<token>
npx afterqr-handoff read
npx afterqr-handoff initialize project-map.json
npx afterqr-handoff init-complete
npx afterqr-handoff phase <phase-id>
npx afterqr-handoff context ON_DEMAND
npx afterqr-handoff push handoff.json
npx afterqr-handoff pass
npx afterqr-handoff user-test <passed|skipped|issue> --phase <phase-id> [compact-note]

REST

GET/api/v1/contextInitialization or compact Work Mode
GET/api/v1/bootstrapExplicit audited Initial Memory read
POST/api/v1/initializationSave Phase Map and optional user-test plan
POST/api/v1/initialization/completeComplete one-time initialization
GET/api/v1/phases/:phaseIdRead one phase detail
GET/api/v1/contextsRead an explicit context scope
POST/api/v1/handoffsAppend a versioned handoff; only goal + completed are required
POST/api/v1/phase/passAgent Pass; automatically PASS + lock
POST/api/v1/phase/user-testRecord explicit user feedback from chat

Secret safety

Never submit .env contents, access tokens, passwords, private keys, cookies or database credentials. The server scans nested data before persistence and again before Agent Pass locks a phase.