Download Beta
Guide contents

Overview

Getting started

Concepts

Using the app

Collaboration

Reference

Dashboard: your repositories

The dashboard is the first screen after sign-in: a grid of every repository you have access to. From here you create repos, import existing ones, and jump into any of them.

The repo grid

Each card shows the repository at a glance:

  • Name (namespace/name) with a visibility badge (public or private).
  • A status dot for repos linked to a local folder: pulsing green means Merget is actively watching the folder and committing, yellow means committing is paused, gray means the folder is linked but not being watched.
  • The description, contributor avatars (hover for names; a "+N" chip expands the overflow), the AI agents that have worked in the repo, and when it was last edited.
  • Cloud repos that aren't on this machine yet show Clone and or link existing actions right on the card.

Click a card to open the repo in the repo view. Right-click a card (or use its ⋮ menu) for more: reveal the folder in your file manager, change which folder the repo is linked to, start watching, clone or link, Edit collaborators (see Collaborators), open the repository's Settings, or unlink the folder.

Personal and organization views

The page title is a dropdown. Personal shows your own repos plus anything shared with you; below it, each organization you belong to gets its own view of the org's repos. You can also create a new organization from the same menu — see Organizations.

The search box filters by name, and the chips narrow the grid to All, Public, Shared (repos owned by someone else), or Private.

Creating and importing

New Repository creates a fresh repo: pick a name, an optional description, private or public visibility, and a folder on disk. The same dialog has tabs for ignore rules (files Merget should never commit) and a license.

The Import dropdown brings existing work in:

  • Import Local Merget — a folder on this machine that already has Merget history (for example, one the committing daemon set up automatically). Registers it with your account and links the folder.
  • Import Local Git — an existing Git repository on disk. Merget converts its commit history into goals, prompts, and steps and starts tracking the folder from here on.
  • Import from GitHub — connect your GitHub account, pick a repository and branch, and Merget clones and converts it.

While an import runs, a progress card sits in the grid showing the current phase; when it finishes, the card flips to ready and the repo behaves like any other. Imported and newly created repos are registered with your account and sync by default — see Sync & privacy for exactly what is transmitted and how to control it.

Under the hood

Git imports keep authorship: each Git commit's author carries over, so the contributor avatars on the card are real. What an import can't recover is intent: pre-Merget history has no prompts or transcripts, because nothing was committing when that code was written. New work in the repo gets full intent attribution from day one. See Merget and Git for how the two histories relate.

Next: The repo view · Related: Organizations · Explore · Your first repo