Overview
ACP sessions always start with the default agent (root, or the first agent). Please let clients pick the agent, e.g. via an agent config option next to mode, model, and thought_level from #4445.
Motivation
Today the only ways to reach another agent over ACP are agent-switch commands (#4391), one per target agent, or a separate config file per entry agent. Neither shows the agents in the client UI, and a command switch is lost on cold session/load/session/resume.
Proposed solution
- Advertise an
agent select option (team agents with their descriptions) in session/new/load/resume.
- Handle it in
session/set_config_option via the agent-switch code path, and persist it like the model and safety selections.
- Optionally, add
--agent <name> to docker agent serve acp.
Related issues
#4445, #4391, #2576
docker-agent v1.144.0.
Overview
ACP sessions always start with the default agent (
root, or the first agent). Please let clients pick the agent, e.g. via anagentconfig option next tomode,model, andthought_levelfrom #4445.Motivation
Today the only ways to reach another agent over ACP are agent-switch commands (#4391), one per target agent, or a separate config file per entry agent. Neither shows the agents in the client UI, and a command switch is lost on cold
session/load/session/resume.Proposed solution
agentselect option (team agents with their descriptions) insession/new/load/resume.session/set_config_optionvia the agent-switch code path, and persist it like the model and safety selections.--agent <name>todocker agent serve acp.Related issues
#4445, #4391, #2576
docker-agent v1.144.0.