Where the workflow shifted
OpenAI's Agents SDK guide shows Codex CLI exposed as an MCP server so a larger agent system can call it across turns.
When Codex is embedded inside an internal platform, keep task input, session ID, tool calls, tests, diff, and human confirmation visible.
Tool names are not outcomes
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check permissions and failure
- Add a session-record page for internal coding-agent work: task, repo, branch, tests, PR, review, and rollback
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Without session evidence, teams cannot see what the agent did, why it did it, or where humans must take over. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.