ACP: let clients select the session agent
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the ACP handlers for session/new, session/load, session/resume, and session/set_config_option, then trace the existing agent-switch path and how model and safety selections are persisted. Done means clients can discover and select a team agent across those session operations, with the selection retained on load/resume; the optional docker agent serve acp flag is a separate consideration.
Written by the indexing model from the issue text.
Description
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
agentselect option (team agents with their descriptions) insession/new/load/resume. - Handle it in
session/set_config_optionvia the agent-switch code path, and persist it like the model and safety selections. - Optionally, add
--agent <name>todocker agent serve acp.
Related issues
#4445, #4391, #2576
docker-agent v1.144.0.
- Dominant language
- Go
- Stars
- 3.4k
- Forks
- 466
- Avg merge
- 7h 1m
- Merged PRs (30d)
- 332
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docker-agent
-
area/docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
docker/docker-agent#4054 ·
Maintainers usually reply within 1 day
-
area/testing
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
docker/docker-agent#4052 ·
Maintainers usually reply within 1 day
-
area/tools
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
docker/docker-agent#3933 ·
Maintainers usually reply within 1 day
-
area/tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
docker/docker-agent#3929 · 2 comments ·
Maintainers usually reply within 1 day
-
area/config area/docs area/security
Difficulty 4/5 3-5 days Newbie friendliness 58/100
docker/docker-agent#4476 · 1 comment ·
Maintainers usually reply within 1 day
All issues in docker/docker-agent
Similar issues
-
Remove CAAPFOpenkind/chore kind/cleanup needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rancher/turtles#2848 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low 🌱 type: enhancement 💅🏼
Difficulty 2/5 Half a day Newbie friendliness 84/100
nebari-dev/llm-serving-pack#199 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kedacore/keda#8225 · 1 comment ·
Maintainers usually reply within 1 day