Skip to content
Docs0.9GitHubInstall

Running itBack up and move

Back up and move

What Vendetta keeps in its config and state folders, what to back up, and how to move an install to another computer.

What Vendetta keeps on disk and what is worth keeping a copy of, for whoever administers the computer. Two folders hold everything that is yours: the config folder and the state folder.

Stop the worker and the scheduler so files are not written while you copy, then archive both folders:

vendetta notify stop
vendetta schedule stop
tar -czf vendetta-backup.tar.gz -C ~ .config/vendetta .local/state/vendetta
vendetta notify start
vendetta schedule start

If systemd or launchd runs them, stop and start them there instead (Run at login).

Folder Default Moved by
Config ~/.config/vendetta XDG_CONFIG_HOME, or --config PATH for the file
State ~/.local/state/vendetta XDG_STATE_HOME
Web client ~/.local/share/vendetta/web [plugins.app] web
Binaries ~/.local/bin
File Holds
config.toml Every setting. Tokens belong in an environment variable or a command the file names, never in the file.
master-prompt.md The Master’s instructions
manager-prompt.md A manager’s instructions

install.sh creates these when absent and never overwrites them.

Worth backing up:

Path Holds
schedules/ Your schedules and their state (state.json)
history/ Seven days of activity journals: states and metadata, never prompts, messages, or tool arguments. Delete the folder to clear history.
names.json, teams.json, mutes.json, ephemeral.json Names you gave conversations, teams and their managers, muted agents, ephemeral chats
project-trust.json, project-agents.json Which project files you trusted and what they declared
notifications/ Messaging: paired devices as digests of their tokens (app-devices.json), the Web Push key (web-push.json), Telegram and Discord checkpoints of IDs, cursors, and receipts, and the kept copies of photos, videos, and audio agents sent (media/)
pages/ Pages agents wrote for you, each with its saved state beside it
diff/ Changes: changes.json, and mirrors/, a bare copy of each repo with every revision pinned
dictation/ Dictations kept to send again: the newest 20, up to 1 GiB, for a week
machines/ projects.json, the list of container projects, and each machine’s clone at machines/NAME/NAME with its proxy sockets
people/NAME/ Each person’s own state, config, and projects (home/projects)
instances.json, shares.json, shared-items.json The people you added, what is shared with whom, and the skills and MCP servers you picked for them
github/account.json Your GitHub token, if connected
app-address.json The address devices are given, when the Tailscale plugin moved it to a name

Not worth backing up:

Path Why
Per-agent status records They count only while their process lives
notifications/worker.log Emptied at each vendetta notify start
tmux/vendetta.conf, kitty/vendetta.conf Written again from your keys tables
tailscale/owned.json What the Tailscale plugin serves on this machine
*.lock Locks
  • Conversations. Each provider keeps its own transcripts in its own folder. Vendetta reads them in place. Back those up with the provider’s files.
  • Messages in the apps. The app plugin holds messages in memory; each device keeps its own history. Pins and chat pictures persist.
  • Pending alerts and timers, and plans. They live in the worker’s memory and go when it restarts.
  • Provider integrations. The hooks, the extension, and the Mod live in each provider’s folder. install.sh or vendetta install-claude and its siblings put them back.
  • Project machines’ volumes. Docker or Podman keeps each machine’s Claude config, Vendetta state, and installed tools.
  • Service units. ~/.config/systemd/user/vendetta-*.service on Linux, ~/Library/LaunchAgents/dev.vendetta.*.plist on macOS.

Stop the worker and scheduler and make the archive, as above. Leave them stopped, so only one computer runs your schedules and bots.

Install Vendetta and the providers (Install), then, before starting the worker:

tar -xzf vendetta-backup.tar.gz -C ~
vendetta config check
What Do
Absolute paths in config.toml (commands, [master.start] cwd, a vault) Edit them, or keep the same user name and layout
[plugins.app] public_url Set it to the new computer’s address and publish the port again (Publish)
Schedules Each names a folder (--cwd) and a project; put the projects at the same paths, or update them with vendetta schedule update
Paired devices Their tokens came across. A device connects to the address it paired at, so with a new address, pair it again.
Conversations to restore Copy the providers’ own folders and the project folders to the same paths
Project machines The clones came across with the state folder; the containers and their volumes did not. See Project machines to make them again.
People vendetta instance update writes their config again and restarts their workers
vendetta notify start
vendetta notify status
vendetta schedule status