Repository navigation
[FEATURE]: Better active/background terminal and bash management #6375
Description
Activity
This issue might be a duplicate of existing issues. Please check:
- [FEATURE]: Configurable command timeout in config.json #3950: Configurable command timeout in config.json - directly addresses the timeout limitation mentioned
- Feature Request: Add Background Bash Execution (Like Claude Code’s Ctrl+b) #1970: Background Bash Execution feature request - proposes background terminal management similar to your proposal
- [feat] True Async/Background Sub-Agent Delegation #5887: True Async/Background Sub-Agent Delegation - discusses async background execution for long-running processes
- Bash tool does not show time out to model or user, model might set time out incorrectly #2985: Bash tool does not show timeout to model - relates to timeout handling and long-running processes
Feel free to ignore if none of these address your specific case.
Codex now has background terminals with polling and I can indeed confirm that it has been very useful for long running tasks whereazs opencode has to terminate and rerun with a longer timeout (unless I remember to tell it that this is going to be a long running thing)
Reacted by Alan Chen, Santiago M. Mola, Caleb Reyes and W1RealTo stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
this would be very nice to see. it's probably one (and only) thing i miss coming from cc/codex!
Feature hasn't been suggested before.
Describe the enhancement you want to request
So currently in OpenCode TUI the way that a terminal can spawn is via a simple
spawn()with piped stdio rather than a full PTY.Some current issues:
SIGTERMto a long running process which would kill it.What I propose:
As I said in this thread, I think the bash/terminal management should be a suite of tools.
When a terminal process is initiated we can keep the timeout and character limit the same, but when the timeout is reached rather than sending a
SIGTERMit will just move that terminal to a background terminal (accessable via some TUI keybind).Then once a terminal has moved to the background the agent should have some tools like
grepandexecuteCommandInTerminalso that it will not fill up a ton of context that isn't needed.This would allow the agent to start/manage/modify/delete sessions a whole lot better than what it does currently. I think a POC might be achievable via a plugin but I want to see what others think of this and other points of view.