The real workflow
Where OpenAI Codex enters the work
A freelance coding agent may read a client repository, run commands, edit files, and use local credentials from the same working environment.
OpenAI Codex can work locally or in cloud environments with repository files, commands, patches, network controls, approvals, plugins, and connected developer workflows.
Codex can run commands under the configured sandbox and approval policy, with escalation requiring explicit authorization.
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 freelancers
A freelancer carries both the delivery risk and the trust risk when one convenient AI workflow mixes personal accounts with confidential client work. In this case, in a work environment, command authority can affect source code, deployment, cloud resources, customer systems, billing, and the integrity of the development pipeline.
A text answer is advice. A command changes state. Once an AI workflow can run scripts, install packages, edit files, call infrastructure, or reach the network, review and containment matter more than conversational confidence.
Each client has a clear access boundary, sensitive inputs are minimized, and the freelancer can explain the controls without exposing the underlying data.
Context decision
Three questions before adding access
Did the client approve this tool, account type, and category of information for the stated task?
Can names, credentials, production records, or unpublished work be replaced with a synthetic example?
Does this account and connected workspace belong to the correct client rather than a personal or reused environment?
Evidence goal: Keep a client-by-client access note that records authorization, approved tools, data limits, account ownership, and the deletion or handoff step.
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
Review the active profile, sandbox mode, writable roots, network restrictions, and escalation behavior.
- 3
Assign the decision and next review to the freelancer responsible for the client account; do not leave the access boundary as an unwritten assumption.
- 4
Keep default sandboxing, approve bounded command prefixes, and deny unnecessary network access. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Keep default sandboxing, approve bounded command prefixes, and deny unnecessary network access.
Run with the least operating-system and cloud privilege that can complete the task.
Deny secret paths and unnecessary network destinations even when commands are otherwise allowed.
Require human review for destructive, external, authentication, deployment, and financial operations.
Decision rule
Know when a formal baseline is justified
If the product is text-only, do not imply command risk that does not exist. If command or tool execution is enabled, a documented sandbox and approval policy should exist before production work begins.
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