Skip to main content
Admins need to be able to answer three questions about any thread: where its data lives, where its work actually executes, and who can reach the credentials a tool call depends on. This page answers those questions at the Sidekick level. For the security posture that applies across all of Oximy, see Security and privacy.

​
Where data lives

A thread’s conversation, tool calls, approvals, files, and artifacts stay together, inside your workspace. Nothing about a thread is split off into a separate system that you’d need to reconcile against it later. The thread itself is where that data lives.

​
Execution is contained inside a placement

Work runs inside a placement: either the cloud or an approved computer you’ve enabled. Both draw a boundary around the work. Cloud placement runs the work in a managed sandbox isolated to the thread that’s using it. It doesn’t share state with other threads or other workspaces, and it goes away once the work is done. Running on your computer draws the boundary differently: the work is confined to that one approved computer, under the permissions you’ve granted, and never leaves it. Either way, execution stays inside the placement that’s running it. It does not reach outside that boundary to touch other threads, other workspaces, or other computers.

​
Credentials are held at the gateway, never in the sandbox

When a thread calls a connector, the credential that connector needs does not travel into the sandbox that’s running the agent. It stays at the gateway, which authenticates the call and attaches the credential only at the last hop, right before the request reaches the external system. This means the environment doing the reasoning and tool-calling never holds a credential it could leak or misuse. If that environment were ever compromised, there’d be no credential sitting inside it to expose, because it never had one.

​
The thread ledger is the record of what ran

Every tool call, every approval, and everything a placement executed on a thread’s behalf gets written back to the thread. That’s what makes the thread useful for security review, not just for getting work done: it’s a faithful, replayable account of what happened, not a summary reconstructed after the fact.

​
Where to go next

Security and privacy

The workspace-wide security posture across every Oximy product.

How work runs

How a thread executes on a harness inside a placement.