VS Code: support external workflow / local-controller notifications into Codex sessions

What feature would you like to see?

Support external workflow / local-controller notifications in Codex for VS Code, so background systems can surface state changes to the active Codex/editor workflow without PTY hacks or manual polling.

A concrete example is a local Argo / Kubernetes workflow that starts, fails, or completes after Codex has submitted it. I want Codex in VS Code to be able to receive that event and show it to the user or route it into the active task/session in a structured way.

This is not a request for arbitrary remote control. The useful minimum would be an opt-in local ingress or notification bridge that lets trusted local controllers deliver structured events into Codex's VS Code surface.

Why this matters

Right now the flow for long-running jobs is awkward:

• Codex launches or helps prepare a workflow/job
• the job runs in Kubernetes/Argo in the background
• when the job changes state, there is no clean way for that external state change to appear back in Codex / VS Code
• the user has to keep polling kubectl, Argo UI, or logs manually

That makes long-running research/dev workflows much worse than they need to be.

The ideal outcome is that Codex can say something like:

• workflow started
• workflow failed
• approval needed
• downstream stage is now unblocked

without the user manually refreshing another terminal.

What I expected

At least one supported path such as:

1. Opt-in local notification ingress for Codex VS Code

• a trusted local process can send structured events to the active Codex session/UI
• local-only by default
• no keyboard/terminal emulation

1. A lightweight event bridge / inbox model

• external tools can post structured status updates
• Codex surfaces them as notifications, inbox items, or attachable context

1. A documented API for editor-integrated Codex sessions

• enough to support workflow systems like Argo, Kubernetes jobs, CI, or local orchestrators

What I observed

Today there does not appear to be a supported way for external workflow state to reach an active Codex VS Code workflow.

Related requests exist for CLI/TUI ingress and inbound MCP notifications, but the VS Code/editor-integrated workflow case still feels uncovered.

Why this is useful

This would make Codex much better for:

• Argo / Kubernetes workflows
• CI/CD jobs
• long-running background tasks
• local multi-agent / orchestrator setups
• workflows where Codex submits something and should later be notified when the result is ready

Suggested scope

A minimal first version would already be useful if it only:

• accepts trusted local notifications
• shows them in the VS Code Codex surface
• optionally lets the user attach the event payload into the current conversation/task

A more advanced version could support richer local controller semantics later.

Related issues

This feels related to, but distinct from:

• #15299 inbound MCP notifications into an active CLI session
• #15355 opt-in local ingress for trusted local controllers in CLI/TUI

The difference here is the focus on Codex in VS Code and on workflow/job event notifications, not only terminal sessions.