File locations

This reference describes the local files used by the client represented in this documentation. Its application folder is ~/.code-shared-config; the paths below are relative to that folder unless stated otherwise. Do not edit managed state files to configure toolkits. Use the web app or CLI.

Cursor project setup is different from a managed launch: it writes supported toolkit files into the project folder.

Local state and downloaded content

Path	Purpose
machine.json	Computer and workspace identifiers.
keys/machine.key	The computer’s request-signing key when stored in a file.
cache/manifest/index.json	The fetched toolkit index.
cache/manifest/<toolkit id>.json	The fetched definition of one toolkit.
state/last-sync.json	Last sync result; the adjacent lock coordinates writers.
state/manifest-diagnostics.json	Diagnostics from the last toolkit fetch.
state/pending-enrollment.json	An unfinished computer sign-in.
state/fetch-stamps/<host>__<owner>__<repo>	Repository fetch times.
state/machine-runtime-reports/<machine id>.json	Unsent runtime reports; an adjacent directory holds queued reports and locks.
repos/<host>/<owner>/<repo>.git	Downloaded repository data without a working folder.
worktrees/<host>/<owner>/<repo>/<commit>/	A checkout of a specific repository version.
sessions/<session id>/	Configuration for a managed launch.
runtime/<session id>/	Files required while a run is active.
logs/	Sync and program logs.
broker/	Local credential-runtime state, created when needed.
materialized/<toolkit id>/<target>/<version>/	Prepared toolkit content associated with its version and delivery target.

Managed local state uses owner-only permissions. Do not share these folders as a diagnostic bundle without checking them for sensitive data.

Managed launch files

These paths are inside the run’s configuration folder. They are not necessarily paths relative to your project or the app’s normal user folder.

Coding app	Files prepared for the run
Claude Code	skills/, agents/, commands/, output-styles/, CLAUDE.md, settings.json, hook scripts, and MCP registration metadata.
Codex	skills/, agent role files, AGENTS.md, hooks.json, and a copy of config.toml. Commands become skills.
opencode	Skills, agents, commands, AGENTS.md, and the copied opencode.json with its MCP registrations.
Antigravity	Its app configuration tree inside a separate home folder for the run.
Cursor Agent	A managed run. Its only project write is the MCP servers in .cursor/mcp.json.

Authored repository layouts and runtime destinations are different. Claude Code repositories commonly use .claude/skills/; the shared .agents/skills/ source layout is not a promise that every target reads that exact runtime path. See the individual coding-app guides.

Cursor project files

Set up and open writes skills and converted commands under .agents/skills/, agents under .cursor/agents/, the toolkit’s MCP servers into .cursor/mcp.json, and a file-ownership record under .code-config/ in the project. Cursor explains the supported content and write failures.

Existing coding-app configuration

Account import copies source account files into managed account storage without deleting the originals.

For Codex, toolkit changes apply to a launch copy of ~/.codex/config.toml. Decisions you make inside Codex itself during the run, such as trust and approvals, can be carried back to the original without the toolkit’s overrides. The original file can still change (it is not frozen). See Codex.

Next

Troubleshooting.