Run the first review

After the first super user signs in, Tasuku opens an authenticated setup checklist. Newly synchronized repositories stay paused until their configuration passes readiness and an administrator explicitly enables reviews.

1. Finish required setup

Follow Finish setting up Tasuku after sign-in:

1. Install the GitHub App on at least one repository.
2. In Settings → Agent, connect a Codex or Claude subscription.
3. Confirm the sandbox. Docker is ready by default; choose Daytona or Lambda only when your worker requires it.
4. Open Repositories and turn on Reviews for the first codebase. Tasuku runs readiness as part of enabling it.
5. A passing check enables the repository automatically. A failed check keeps reviews paused and shows the configuration error.

For other ${secrets.NAME} references, add the value under Settings → Secrets. Tasuku stores secret values separately and returns only metadata and fingerprints.

2. Review the repository policy

Open Repositories and choose the synchronized repository. Choose which events trigger review:

• pull request opened
• reopened
• converted from draft to ready
• synchronized by a new push

Decide whether drafts are eligible. Set strictness, excluded authors, excluded paths, max_changed_files, and comment_limit. See Review policy. A paused repository, a repository without a passing readiness check, or one no longer accessible to the GitHub App cannot execute reviews.

3. Open or update a pull request

Use an event enabled by the policy. Tasuku should persist a workflow run, queue an agent task, prepare the repository at the pull request head SHA, and run the configured agent in an isolated workspace.

4. Verify the outcome

Check three places:

1. Pull requests shows the synchronized pull request and its latest review state.
2. Work shows requested work, its provider, execution progress, and any sanitized error.
3. Automations shows recurring or event-driven activity and its latest status.

On GitHub, Tasuku publishes inline findings and review text through the App identity. On later pushes it reconciles stable finding fingerprints and resolves GitHub threads that are no longer current.

If the run fails, start with Troubleshooting and correlate the delivery, workflow, task, attempt, sandbox, and provider identifiers.