Codex + Deputy
Codex runs the task; the Deputy connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Codex, asks for Deputy access before sending, and keeps both choices in one task draft.
How the combination works
Codex plans and executes. Deputy supplies authorized app access.
Codex owns the coding-agent loop: it explores the repository, changes files, runs commands, and returns evidence from the cloud workspace.
Employee scheduling, timesheets, tasking and communication platform
Codex
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Deputy connector
Supplies the currently exposed operations for the authorized Deputy account. It does not promise every feature in the Deputy product.
Permission boundary
The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Codex can do.
Setup and first task
Connect one Deputy account and verify one known resource.
The Composer preselects Codex with GPT-5.6 Sol. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.
Open the Codex Composer
The Composer above carries Codex, GPT-5.6 Sol, and Deputy. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Deputy account
Review the Deputy account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.
Run and verify a bounded task
Name one Deputy resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in Deputy and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Access, cost and limits
What to verify before scaling Codex + Deputy
Software engineering tasks that benefit from Codex's repository navigation, command execution, and iterative implementation loop.
Establish with the first run
- Codex and GPT-5.6 Sol remain selected after sign-in.
- Deputy shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.
Still depends on your setup
- A catalog listing does not guarantee every Deputy website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.
Verification and recovery
Check Deputy itself before trusting the result.
Open the same resource in Deputy and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Connection troubleshooting
If Deputy access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
Writes need explicit scope
Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
Re-check current state
For decisions or follow-up writes, open the resource in Deputy and check its current state. A successful earlier read may already be stale.
Common questions
Related resources