Tasuku

Tasuku documentation

Operate Tasuku, your self-hosted control plane for agentic engineering.

Your control plane for agentic engineering.

Tasuku turns requests from GitHub, Slack, and Linear into durable coding-agent workflows. It reviews pull requests, investigates and plans work, runs source-backed research, and—after human approval—implements changes inside isolated sandboxes.

The workflow system is the product boundary. GitHub supplies code and trusted publication, while Slack and Linear provide additional places to request, discuss, approve, and follow engineering work.

The central boundary

An agent can inspect repositories and produce bounded output, but it does not receive integration credentials or publish directly. Tasuku validates the output and performs the trusted write.

Mental model

Think of Tasuku as five connected parts:

  1. Work channels — GitHub, Slack, and Linear supply authenticated requests, conversations, and ticket context.
  2. Server — serves the dashboard and versioned API, verifies inbound events, and records durable workflow intent.
  3. Postgres — stores configuration, encrypted credentials, work items, queue state, reviews, events, tasks, feedback, and learnings.
  4. Worker — leases queued work, prepares repositories, controls the sandbox, validates artifacts, and publishes through trusted integrations.
  5. Sandbox — runs Codex or Claude against a bounded workspace using Docker, Daytona, or AWS Lambda.
GitHub / Slack / Linear → verified request → durable work
                       → isolated agent → bounded artifact
                       → approval and trusted publication

What Tasuku can do

  • Review pull requests when they open, reopen, become ready, or receive a push.
  • Plan GitHub or Linear issues and keep the selected GitHub code target explicit.
  • Implement an approved plan and open a draft or ready-for-review pull request.
  • Answer questions and run source-backed research from Slack threads.
  • Create private HTML research artifacts with authenticated browser previews.
  • Schedule recurring questions, research, and approved builds with Slack delivery.
  • Respond to explicitly mentioned pull request change requests, including inline context.
  • Generate pull request descriptions from a selected repository template.
  • Record work items, plans, findings, workflow events, task attempts, feedback, analytics, and approved learnings.

Start with the operating boundary

Before connecting a production organization, read Requirements, Architecture, and Security. Then follow Installation and Create the GitHub App.

Configuration model

Instance configuration supplies the defaults for agents, sandboxes, MCP servers, skills, custom instructions, and secondary repositories. A repository can override individual categories without copying or freezing the instance default. See Inheritance and overrides.

Secrets are stored separately from configuration. A repository secret with the same name shadows the instance secret for that repository. API responses expose metadata and fingerprints, never plaintext values.

Where to look next

Requirements

Infrastructure, GitHub, and agent prerequisites for running Tasuku.

On this page

Mental modelWhat Tasuku can doStart with the operating boundaryConfiguration modelWhere to look next