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.
A task rooted too high in the filesystem or connected to a broad repository set can expose unrelated context.
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, oversharing can expose customers, employees, pricing, incidents, internal strategy, credentials, and contractual information without any need for broad system access.
Most oversharing is not malicious. It happens because copying the whole document, screenshot, error log, inbox thread, or customer export is faster than preparing a minimal example.
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
Confirm cwd, worktree, mounted paths, repository selection, and attachment list before starting.
- 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
Use one narrow worktree per task and avoid home-directory or multi-client roots. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Use one narrow worktree per task and avoid home-directory or multi-client roots.
Use a redaction checklist for screenshots, logs, contracts, support tickets, and customer exports.
Create synthetic examples for recurring prompts instead of repeatedly cleaning real records.
Keep sensitive source material outside the AI workspace unless access is explicitly justified.
Decision rule
Know when a formal baseline is justified
A license is not necessary for every harmless prompt. It becomes justified when oversharing risk is repeatable, involves client or company systems, or combines with repository and connector access that needs enforceable controls.
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