Ship a change
Inspect a repository, update the work item, open a pull request, and notify the team from one agent workflow.
GitHubLinearSlack
CODEX + WORKING MACHINES
Connect Codex to the software around your codebase
Working Machines gives Codex structured access to business and engineering applications through MCP. Codex can discover the actions relevant to a task, request an authorized connection, execute the selected action, and receive a structured result without handling provider credentials directly.
The connection begins with a compact discovery surface rather than the full catalog. Codex loads the action contract it needs, operates through a named account connection, and receives a structured response. Working Machines applies authorization and action policy at execution time, outside the prompt.
REAL WORK ACROSS APPLICATIONS
Work across apps, not inside them.
Investigate an incident
Find unresolved errors, connect them to recent deployments, create prioritized issues, and publish the incident summary.
SentryGitHubLinearSlack
Coordinate a release
Check repository state, inspect deployment status, update the release task, and communicate the outcome.
GitHubCloudflareLinearSlack
CAPABILITY LAYER
Give Codex capabilities, not credentials.
Repository work
- Inspect repositories and changes
- Create issues and pull requests
- Review CI and deployment context
Project coordination
- Search and update engineering tickets
- Assign owners and change status
- Attach implementation context
Team communication
- Read relevant channels
- Post release or incident summaries
- Create focused discussion threads
SETUP
Connect in five steps.
- 01Copy the Working Machines MCP URL.
- 02Add it to the Codex MCP configuration.
- 03Complete the browser authorization flow.
- 04Connect only the applications needed for the task.
- 05Ask Codex for an outcome and approve sensitive actions when appropriate.
BOUNDARIES
What to consider.
- Codex receives action inputs and returned results, so do not send data your selected model configuration should not process.
- Provider credentials remain inside Working Machines, but action results are visible to the calling agent.
- Use narrow provider scopes and separate connections for production-sensitive systems.
ONE CONNECTION. REAL WORK.
Give your agent software it can use.
Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.