Documentation

Dashboard

Manage installation settings and read review findings in the dashboard.

On this page

Open your CroCode address and select Sign in with GitHub. App installation and user authorization are separate actions. You must authorize user access to use the dashboard.

Sessions last eight hours. Sign in again after expiry. CroCode keeps tokens in encrypted, httpOnly cookies. Browser code does not receive them.

Manage installations

Choose an installation from the overview or sidebar.
Open the Settings tab.
Turn reviews on or off.
Choose an enabled agent.
Choose a model from the list, or type a model name. Leave the model blank to use the agent default.
Optional: turn on the Weekly security digest and enter an HTTPS chat webhook URL.
Save the settings.

The model list shows the models that each agent reports. For Claude, it shows the aliases and the versioned models from the Anthropic Models API. The worker checks them at start and every 6 hours.

The Overview tab shows open pull requests and the state of their newest review. It also shows review totals, reviews per day, and findings by severity for the last 30 days.

The Agent health and usage card shows whether each agent CLI answered its last model list check in the sandbox. This check does not test credentials. The card also shows reviews, median agent time, token counts, and models for each agent. Token counts appear only when the agent CLI reports them.

Only the account owner or an active organization admin can change settings. The server checks this access again when you save. Repository config can override the installation’s agent and model.

Read a review

Open a review from the installation overview. The page shows the pull request state, branches, and size from GitHub. The Summary tab shows the agent summary, agent, model, and attempts. The Findings tab shows each finding in its diff. The Timeline tab lists every review of the pull request.

Status	Meaning
queued	Waiting for a worker.
running	A worker claimed the job.
succeeded	The review finished.
failed	The job failed.
cancelled	The job was cancelled, for example after a new push.
skipped	Review policy skipped the job.

A failed or cancelled review shows a plain reason and a next step. Open Error details to read the stored error.

An admin can select Cancel review on a queued or running review. A running agent stops within about 20 seconds. An admin can select Retry review on a failed or cancelled review when it is the newest review of its pull request. A retry starts with fresh attempts and does not post a GitHub review twice.

The Summary tab also shows agent time and the token counts that the agent CLI reported. The Static analysis tab lists the OpenGrep results that the agent received as hints. They can be false positives.

Run the dashboard locally

bun install --frozen-lockfile\ncp .env.example .env.local\nbun run dev

Set all six values in .env.local: GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, GITHUB_APP_SLUG, BETTER_AUTH_SECRET, BETTER_AUTH_URL, and CROCODE_API_URL.

The auth secret needs at least 32 characters. The auth URL must be an HTTP(S) origin with no path. Set the GitHub OAuth callback to that origin plus /api/auth/callback/github. Keep API calls and tokens in server code.

The public docs on GitHub Pages need no sign-in or GitHub credentials.