Feature request: persistent daemon agent for workspace context and main-agent coordination

What variant of Codex are you using?

Codex App / CLI

What feature would you like to see?

I’d like Codex to support a persistent background daemon agent that runs alongside the main agent within a workspace.

The key idea is not just background scanning, but a first-class agent that stays alive during the session and can coordinate with the main agent through both pull and push communication.

Core concept

A workspace-scoped daemon agent should be able to:

• run continuously in the background
• observe workspace state over time
• maintain structured context that should not be forgotten mid-session
• communicate with the main agent in two ways:
• pull: the main agent can query the daemon for current state or recommendations
• push: the daemon can proactively notify the main agent when important changes happen

Why this matters

In longer coding sessions, the main agent is often focused on the immediate task and loses track of operational context that evolves in parallel.

What I want is a durable “background brain” for the workspace, rather than forcing the main agent to repeatedly rediscover or remember everything itself.

One concrete use case: multi-repo workspace intelligence

A strong example is a project folder that contains multiple child Git repositories.

In that setup, the daemon agent could maintain per-repo context such as:

• current branch
• whether the branch has already been merged upstream
• dirty/clean state
• ahead/behind status
• detected language / stack
• canonical lint / test / build entrypoints
• environment hints such as “use uv run”, “use make test”, “use pnpm”, etc.

This would help prevent common failures like:

• only discovering at commit time that the current branch was already merged and a new branch should be created
• forgetting repo-specific execution conventions, especially Python environments that require uv
• repeatedly re-explaining how a given sub-repo should be linted or tested

Important clarification

The Git/repository example above is just one business scenario for the daemon agent.

The feature request is broader:
I’m asking for a persistent background agent architecture with structured main-agent coordination, not only for Git status reporting.

Proposed UX

Possible surfaces could include:

• automatic startup of a daemon agent when entering a workspace
• a command for the main agent to query daemon state
• background notifications from the daemon to the main thread when something important changes
• a compact status panel showing what the daemon currently knows

Acceptance criteria

• Codex can run a persistent daemon agent for the active workspace
• the daemon can keep state across the session instead of acting like a one-shot tool call
• the main agent can pull structured information from the daemon on demand
• the daemon can push important events back to the main agent proactively
• multi-repo Git tracking is possible as one implementation/use case, but the daemon mechanism is general-purpose

Additional information

This feels related to existing requests around event surfaces, sub-repo awareness, and durable workspace context, but the missing primitive is a true background daemon agent that can collaborate with the main agent throughout the session.