Repository navigation
Custom commands with agents should(?) change to the agent session. #3329
Description
Description
Currently, when a custom command with a primary agent is executed, the session is not changed, which prevents further interactive conversations with it, unless the user manually changes to the agent configured in the command.
This behavior has been described in #3222 and #2315
OpenCode version
No response
Steps to reproduce
- Create an agent named
myagentwith:
mode: primary
- Create a custom command:
command: mycmd
agent: myagent
subtask: false
- Trigger the command with
/mycmd - Observe the session has not changed to
myagent
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Oct 21, 2025
This issue might be a duplicate of existing issues. Please check:
subtaskparameterFeel free to ignore if none of these address your specific case.
rekram1-node commentedon Oct 21, 2025
will fix
plsgivemeachane commentedon Dec 28, 2025
+1. Should be fixed soon!
shanepadgett commentedon Dec 29, 2025
I look forward to this change as I default to interactive workflows, but also think we should make consider a system of allowing for agent changing and permissioning around it like Kilo Code does. Its architect agent can ask you to switch to the coding agent when it feels you have finished making decision with it so it can get to work.
thdxr commentedon Mar 25, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.