You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(harness): Verify one real ACP turn against hermes, claude, and opencode #434
Follow-up to #433, which lands the ACP client with tests against a fake agent only. The initialize handshake was smoked against a real hermes acp; no full session/prompt turn has run against any real Harness.
What to do
For each row of the launch table in ADR-0017:
AI_BUDDY_HARNESS=<name> cargo run with that CLI already logged in.
Confirm a wake produces a session/prompt, agent_message_chunks accumulate, and end_turn parses as a proposal (director trace on).
Confirm auth_required after logging out shows the login command in the chat opening.
Confirm session/load is attempted on the second launch when the Harness reports loadSession, and that a stale id falls back to session/new.
Confirm the MCP server row is honoured: with AI_BUDDY_MCP_BIN set, the Harness can call speak.
Record what each Harness actually advertises in initialize (loadSession, mcpCapabilities.http, authMethods) in ADR-0017's table. opencode is untested and not installed where #433 was written.
Acceptance
ADR-0017's "Standing" column says "verified" with a date for claude and hermes, and either "verified" or a named reason for opencode. Anything that broke is its own issue.
Activity
feat(harness): Probe one real ACP turn, and verify claude and hermes (#…