<!-- Source: https://console.uubright.com/docs/setup-check/ -->
# Setup check

On the first run, uuBright Console looks at what the computer it runs on already has
for coding tasks, so you don't have to type it in: the repositories you've worked
in lately, the Git identities and push credentials each one uses, your GitHub CLI
accounts and a local Claude Code Router. **Needs you** shows a **Set up this
computer** card while something needs your attention; **Settings → Setup check**
(in the ⋯ menu, and under **Server settings**) shows the full list any time.

Only the owner token on a direct connection can open it, because it lists this
computer's folders, emails and accounts. A paired phone or a relay connection sees
an explanation instead.

## What it finds

**Repositories.** The ten Git repositories you committed to most recently, from:

- VS Code's, Cursor's and VSCodium's recent folders, and JetBrains IDEs'
  recent projects (macOS and Linux locations);
- `safe.directory` entries in your Git config;
- your home folder and the server's repository roots, four folders deep, for at
  most a few seconds (`node_modules`, `Library` and hidden folders are skipped; on a
  Mac so are Desktop, Documents and Downloads, which macOS would ask you about, so
  repositories there are found through your editor's recent list).

Each shows its path, `origin` remote (without any user name, password or token in
it), branch and last commit, with **Add** to make
it a project in the current workspace.

Reading a checkout runs no program its `.git/config` names (hooks, signature checks,
pagers, external diffs), and a checkout Git won't read because another user owns it
isn't listed.

**Git identities.** The name and email in the system and global Git config, each
`includeIf` block (for example `gitdir:~/work/` using a work email) and any
repository's own `user.email`. For every repository, the check shows which one Git
would use and why (global, `includeIf …` or this repository). Under **Git identity
for this workspace**, pick one: tasks in the workspace then commit with it.

**Push credentials.** For each repository, how a push would authenticate: an SSH
alias from `~/.ssh/config` with its key, your default SSH key, gh for HTTPS GitHub
remotes (when `gh auth setup-git` set it up), or another credential helper such as
`osxkeychain`, `manager` or `store`. Only key file names and helper names are read:
never a private key, a stored password or a token.

**Mismatches.** A repository is flagged when commits there would fail or go out
under the wrong name: no email at all, a personal email (Gmail, Outlook, QQ and the
like) on a company Git host, or a remote or SSH alias that names a company whose
email you use elsewhere, for example `git@github-acme:…` while committing as
`you@gmail.com` with `you@acme.com` configured for `~/work/`. An HTTPS remote with
no saved credential is flagged too.

**GitHub CLI.** Whether `gh` is installed and every account it is signed in to, per
host, and which is active.

**Claude Code Router.** Whether `~/.claude-code-router/config.json` exists, the host
and port it sets (default `127.0.0.1:3456`), and whether CCR answers its `/health`
check there. Nothing else from the file is read into the app, so provider keys stay
in CCR. When CCR is running, **Connect your model** offers it as the gateway.

## Sign in with GitHub

When gh isn't signed in, **Sign in with GitHub** on the GitHub item runs
`gh auth login --web` on the server as a device flow: the app shows the one-time
code and a link to github.com/login/device. Open it in any browser (your phone is
fine), enter the code and approve; the page notices and finishes on its own. The
code expires after 15 minutes, and **Cancel** stops gh.

In the Default workspace this signs in the server user's own gh, then runs
`gh auth setup-git` so Git pushes to github.com over HTTPS with that login, as gh's
interactive login does by default. In a named workspace with its own Git identity,
the login is saved in that workspace's own gh folder instead, like
`npm run workspace -- login-github ID`, and only that workspace's tasks use it. A
second account is fine: gh keeps several and the new one becomes active.

## The list

| Item | OK | Needs action | Skipped |
|---|---|---|---|
| Repositories | At least one added | Some found, none added | None found, or tasks run in containers |
| Git identity | Chosen for this workspace, or only one on the computer | Several and none chosen, or none at all | |
| Identity and push access | No repository flagged | A repository is flagged (see above) | Nothing found yet |
| GitHub sign-in | gh signed in to github.com | An HTTPS github.com remote and gh not signed in | No such remotes and no gh |
| Claude Code Router | Running and healthy | Configured but not running (`ccr start`) | Not installed |
| Zhipu GLM | A coding-plan key is saved and the last check passed | A key is saved and the last check failed | No key saved. Optional; tasks stay on Claude or Codex. **Add GLM key** opens Connect your model |

**Check again** reruns discovery; otherwise a result is reused for a minute.
**Not now** on the Needs you card hides it in that browser; the page stays under
Settings.
