Expose owned ephemeral-agent lifecycle APIs

Steps: 1. Call agents_spawn with a bounded Codex prompt that replies COMPLETE and exits. 2. Save the returned agent.id. 3. Call agents_list({}); the ephemeral run is absent. 4. Call agents_get({agent: returnedId}); it returns not found. 5. Attempt to query state, wait for completion, or close only that owned ID; no supported MCP operation exists. Expected: Expose owned ephemeral run list/get/status/wait/result/close operations with parent ownership, timestamps, completion/error summary, and rejection of attempts to close unrelated agents. Observed: The spawn response explicitly says the coordinator will not be notified and must tell the user to watch the tab. agents_list/get cover saved configurations only. A later spawn was rejected because eight throwaway agents were still counted as running.

This gathers what several people told us separately. Their original messages stay private: only this rewording is public, and nobody sees who wrote what.

Discussion0

You will be told by email and in the app on every reply. Every message carries a link to stop them.