You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
New tui does not let running agents using @agent_name. #3831
New TUI in versions 1.0.x doesn’t allow running agents using @agent_name. In older versions (0.15.x), it works correctly.
In versions 1.0.x, writing @ provides autocompletion to select files but doesn’t show agents. If you ignore autocompletion and type the agent name directly, it doesn’t recognize the name in the prompt and treats it as part of the input.
This is an issue when creating custom agents meant to function as subtasks.
According to the (documentation)[https://opencode.ai/docs/agents/], it should still work?
OpenCode version
1.0.x
Steps to reproduce
run opencode
switch to build mode
write prompt @plan create plan to implement hello world application in python
TUI will accept it as just regular prompt in build mode and would not invoke @plan agent.
Screenshot and/or share link
Operating System
macOS 17.7
Terminal
iTerm2. Problem is the same with regular Terminal.
In my use case, I've redefined the default @build agent to be a subagent. I did this to prevent unintentional switches to build mode without compromising the planning process.
But I'd still like to have the option to run simple tasks that don’t require planning by using @build do some task.
Is it possible to modify the check and remove the restriction on using built-in agents as subagents? Is there any reason for this limitation that I’m not understanding?
Activity
thdxr commentedon Nov 4, 2025
is this the built in plan mode? you don't have anything configured?
AbbasSrour commentedon Nov 4, 2025
I can confirm as well, the @ is not showing subagents for me also.
skozar commentedon Nov 4, 2025
i have configured agent named @refactor. It does work too.
skozar commentedon Nov 4, 2025
yes, it's default plan mode in example
thdxr commentedon Nov 4, 2025
can i see your config?
thdxr commentedon Nov 4, 2025
thdxr commentedon Nov 4, 2025
this is how we check
skozar commentedon Nov 4, 2025
In my use case, I've redefined the default @build agent to be a subagent. I did this to prevent unintentional switches to build mode without compromising the planning process.
But I'd still like to have the option to run simple tasks that don’t require planning by using
@build do some task.Is it possible to modify the check and remove the restriction on using built-in agents as subagents? Is there any reason for this limitation that I’m not understanding?
Thank you.