Replies: 6 comments 1 reply
|
I'm not sure what you mean? I think this is mostly representing tool outputs no? |
|
ok. currently claude code can press UP and DOWN to switch between background |
|
You can find MPC/ACP workers which can help you to run bash scripts in ACP repos by default. I set optional file system tuning switch, and other elements logic to @stdiobus/workers-registry. It woks well. |
|
I believe v2 has a much better answer for this |
|
There are two different cases here. In ACP v1, a client-managed terminal can already keep running while the agent does other work. The terminal ID from terminal/create is what terminal/output and terminal/wait_for_exit use. That does not give an ACP client a portable handle for a background task created internally by Claude Code or another agent. V1 terminals The v2 path Ben mentioned is easier to see in the Background Work RFD. It describes reporting background work separately from foreground state and advertising whether individual items are cancellable. An idle session is not proof that background work finished, and the RFD is not proof a specific adapter implements it. For the UI question, I would show client-owned terminals in a switchable list in v1 and only add native background tasks when the adapter exposes reliable IDs and status for them. I maintain Open Agent API, and the same distinction matters for our gateway: a caller-facing run ID, an ACP terminal ID, and an agent-native task ID are not interchangeable. |


Uh oh!
There was an error while loading. Please reload this page.
recent claude code has background Bash/Task support,
using BashOutput to get background bash output,
using TaskOutput to get background task output(I believe).
Does acp supports background Bash/Task,
it seemed current acp only has foreground bash?
All reactions