Uninstall & Updates

Updates

Vibeless updates itself. The app checks for new versions, downloads them in the background, and verifies each update against the release signature before installing. There is nothing to re-download by hand — the download page always serves the current version for fresh installs.

Uninstalling cleanly

The order matters: remove the agent integrations first, while the app can still do it for you.

1. Per project: Project Settings → Connected Agents → Uninstall for each installed agent. This surgically removes the Vibeless entries from your editor's config files, deletes the hook envelope files, and cleans the .gitignore lines Vibeless added. Your own MCP servers, hooks, and rules are left untouched.
2. Uninstall the app through your OS as usual — Windows "Add or remove programs", or drag Vibeless out of Applications on macOS.
3. Optionally remove data:
   • ~/.vibeless/ — the app's own state (registered projects, sign-in tokens, logs).
   • <project>/.vibeless/ in each project — the project's specs, decisions, version history, and drift baselines. Only delete this if you're sure you no longer want that history; reinstalling Vibeless later picks the directory right back up.

Every file Vibeless writes

Inside its own directories:

• ~/.vibeless/ — registry.db, auth.db (encrypted tokens), manifest.json, logs/, local-api.token
• <project>/.vibeless/ — vibeless.db, vibeless.version.db, hooks/ (per-agent envelope files)

In your projects, per installed agent — every entry marker-wrapped for surgical removal:

| Agent | Files touched | |---|---| | Claude Code | <project>/.mcp.json, hook entries in <project>/.claude/settings.json, envelope in .vibeless/hooks/, .gitignore lines | | Codex | <project>/.codex/config.toml, <project>/.codex/hooks.json, envelope in .vibeless/hooks/, .gitignore lines | | Cursor | <project>/.cursor/mcp.json, <project>/.cursor/rules/vibeless.md, .gitignore line |

The Cursor rules file is deliberately not gitignored — it carries agent-steering instructions the whole team benefits from. Only files holding per-machine credentials are gitignored.

Removing Vibeless entries by hand

If you'd rather not use the UI, the markers make manual removal safe:

• JSON files (.mcp.json, .cursor/mcp.json): delete the vibeless and _vibeless_managed keys under mcpServers. In .codex/hooks.json, delete the top-level _vibeless_managed key plus any hook entry whose command contains .vibeless/hooks/. In .claude/settings.json there is no sentinel — remove just the hook entries whose command contains .vibeless/hooks/ (or vibeless-hook, from older installs).
• TOML files (.codex/config.toml): delete everything between the # vibeless-managed-start and # vibeless-managed-end comment pair, inclusive.
• Markdown files (.cursor/rules/vibeless.md): delete everything between <!-- vibeless-managed-start --> and <!-- vibeless-managed-end -->, inclusive.
• Envelope files: delete <project>/.vibeless/hooks/<agent>-*.json, then the hooks/ directory if it's empty. They're machine-generated; nothing in them is worth keeping.
• .gitignore: remove the lines tagged with the # vibeless-managed comment above them.

Signing out without uninstalling

Sign out from the app's account menu. For a belt-and-braces local sign-out, deleting ~/.vibeless/auth.db invalidates the stored session on this machine.