Add terminal completion notifications and active terminal indicators to chats
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
Codex App / Desktop
What feature would you like to see?
I would like better visibility into integrated terminals when multiple chats are open.
Currently, it is easy to start a process in the terminal of one chat and then switch to another chat. In this situation, the user may forget that a process is still running or may not notice when it finishes or fails.
Some common examples:
- starting a deployment and switching to another chat;
- leaving a server, build, or other long-running process running;
- running a command, switching chats, and not noticing that the command exited with an error;
- working across several chats/projects and losing track of which chat contains the active terminal.
It would be useful if Codex could:
- Notify the user when a terminal process finishes, especially for processes that have been running for some time.
- Visually distinguish whether the process completed successfully or with an error.
- Show a terminal icon on the chat while that chat has an integrated terminal open.
- Optionally show an additional state when a process is currently running, making it easy to locate chats with active terminal activity.
This would be particularly useful for users who work with many chats simultaneously and use integrated terminals for deployments, builds, development servers, and other long-running commands.
Additional information
Notifications would not need to appear for every short-lived command. There could be a small duration threshold or a setting that controls when completion notifications are shown.
It would also be useful for the chat indicator to expose simple states, such as: terminal open, process currently running, and last process completed with an error. This would make it much easier to identify which chat needs attention without opening each chat individually.
Contributor 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.
Research direction
No files or tests are named. Start by locating the Codex App/Desktop entry points for integrated terminal state, chat indicators, and notifications; define the states and notification threshold before implementation. Done means chats expose terminal activity and process outcomes, with completion notifications for qualifying commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100