Quick tour
Five minutes of orientation. Everything here has its own page when you want depth.
The app at a glance
- Sidebar (far left, expands on hover): Repositories (the Dashboard), Explore (public repos), and Settings.
- Repo window: open a repo and this is where you'll spend your time - history, code, stats, and chat all live here.
Inside a repo
The repo window has three zones:
- The left panel - either the chat agent (ask anything about your repo's history, get cited answers) or built-in terminals (run your coding agents in up to four panes). Switch between them from the toolbar.
- The toolbar - two kinds of controls sit side by side. The view tabs (Home, Map, Stats, Editor) switch the content area between Merget's in-app views. Other buttons launch things outside that area: your coding tools (VS Code, Cursor, Claude Code, Codex, Copilot) open in their own apps, not as a view. The toolbar also holds bookmarks, repo settings, and - in manual commit mode - the Commit button.
- The content area - whichever view is active. If a repo isn't yet linked to a folder on your machine, this is where a Link folder button appears to connect it; once linked, the toolbar's Folder button opens that folder in your file manager.
The views
Four tabs switch the content area, in this order: Home, Map, Stats, Editor.
| View | What it's for |
|---|---|
| Home | A section containing the repos README and quick look at the most recent activity: the latest goals, prompts, and diffs as they land. It's a snapshot of what just happened, not the full history. |
| Map | The heart of Merget. Your repo's entire history as a graph: navigate it, check out any point, bookmark, fork, and merge. This is where you actually understand what happened and why, and it's the most developed view in the app. |
| Stats | Cost, tokens, model usage, and per-contributor breakdowns. |
| Editor | A file tree and code editor, including diff review for any step. |
Browser isn't one of these tabs. It's an embedded preview browser that opens on its own: from the Repository menu, or when you open a link from chat. More on the Browser.
The loop to remember
Work with your agent, and the latest changes show up on Home. The full shape of the project - every goal, fork, and merge - builds up on the Map, where any line of code traces back to the transcript behind it.
And if you're ever curious about the repo - why something exists, what you or a teammate changed, how some part came to be - just ask the chat. It can answer almost anything you'd want to know about the project's history.
Next: The repo window | Related: Mental model: how Merget works | Glossary