Marvis

Desktop app for working with git repos and their worktrees.

Keeps files, diffs, terminals, and review notes in one window per checkout. Run any coding agent in a terminal inside that checkout. Send review notes to OpenCode (or export as Markdown).

Platforms: macOS (Apple Silicon) · Linux (amd64 / arm64)
License: MIT

---

Why

Multiple worktrees → files and terminals get mixed across tabs and windows.

Review notes go stale when the code moves.

Copying feedback to an agent is tedious.

Marvis keeps each checkout isolated and attaches notes to specific diff lines. Notes that no longer match are marked outdated.

---

What it does

• Open a repo → Marvis remembers it and its worktrees
• Multiple checkouts side by side (main, feature/x, …)
• File tree + simple editor (for quick edits)
• Diffs (side-by-side or unified), mark files as viewed
• Notes on diff lines → draft → sent → resolved. Auto-detects outdated ones
• Multiple terminals per checkout; Marvis resets their splits and layouts on restart
• Optional OpenCode integration: sessions, prompts, send review rounds (test notes)
• Works with any CLI agent (Claude Code, Codex, pi, …) or none

Not an IDE. Not a GitHub/GitLab client. Not a plain terminal.

Architecture and data flow: docs/architecture.md.

---

Install

Download from the latest release.

macOS

# .dmg → drag to Applications
# First open may be blocked (ad-hoc signed):
xattr -dr com.apple.quarantine /Applications/Marvis.app

Debian / Ubuntu

sudo apt install ./Marvis_<version>_amd64.deb   # or _arm64.deb

Other Linux

chmod +x Marvis_<version>_amd64.AppImage
./Marvis_<version>_amd64.AppImage

Optional: install OpenCode if you want the built-in agent integration.

---

Quick start

1. Open a folder that is a git repo
2. (Optional) Add worktree from the menu
3. Select a checkout in the sidebar
4. Open Changes → click a line in a diff → write a note
5. Open a terminal in that checkout and run your agent
6. Send notes:
   • OpenCode → "Send to opencode"
   • Other agent → export Markdown and paste

---

Privacy

Everything stays on your machine. No telemetry. What an agent sends to a model provider is up to that agent.

---

Workspace data

Marvis keeps repository registrations, review notes and rounds, and workspace state in marvis.sqlite3, in the app-data directory for dev.marvis.workspace. Repository and worktree files stay where they are. Terminal processes cannot outlive the app, so Marvis clears terminal sessions and their layouts on startup; window size and UI state survive a restart.

Missing folders stay registered and are marked missing. If the path comes back, Marvis restores that registration with its metadata.

If a directory was moved or renamed, the Sidebar offers no way to point the old registration at the new path. Opening the new path creates a separate checkout, and the two histories do not merge. Keep the old registration if you need its notes.

Close missing removes the registration and everything attached to it, notes and rounds included. The confirmation says no files are deleted, and that holds for repository and worktree files only.

Marvis does not back up the database. Quit the app and make your own copy before confirming that action or deleting the file yourself.

---

Troubleshooting

Marvis does not start

Check the database first. Marvis does not migrate its schema. A build refuses a database stamped with a schema version it does not know, by name, rather than reshaping a file it did not write, and losing the repositories someone registered is worse than opening empty.

1. Read the log. It names the refusal.

   tail -n 60 "$HOME/Library/Logs/dev.marvis.workspace/Marvis.log"                        # macOS
   tail -n 60 "${XDG_DATA_HOME:-$HOME/.local/share}/dev.marvis.workspace/logs/Marvis.log" # Linux

2. Ask the database which schema it holds.

   DB="$HOME/Library/Application Support/dev.marvis.workspace/marvis.sqlite3"     # macOS
   DB="${XDG_DATA_HOME:-$HOME/.local/share}/dev.marvis.workspace/marvis.sqlite3"  # Linux
   sqlite3 "$DB" 'pragma user_version;'   # compare with SCHEMA_VERSION in src-tauri/src/persistence/mod.rs

3. Reset it. Quit Marvis first: a running copy holds the file, and a second launch is turned away by the single-instance plugin.

   pkill -f -i marvis                                # quit every Marvis copy
   cp -v "$DB" "${DB%.sqlite3}.$(date +%s).sqlite3"   # keep a copy before removing it
   rm -v "$DB" "$DB"-wal "$DB"-shm "$DB"-journal

The next launch writes a fresh schema and opens an empty workspace.

This removes repository and checkout registrations, review notes and rounds, viewed files, per-checkout UI state, and the saved window size and position. It does not touch repository or worktree files, ~/.marvis/config.yml (UI, terminal and editor settings), or ~/.marvis/tmp/code-reviews/ (review exports).

On Linux the log lives inside the database directory, so copy it out before removing anything.

---

Building

Source setup, build and artifact notes: docs/development.md.

Release and branch-gate checklist: docs/release-safety.md.

---

License

MIT