Repository navigation
Description
Problem
The README's Harness Support table sends GitHub Copilot CLI through the escape hatch: "copilot --acp --stdio reaches ai-buddy this way today and earns a named row once smoked (#457)". #457 closed with Grok, Codex and OpenCode named and Copilot still unsmoked, and nothing tracks it since. A user who types copilot --acp into Custom gets no row, no Settings option, no Connect button, and no evidence anyone has run it.
What a named row is
What #971 gave Goose. One value, copilot, that every surface understands:
harness::launchmapscopilotto its argv, andnamed_loginandnot_installedcarry its sign-in line and install hint.HARNESS_PRESETSlists it, so Settings offersHarness · copilotand the two disclosures naming standalone CLIs include it.- Chat's connect landing has a branded button,
DISPLAY_NAMESandinstallUrlForknow it. - The README names it in the launch table, the tools table and the session table, and the escape-hatch row stops naming it.
docs/DEVELOPMENT.md'sAI_BUDDY_HARNESSrow lists it.- The two Settings fixtures are regenerated from the comparison test's dump.
What the smoke has to establish
ADR-0022 sets the bar at a turn smoked fresh and resumed, through AI_BUDDY_HARNESS=copilot scripts/probe-harness.sh. The row states each of these from the run, not from the vendor's docs:
- A fresh session ends in
end_turn. - Whether
initializeadvertisesloadSession, and whether a second run reports the same session id.cursor-agentadvertises none and every attach is fresh; the row says which this is. - What
initializeadvertises:mcpCapabilities.http,authMethods, and the rest the session table records. - Whether ai-buddy's MCP reaches the session. The stock probe serves no endpoint (fix(verify): probe-harness serves no MCP endpoint, so every tool claim it made is untested #984), so this needs a local run that does, the way the Goose tools row was measured. If it cannot be established the row says so instead of guessing.
- What tools it keeps under the attach, for the tools table.
The argv is checked against copilot --help before it is trusted; --stdio is not in the help text.
— Claude Code agent, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsDone
Activity
omesser commentedon Sep 25, 2026
The smoke, copilot 1.0.88 at
/opt/homebrew/bin/copilot, macOS 25.6,origin/mainate5ac66b7. Three runs ofAI_BUDDY_HARNESS="copilot --acp" scripts/probe-harness.sh, in this order. The first two are the stock probe; the third is a local run patched to servemcp_httpand log every method it receives, the same instrument the Goose tools row came from. Nothing from that patch is committed.The argv
copilot --helplists--acp("Start as Agent Client Protocol server") and does not list--stdio. Bothcopilot --acpandcopilot --acp --stdioansweredinitializewith the same body, so the preset iscopilot --acp.Run 1, fresh session, exit 0
Run 2, resumed session, exit 0
Same session id as run 1, read back from
probe/harness-session.json.Run 3, patched to serve MCP, exit 0
MCPREQlines are the patchedmcp_http::handlenaming each method Copilot sent. Theproposal: noat the end is expected: this run's prompt asks for a tool list, not a Behavior.What that establishes
end_turnloadSession, resumed sessiontrue; run 2 reuseda51b9ded…and ended inend_turninitializemcpCapabilities.httpandsseboth true; one auth method,copilot-login, a terminal command (copilot login);promptCapabilities.imageandembeddedContext;sessionCapabilities.closeandlistserver/discover,initializeandtools/liston the served endpoint and listed all seven ai-buddy tools under anai-buddy-prefix. No call into a tool was made, so this confirms delivery of the list, not a call.bash,read_bash,stop_bash,list_bash,view,create,edit,grep,glob,web_fetch,search_code_subagent,skill,sql,session_store_sql,read_agent,list_agents,write_agent,task,parallel, fivegithub-mcp-server-*tools from its bundled server. No web-search tool, no ask-user tool.Not established: whether a running Copilot session re-reads
~/.copilot/mcp-config.jsonafter acopilot mcp add, and nospeakthrough the Settings-generated registration has been drawn in a bubble.copilot mcp add --transport http … --header "Authorization: Bearer …",getandremovewere run against the CLI directly; a secondaddof a held name exits 1 with "already exists", which is why the generated snippet removes first.— Claude Code agent, on @omesser's behalf.
omesser commentedon Sep 25, 2026
Marks for the rows that lack one, measured against Simple Icons' 3470 slugs:
piexists and is the right product (sourcehttps://pi.dev/favicon.svg), so the README row now carries it. No OpenAI, xAI, Grok, Block or Goose mark exists there; the near matches (OpenAI Gym, ngrok, Mongoose) are other products.codex,grokandgoosewould each need a self-hosted SVG underdocs/readme/likenous.svg, with the vendor's licence carried in the tree. Not done in #1017.— Claude Code agent, on @omesser's behalf.
omesser commentedon Sep 25, 2026
Shipped on
mainvia #1017 (merge52a4442).What landed: named
copilotpreset (copilot --acp), Settings option and disclosures, Chat connect button, BYOcopilot mcp remove/addarm, README launch/tools/session rows (escape-hatch row no longer names it), ADR-0022 Copilot sentence as history, DEVELOPMENT.mdAI_BUDDY_HARNESSlist. Smoke evidence (fresh, resumed, HTTP MCP tool list) is on this issue.Still out of scope here, recorded as standing rather than open work: BYO registration is config generated, unverified (no
speakthrough the Settings snippet yet); mark gaps forcodex/grok/gooseare #1021.— Cursor agent (Coder), on @omesser's behalf.