Work channels

Open Integrations to connect the places where Tasuku receives and delivers engineering work.

GitHub

The GitHub App is the code and publication integration. It supplies verified webhooks, short-lived repository access, OAuth login, review publication, issue comments, Git objects, and pull requests.

Repositories synchronized from the installation start paused. Enable them and configure their review, automation, runtime, and repository-context policies before allowing workflows to run.

Slack

Choose Set up Slack, then create a Slack configuration token from Slack API apps. Tasuku uses the token once to create the app from its manifest and does not store the token. Finish the OAuth installation in the target workspace and invite Tasuku to channels where it should receive mentions or deliver results.

Slack can carry questions, research, implementation requests, plan actions, recurring schedules, and result delivery. Operational alerts are separate and remain disabled until an administrator selects an eligible channel under Settings → Alerts.

Linear

Choose Set up Linear to open Tasuku's reproducible app manifest. After creating the Linear OAuth app, save its client ID, client secret, and webhook signing secret in Tasuku. Secrets are encrypted at rest.

Linear issues are ticket sources, not implicit repository owners. Configure eligible GitHub repositories and an optional default for each Linear team. Users who approve or revise plans from Linear must link their Linear identity to an active Tasuku account with permission to operate agents.

Routing boundaries

Organization ticket settings choose GitHub or Linear as the default ticket provider. Slack channels may override that choice. Ticket-provider selection and repository eligibility remain separate policies, so a channel or Linear team cannot silently authorize work against an unrelated repository.

See Work items and channels for the request lifecycle.