Show agent-started dev servers and background processes in Codex Desktop
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App
What feature would you like to see?
Feature request
When Codex Desktop starts long-running local processes such as:
npm run dev- Next.js / Vite dev servers
- Python web servers
- Docker-related processes
- other background commands
there should be a dedicated place in the app where the user can see and manage them.
Current problem
Codex may start a localhost development server during a task, but afterwards it is not obvious which processes are still running.
To find them, I currently need to leave Codex and use tools such as:
lsof -iTCP -sTCP:LISTEN -n -P
ps aux
This is especially difficult when working across multiple Codex threads or projects.
Since Codex started the process, it would be useful for Codex to retain and expose that information in the UI.
Suggested UI
A "Running processes" or "Dev servers" view could show:
- Project / worktree
- Command
- PID
- Port
- Localhost URL
- Start time / duration
- Current status
With actions such as:
- Open localhost URL
- View logs
- Stop
- Restart
Example:
Running processes
● localhost:3000
npm run dev
project: my-next-app
PID 48231
[Open] [Logs] [Restart] [Stop]
This would make it much easier to understand what Codex has left running and avoid orphaned development servers or background processes.
Related issues
Related, but not quite the same:
- #37213 — visibility of commands being run in Codex Desktop
- #7932 — background process handling / missing job control in Codex CLI
- #26773 — Codex Desktop process cleanup / leaked processes
- #32948 — insufficient visibility into whether tasks are actually still running
Additional information
No response
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
Start by reading related issues #37213, #7932, #26773, and #32948 to understand existing command visibility, background-process handling, cleanup, and task-status work. Then identify the Codex Desktop process-management and UI entry points. Done means users can see and manage Codex-started processes across projects, including their command, status, and available open, logs, stop, and restart actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100