The real workflow
Where OpenAI Codex enters the work
The agent workflow can combine repository reading, file edits, terminal commands, dependency installation, tests, and network access.
OpenAI Codex can work locally or in cloud environments with repository files, commands, patches, network controls, approvals, plugins, and connected developer workflows.
Client repositories and files may be processed locally or through connected cloud environments under different account and access controls.
Codex behavior depends on the environment, sandbox profile, approval policy, network access, connected services, and task scope. A protected default can still be widened by explicit authorization.
The presence of this path does not prove an incident. It identifies the boundary that should be checked before more sensitive context or authority is added.
Tool-specific boundary
Inspect the real access points.
What may carry context
local repositories and worktrees
commands, patches, tests, and tools
cloud repositories, plugins, MCP servers, and network access
Settings to verify
Sandbox and approval profile
Writable roots and network policy
Repository, plugin, MCP, and cloud connections
Why this context matters
The consequence for developers
Developer workflows join high-value source code with tools that can retrieve context, propose changes, run commands, and cross trust boundaries quickly. In this case, exposure can trigger contractual disputes, notification duties, account reviews, project delays, and costly investigation even when no malicious intent was involved.
Client data is not yours to expose simply because it helps complete a task. The practical question is whether the client authorized this tool, this account type, this data category, and this specific access path.
The team can reproduce what the tool accessed, separate read and write authority, protect secrets, and review consequential changes before execution.
Context decision
Three questions before adding access
What can this session read, write, execute, contact over the network, and approve without another person?
Are secrets, production data, protected branches, deployment credentials, and unrelated repositories outside the effective scope?
Will the final diff, commands, dependency changes, test evidence, and approvals survive after the session closes?
Evidence goal: Produce a reproducible technical record of roots, permissions, denied paths, network policy, generated changes, approvals, tests, and rollback points.
A repeatable review
Four steps, no sensitive data required
- 1
Write down the exact OpenAI Codex account, workspace, project, device, and connected service used in this workflow.
- 2
Confirm authorization, account plan, environment location, repository scope, retention, and client restrictions.
- 3
Assign the decision and next review to the repository owner or engineering lead; do not leave the access boundary as an unwritten assumption.
- 4
Create an isolated client worktree or cloud environment containing only approved materials. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Create an isolated client worktree or cloud environment containing only approved materials.
Use separate client workspaces and least-privilege accounts instead of one shared personal AI context.
Minimize, redact, or synthesize data before it reaches the assistant.
Keep a simple register of approved tools, client constraints, access dates, and deletion steps.
Decision rule
Know when a formal baseline is justified
If a task contains client-confidential material, do not proceed on assumptions. CapitalGuard becomes useful when the work also involves repositories, connected tools, repeat client workflows, or evidence that must be shown back to the client.
CapitalGuard is relevant when the workflow includes repositories, recurring private work, credentials, connected systems, commands, or evidence that must be shared with another person. It does not inspect this account from the page or guarantee that an incident cannot occur.
Primary references