Download v.0.
Guide contents

Overview

Getting started

Concepts

Using the app

Collaboration

Reference

Sign in and set up your account

The first thing Merget asks for is an account. That's deliberate: every goal, prompt, and step in your history is attributed to a person, so Merget needs to know who you are before it commits anything. (What an account means for your data: Sync & privacy.)

Sign-in options

Three ways in, and all of them also create your account if you don't have one yet:

  • Email - enter your email and password, then confirm with a one-time code sent to your inbox.
  • Google or GitHub - one click, approved in your browser. This uses OAuth, a standard way for one app to verify who you are through another without sharing your password. The first time, Merget creates your account automatically; there's no separate sign-up step.

Completing your profile

After your first Google or GitHub sign-in, Merget asks you to set up your profile: a username, a display name, and (optionally) an avatar. Your display name and avatar are what teammates see on the Map and in statistics.

The onboarding questions

A couple of quick questions about you. It takes under a minute.

Shortly after you sign in, Merget asks whether to auto-track your coding sessions: automatically set up committing whenever you start a session in a supported agent. Saying yes is what makes the "it just commits" experience work. You can change your answer anytime in Settings.

Under the hood

When you sign in with Google or GitHub, Merget receives only your email - never your password. Deleting your account later hard-deletes your personal repos; see Sync & privacy: Retention.

Next: Your first repo | Related: Sync & privacy | Settings