Where Claudette keeps things

Claudette keeps its files in two folders in your user profile: one for its settings and one for everything else, its data. Claude Code keeps its own files separately.

The folders

  Windows macOS Linux
Settings %APPDATA%\Claudette ~/Library/Application Support/Claudette ~/.config/claudette
Data %LOCALAPPDATA%\Claudette ~/Library/Application Support/Claudette ~/.local/share/claudette

On Linux, XDG_CONFIG_HOME and XDG_DATA_HOME move them. The Windows package keeps its files in these same places.

Settings → Advanced → Open data folder shows the data folder in your file manager.

To keep a copy of Claudette’s files somewhere else, such as for trying things out, start it with the CLAUDETTE_HOME environment variable set to a folder. Claudette then keeps everything under that folder, in settings and data, and leaves your real files alone. A copy started that way leaves your login entry alone too (Starting at login).

What’s in them

Settings are in settings.json in the settings folder. It holds the choices you make in the Settings window. It never holds a password or an API key.

The data folder holds:

Where What it is
state.json What Claudette remembers about this machine: your open tabs and their order, groups, recent and favorite folders, which folder a session’s project is on this machine, and notices you dismissed.
usage.db Usage history: plan usage readings, and for each turn the tab, model, token counts and estimated cost. Never your prompts, Claude’s replies or any code. It’s this machine’s own, and kept for as long as Settings → Usage → Keep usage history says (1 month by default).
drafts Each tab’s unsent message, and the stash (Earlier prompts, drafts and the stash).
scratch This machine’s copy of each scratch pad.
library The session library, unless you’ve pointed it somewhere else.
sessions Working copies of sessions you opened from the library, which Claude Code continues from.
logs claudette.log, with Claudette’s own warnings and errors, kept under 2 MB (with one older copy). The protocol folder inside holds raw logs of what each session sends and receives, only while Settings → Advanced → Log protocol traffic is on. They hold your prompts and file contents, and Claudette deletes them after 7 days. Open log folder opens the protocol folder.
updates A Claudette update you’ve downloaded, until you’ve installed it.
before-content, diff-temp Files Claudette keeps so it can show and revert what Claude changed: large files as they were before Claude’s first change, and the “before” files an external diff tool is handed.
utility, project-jobs, builds, presence Working files: the folder of Claudette’s hidden helper session, files that project actions write for Claudette to read, the copies a source build runs from, and a marker that exists while Claudette’s window is in front.
restart.json, restart-ready Files that exist only while Claudette restarts into an update or a new build, to carry your tabs across.

Unsaved edits in a Project files tab are kept in editor-backups, so quitting never loses them. The names and colors of your API-key accounts are in state.json. Their keys aren’t (Passwords and keys).

Claudette writes its files whole or not at all: to a temporary file, then renamed over the real one. A crash or a power cut leaves the old file or the new one, never half of one. A settings or state file that isn’t valid is kept next to it as <name>.<time>.bad, and Claudette starts from defaults (Settings back to their defaults).

The session library

The library is where a tab that syncs copies its session, in the library folder or the one you chose. Each session has its record and a copy of the transcript, which holds your code, command output and anything else Claude read. The session library lists what’s in it and What leaves this computer says when it goes anywhere.

Claude Code’s own files

Claude Code keeps its sign-in, its settings and its transcripts of your sessions in its own folder: ~/.claude, or the folder CLAUDE_CONFIG_DIR names. Each tab runs the real claude, so those files are the ones the terminal’s claude uses.

  • Claudette reads the transcripts, for History and to show a session’s earlier conversation.
  • Claudette never reads or stores your sign-in. Claude Code keeps it, and Claudette only asks Claude Code whether you’re signed in.
  • Claudette’s settings are separate from Claude Code’s. Claudette doesn’t edit Claude Code’s settings.json or a project’s .claude settings, except where a feature says so: Always allow on a permission card has Claude Code save a rule to the project’s .claude/settings.local.json (Permission cards).
  • Claude Code deletes its transcripts after 30 days by default, which History can only list as long as they last. Sessions that sync keep their copy in the library.

See also

Back to top

Claudette is made by dotBunny under the MIT license. Privacy policy

Claude and Claude Code are trademarks of Anthropic, PBC. Godot and the Godot logo are trademarks of the Godot Foundation; the logo is by Andrea Calabró, under CC BY 4.0. Unity is a trademark or registered trademark of Unity Technologies or its affiliates in the U.S. and elsewhere. Unreal®, Unreal Engine®, and the Unreal Engine® logo are trademarks or registered trademarks of Epic Games, Inc. in the United States of America and elsewhere. Other brands or product names are the trademarks of their respective owners. The logo is used with Epic's permission. Perforce, P4V and the Perforce logo are trademarks of Perforce Software, Inc. or one of its affiliates; the logo is used with Perforce's permission. Claudette isn't sponsored by, affiliated with or endorsed by any of them. Other names are trademarks of their owners.

Edit this page on GitHub

This site uses Just the Docs, a documentation theme for Jekyll.