Download Beta
Guide contents

Overview

Getting started

Concepts

Using the app

Collaboration

Reference

Organizations

Your first repo

Five minutes from sign-in to watching history write itself.

1. Add a repo on the Dashboard

The Dashboard is where repos live. Top right:

  • New Repository - start fresh.
  • Import - a menu with three ways to bring in an existing project:
    • Import Local Git - point at a folder with a .git/ history; Merget converts the commits into steps (authorship preserved; no prompt history for the past, since Git never recorded any).
    • Import Local Merget - link a folder that already has a .merget/ history.
    • Import from GitHub - connect GitHub and pick repos to import.

Large imports process in the background; a progress card on the dashboard tracks each one until it's ready.

2. Your agents are already set up

There's nothing to configure here. When you installed and launched Merget, it added its plugin to whichever supported coding agents it found on your machine - Claude Code, Codex, Cursor, GitHub Copilot - so their sessions get committed. The plugin is installed globally, once, not per repo, and only Merget's plugin is added - never the agents themselves.

Installed a new agent since? Run merget plugins install to add Merget's plugin to it (more in Troubleshooting).

3. Work - and watch

Open the repo and start a session with your agent - in your usual terminal or IDE, or right inside Merget's built-in terminals. Ask it to build something real.

Then open the repo's Map view. Within a short while your session takes shape there: a goal appears on the map, and opening it reveals the prompts you sent nested inside. Each prompt carries the prompt text and the changes it produced; expand one to see its steps - each a generated headline and description over a slice of the diff.

(The Map is the visual history of your work, and the best view for a solo project. The Home view is an activity feed that's more useful once you have collaborators.)

What to look for: the Map going from empty to a named goal (like "Set up the project scaffold") with your prompt inside it, which you can expand to see the steps and the diff - without you having written a single commit message.

There may be a brief "pending" stage while Merget's processing service organizes the raw activity into goals and prompts - that's normal. See How Merget works.

4. Ask why

Open Chat and ask your repo anything - "why was this added?", "what changed in the login flow?" - and it answers from your history, with links to the prompts and changes behind each answer.

You can also go straight to the source: every prompt on the Map shows what you asked and the changes it produced. That's the core loop of Merget - every change knows where it came from. Chat answers carry citations, click any and move right to the source. From here, take the quick tour to see the rest of the app.

Next: Quick tour | Related: Dashboard | How Merget works | Your agent and Merget