Skip to content
Weaveweave / fleet
Install Fleet
Docs/Reference/Where Fleet keeps data

Where Fleet keeps data

What lives in the ~/.weave folder, where Fleet writes its logs, how to move the data, and what is safe to delete.

Fleet keeps your sessions, settings and tokens in one folder on your computer. Nothing is stored in the cloud. The desktop app and the fleet command use the same folder.

The folder is ~/.weave (%USERPROFILE%\.weave on Windows). To use another one, pass --data-dir or set WEAVE_FLEET_DATA_DIR. --profile <name> uses profiles/<name> inside it. See The fleet command.

Only one Fleet can use a data folder at a time. A second one stops with exit code 75.

What is in it

Section titled “What is in it”
Path What it holds
fleet.db Your sessions, projects, messages and settings. This is the important one. The -shm and -wal files beside it belong to it.
fleet-analytics.db Usage numbers Fleet records.
fleet-keys/ The keys Fleet uses to encrypt secrets it stores.
fleet.machine.json This Fleet’s name and its access token for other devices. Only you can read it.
fleet.push.json The keys for phone push notifications. See Fleet on your phone.
fleet.lock and fleet.instance.json Show that a Fleet is running here.
fleet/ The Fleet program itself, from the terminal install.
mods/, skills/ Your mods and skills, with their saved versions.
memory/ What Fleet remembers for you.
terminals/ Saved terminal scrollback.
screenshots/, pages/ Screenshots and pages that agents showed you, kept per session.
weave-config/ The Weave settings you edit in Fleet.
opencode/, opencode2/, claude-code/ Files Fleet gives each harness: built-in skills, profiles and sign-in folders.
harnesses/, runtimes/ Tools Fleet installed for a harness, such as a separate OpenCode 2 or Bun.
integrations/ Settings for connected services.
release-notes.json, catalog-cache.json Saved copies of release notes and the skill catalog.
fleet.db.legacy-backup A copy of an older Fleet database, made before Fleet changed it. Fleet imports its sessions into an empty fleet.db.

You may not see all of these. Fleet makes each one when it first needs it.

Outside the data folder

Section titled “Outside the data folder”
  • Worktrees. Each session works in a git worktree. By default Fleet puts it next to your repository, in a folder named like storefront-worktrees. A worktree naming setting can change that.
  • .weave/attachments inside a session’s worktree holds files you attached to that session.
  • Logs. Fleet writes one file a day, fleet-yyyy-MM-dd.log, to a WeaveFleet/logs folder in your app-data folder. That is ~/.local/share/WeaveFleet/logs on Linux, ~/Library/Application Support/WeaveFleet/logs on macOS and %LOCALAPPDATA%\WeaveFleet\logs on Windows. Fleet deletes logs after 30 days.
  • harness-processes/, in the same WeaveFleet folder, lists the harness processes Fleet started, so it can stop them if it quits unexpectedly.
  • A node as a service logs to journalctl --user -u fleet-node on Linux and ~/Library/Logs/fleet-node.log on macOS.

What is safe to delete

Section titled “What is safe to delete”

Quit Fleet first.

Delete What happens
Old files in logs/ Nothing. Fleet clears them itself after 30 days.
release-notes.json, catalog-cache.json Fleet fetches them again.
screenshots/, pages/, terminals/ You lose that history. Sessions still work.
fleet-analytics.db You lose those usage numbers.
fleet/ Fleet is uninstalled. Your sessions stay. Install again to get it back.
fleet.lock, fleet.instance.json Nothing, if Fleet isn’t running.

Do not delete fleet.db, fleet-keys/ or fleet.machine.json unless you want to start over. Without fleet-keys/, Fleet can’t read secrets it saved. Without fleet.machine.json, other Fleets lose their access to this one.

To back up Fleet, quit it and copy the whole data folder.

Where next

Section titled “Where next”