Skip to main content
Every karta is a durable private computer that accumulates files across its sessions - its memory. With workspace access enabled, an admin can clone that workspace read-only over git to inspect, back up, or audit exactly what a karta has built up.

​
Enable it

Workspace access is off by default. An organization admin turns it on per agent, from the agent’s settings in the dashboard. Enabling it is a recorded attestation that requires re-authentication, and every clone is written to the audit log.
The setting is per agent and covers all of that agent’s kartas. Turn it off to stop new access.

​
Clone a karta

Sign in once - karta login installs a git credential helper - then clone the karta’s git address, shown on its page in the dashboard:
1

Sign in

karta login
2

Clone the workspace

git clone <clone-url>   # the git address on the karta's page
3

Fetch later changes

git pull
The credential helper authenticates each request with a short-lived, read-only credential, so the address you clone never carries a secret.

​
What you get

The clone is the karta’s workspace as it runs: the agent’s own files plus everything that karta has changed across its sessions, with history - so git pull brings down what changed since. It is the same thing you would see if you ran the agent folder locally and had those conversations.

​
Guarantees

Read-only. Workspace access is clone and pull only. There is no push, so an export can never alter a karta.
Workspace files are served directly by the data plane that runs your agents and never pass through Karta’s control plane, so a clone keeps a karta’s data within its own boundary. Access stays gated by the admin attestation and recorded in the audit log.