Dashboard

The dashboard is an operator view of the same durable state exposed by the versioned API. Access depends on membership state and role.

Getting started

Until required setup completes, signing in leads to Getting started, an activation checklist. Tasuku keeps the checklist in sync with the server and checks repository readiness automatically; review activation stays in the operator's control.

Overview

Overview is the organization’s work control surface. It leads with successful review, research, and delivery runs completed over the last seven UTC days, followed by current work counts, AI usage and cost, work that needs attention, active work, upcoming automations, and recent outcomes. Review-specific findings and quality metrics remain in Analytics.

Work

Work is the durable record for engineering requests received through GitHub, Slack, or Linear. A work item keeps its source conversation, ticket, selected repository, plans, artifacts, agent tasks, and delivery links together. Open a work item to inspect its current state or act on a plan that is waiting for approval. Workflow-run events appear in the work item detail timeline and on the pull request detail view.

Pull requests and findings

Pull requests lists synchronized pull requests with repository, state, latest review, and finding counts. Search or filter by open, closed, or merged state.

The pull request detail view combines:

• GitHub pull request identity and state;
• the latest and historical reviews;
• line-level findings and validation state;
• stored GitHub conversation;
• related workflows and agent tasks;
• finding feedback and publication outcome.

Finding records remain available even when a comment limit prevented every candidate from being published.

Review analytics and CSV export

Review analytics aggregates findings and feedback so operators can inspect volume, severity, acceptance, false positives, and other feedback reasons over time. Filters constrain the displayed interval or repository. CSV export downloads the filtered review data for offline analysis; it does not mutate reviews.

Automations

Automations lists scheduled questions, research, and builds created from Slack. Open a schedule to inspect its interval, next run, failure count, active occurrence, and delivery destination. Operators can pause, resume, stop, or run now without losing occurrence history.

Repositories

Repositories synchronized from the GitHub installation appear here. New repositories start paused, and enabling one requires a current passing readiness check. Admins and super users can:

• enable or pause workflows;
• set review triggers, draft behavior, exclusions, strictness, and limits;
• set implementation pull requests to draft or ready;
• enable description regeneration and select a discovered template;
• choose category-specific runtime overrides;
• manage repository-scoped secrets;
• choose approved read-only secondary repositories.

The repository detail view reports whether each effective setting comes from the instance, the repository, or built-in defaults when no instance configuration exists.

Learnings

Learnings shows reusable guidance recorded from trusted review-thread conversations, with actor, repository, interaction, and approval provenance. A learning recorded this way is enabled immediately; admins and super users can disable or re-enable it here. See Feedback and learnings.

Usage

Usage monitors subscription allowances and metered AI costs across Tasuku.

Connections

Settings → Connections opens Connected services, where operators connect and inspect:

• the GitHub App used for repositories and trusted publication;
• Slack workspaces used for requests, approvals, results, and optional alerts;
• Linear workspaces used as ticket sources;
• Composio connected apps;
• the agent and sandbox connection status.

Integration credentials are not returned to the browser after storage.

Settings

Settings are grouped into:

• Workspace
  • General — organization name and the viewer's role.
  • Members — role and active-state management plus membership-change history.
• Connections
  • Connected services — the connection overview above, including Composio connected apps.
  • GitHub App — App identity and super-user reconfiguration.
  • Alerts — opt-in Slack operational alerts and their selected destination.
• Agent runtime
  • Coding agent — Codex, Claude, or OpenCode provider, model, default reasoning effort, and workload routing.
  • Conversation intelligence — the OpenAI-compatible conversation model configuration.
  • Sandboxes — Cloudflare Containers, Daytona, or external runtime host provider fields.
  • MCP servers — remote HTTPS HTTP or SSE transports and encrypted header references.
  • Skills — packaged agent instructions.
  • Instructions — shared custom instruction text.

Member management

USER can view product state. ADMIN can also manage repositories, runtime configuration, secrets, and learnings, and operate agents. SUPER_USER can additionally manage users, the GitHub App, Slack, Linear, artifact visibility, and Composio connected apps.

Disabling a member revokes all active sessions. Tasuku supports several super users but prevents disabling or demoting the last active one. See Members and access.