The real workflow
Where Claude Code enters the work
An agency coding agent can cross client boundaries when repositories, terminals, credentials, caches, or sessions are reused between engagements.
Claude Code is a local or cloud coding agent with file, command, network, MCP, and editing capabilities governed by permissions, sandboxing, trust, and account settings.
Local and cloud sessions, account privacy choices, logs, and exported output may preserve code context in different places.
Claude Code only has the permissions granted to it, but broad read access, bypass modes, unsandboxed commands, or overpowered MCP servers can make that boundary much wider than expected.
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
repository and local file reads
edits and Bash commands
network access, MCP servers, hooks, and cloud environments
Settings to verify
Permission mode and deny rules
Filesystem and network sandbox
Trusted directories, MCP servers, hooks, and unsandboxed escape paths
Why this context matters
The consequence for agencies
Agency risk compounds when staff, contractors, shared tools, and reused credentials create paths between otherwise separate client environments. In this case, persistent chats and shared links can outlive projects, staff changes, client permissions, retention requirements, and the business reason for keeping the information.
Closing a browser tab does not necessarily delete the conversation, uploaded material, memory, project context, connector index, or shared link. Each product has its own controls, and account type can change the rules.
Every client remains isolated, access is attributable to a named operator, and the agency can deliver consistent evidence without revealing another client.
Context decision
Three questions before adding access
Can this operator or tool reach any repository, mailbox, drive, cache, token, or transcript belonging to another client?
Are credentials and AI sessions issued per client and person rather than shared across the agency?
Can the agency deliver useful proof to this client without including another client's names, paths, findings, or configuration?
Evidence goal: Create a separate client evidence record covering operator identity, workspace isolation, credentials, approved systems, review history, and delivery status.
A repeatable review
Four steps, no sensitive data required
- 1
Write down the exact Claude Code account, workspace, project, device, and connected service used in this workflow.
- 2
Review account privacy settings, session storage, cloud task records, verbose logs, and exported transcripts.
- 3
Assign the decision and next review to the client service owner or agency security lead; do not leave the access boundary as an unwritten assumption.
- 4
Avoid storing raw secrets in prompts and delete unneeded session artifacts according to the documented controls. Record the result without copying private content or raw credentials into the report.
Controls to apply
Reduce access before adding trust
Avoid storing raw secrets in prompts and delete unneeded session artifacts according to the documented controls.
Use temporary or incognito modes for disposable sensitive work when the vendor’s terms fit the task.
Keep personal, client, and employer conversations in separate managed contexts.
Set a recurring review for histories, memories, projects, indexes, and shared links.
Decision rule
Know when a formal baseline is justified
For ordinary personal questions, vendor privacy controls may be enough. When retained history intersects with connected work files, repositories, or client obligations, include it in the access baseline and evidence record.
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