Skip to content
Powered by BridgeApp

File locations

Every path Magic Coder touches, in one place.

All under ~/.magic/:

PathWhat it isEdit by hand?
~/.magic/config.tomlUser config (machine ID, generation defaults, UI prefs)Yes
~/.magic/known.tomlWorkspace registry (paths and trust state)Yes
~/.magic/known/<key>/history.jsonlPer-workspace input historyDelete to wipe; don’t edit by hand
~/.config/magic-coder/credentials.jsonLinux fallback OAuth credentials fileUsually no
~/.magic/skills/<name>/SKILL.mdUser-level skill (loaded on every session)Yes
~/.magic/rules/<category>/<name>.mdUser-level Markdown rule (loaded on every session)Yes
~/.magic/cache/Internal cache (incl. background shells)No
~/.magic/locks/Lock filesNo

<key> is a stable hash of the workspace’s absolute path.

All under <workspace>/.magic/:

PathWhat it isEdit by hand?
<workspace>/.magic/skills/<name>/SKILL.mdProject-local skill (loaded only when trusted)Yes; commit
<workspace>/.magic/rules/<category>/<name>.mdProject-local Markdown rule (loaded only when trusted)Yes; commit

In addition, Magic Coder reads project-context files from your repo:

PathWhat it isEdit by hand?
<workspace>/AGENTS.mdProject context loaded at session startYes; commit it
<workspace>/<subdir>/AGENTS.mdPer-package project context, loaded on demand when work touches the subtreeYes; commit it
WhereWhatHow to manage
MAGIC_CODER_OAUTH_TOKENIn-memory opaque access-token override that wins over every other credential sourceUnset it, or replace it with a fresh token
macOS KeychainOAuth credentials (service magic-coder-credentials, account = your macOS username)/logout from inside the TUI; or Keychain Access
Linux Secret Service / GNOME KeyringOAuth credentials in the native keyring/logout; or seahorse / secret-tool
~/.config/magic-coder/credentials.jsonLinux fallback OAuth credentials file/logout; or remove the file
%APPDATA%\magic-coder\credentials.jsonWindows fallback OAuth credentials file/logout; or remove the file
OS temp dirShort-lived files for browser-flow callbacks during sign-inCleaned up automatically

You generally never need to edit OS-managed paths directly.

Not on your machine, but useful to know:

Terminal window
# 1. Sign out (from inside the TUI; clears the saved credential)
/logout
# 2. Remove all user state
rm -rf ~/.magic
# 3. (Optional) Remove per-project state from each repo
find ~/code -type d -name '.magic' -prune -exec rm -rf {} +

After step 2, your next coder run will sign in fresh and treat every workspace as new. Step 3 is destructive — it removes every .magic/ directory it finds, including project-local skills and rules you may have committed. Most users don’t want this.