ACP mode: fork, session resume, and model config gaps #2202
rawizhere
started this conversation in
Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I maintain bb-plugin-prime-agent-acp, a plugin for bb (an IDE for agent threads) that runs the
prime-agentbinary as an ACP provider. The integration is in decent shape: subagents, goal state, compaction, refinements and autonomous counters all come through_metaand render natively in bb's UI.What doesn't work is the other direction. bb's provider bridge sends standard ACP requests that the ACP mode has no handler for, and there's nothing I can do about it client-side, since the agent is the one that has to answer. Three of these block features I'd like to ship:
Fork. Forking a thread in bb issues
session/fork {sessionId, cwd, mcpServers}and fails withdoes not advertise session/fork support. ACP mode doesn't advertisesessionCapabilities.forkand has no handler, and I couldn't find any PR for it. Open PR #1389 already adds a daemon command that copies a slice of the conversation into a new session file without touching the original, which is probably the backend an ACPsession/forkhandler needs.Resume.
loadSession: falseand nosession/load, so every restarted thread starts with blank in-agent history. PR #1600 fixed exactly this (the description mentions bb threads), and PR #1116 went further withsession/liston top oflistSavedSessions(). Both closed without review.Model picking.
session/newreturns only asessionId, so bb shows an empty model picker and hides reasoning selection. PR #2105 added selectors tosession/newplussession/set_config_optionwithconfig_option_updatenotifications. The agent side already hasgetModelCatalog(),setModel()andsetThinkingLevel(); they just aren't exposed.Smaller things:
available_commands_updateis never sent, so slash commands and skills are invisible to ACP clients (formerly #1306 / #1308). Context usage already has an open discussion (#1356) and a complete implementation in PR #1351 — is that one still planned?As far as I can tell, all of this only needs code in
modes/acp/.fork,switchSession,getModelCatalogand friends already exist on the daemon connection. I get why the PR queue got closed, and I'm not asking anyone to reopen old PRs. Just asking whether any of this is of interest. If something lands I'm happy to test it against a real client build.All reactions