Onboard a repo

There's no explicit "add repo" step for everyday use. Any git repo is indexed the first time you run a repo-aware rt command inside it:

bash

cd ~/code/my-repo
rt cd                # or rt run, rt code, anything repo-aware

On that first invocation rt will:

1. Derive a stable identity for the repo from git config --get remote.origin.url. A repo with no origin gets a path-based identity instead, so local commands still work.
2. Record it in the repo index inside ~/.mattstack/rt/state.db.
3. Create a per-repo data directory under ~/.mattstack/rt/repos/.

All of this lives under ~/.mattstack/, never inside the repo itself. Onboarding never adds files, config, or commits to your project.

Background tracking

The daemon refreshes data in the background for the repos you grant tracking:

bash

rt repos register . --track live    # index this repo and grant background tracking
rt daemon track                     # list tracking, or change a repo's level: live, poll, or off
rt repos prune                      # drop index rows whose repos no longer exist on disk

An untracked repo fetches its data on demand. Once a repo is tracked, merge-request data refreshes every 5 minutes. See Daemon for what each tracking level does.

Optional per-repo config

Command	When you need it
rt repos register --track	You want the daemon refreshing this repo in the background
rt hooks	The repo uses husky and you want a quick on/off toggle

Accounts and preferences

The accounts rt uses (your team's GitHub or GitLab, Linear, and whatever else the team declares) are connected in the setup checklist and apply to every repo. Reopen the checklist with Setup status… in the menu bar app to connect or rotate one. See Install.

Preferences such as which events fire native macOS notifications (rt.notifications) are settings: change them on the console's settings page, or with rt settings set.