@tasksmind in any channel it’s in to investigate a reported bug, review PRs, fix CI failures,
and open pull requests, without leaving Slack.
Installation
1
Add tasksmind to Slack
Install from your dashboard so the workspace links to your organization. Sign in, then go to
Settings → Integrations and click Add to Slack there. This runs the authenticated
OAuth flow, so no manual token configuration is needed. (Installing from a public
page can’t detect your organization, so it isn’t offered there.)The following permissions are requested:
2
Add tasksmind to a channel, before you connect it
The connect commands below run inside the channel they configure, so tasksmind has to be a
member of that channel first.Or open the channel name → Integrations → Add apps → tasksmind. For a public channel,
tasksmind adds itself when you connect it; a private channel must invite it (agents can’t
self-add). If you connect before it’s in the channel, nothing is saved, it’ll ask you to add
it first.
3
Link a channel to a GitHub repo
Link a repo to the current channel. tasksmind uses this repo as context for all agent commands
run in this channel.Repeat this in each channel to connect different repos. One channel can have one active repo.
4
Connect a customer-support channel (optional)
In a channel your customers post to, an org owner or admin maps it to an on-call project’s
repo. Reports here become incidents and fix PRs automatically. Customers only see friendly
updates, never code, logs, or stack traces.The repo must already have an on-call project in your dashboard.
5
Designate a dev channel for incident detail (optional)
In your team’s internal engineering channel (never your customer support channel), route the
full technical detail for incidents, root cause, file paths, PR links:The agent refuses to designate a channel already marked as a support channel, so this can’t
accidentally leak technical detail to customers.
6
Verify setup
Commands
Every command works as an@tasksmind … mention in a channel the agent is in, or in a DM with
the agent. Agent commands stream progress updates in a thread and may ask for approval before
taking action.
Setup
Status & info
Instant replies, no agent job started.Agent commands
These start a background job. tasksmind posts progress steps in a thread and asks for approval before committing or opening a PR.
Replies are posted in a thread on your message so the channel stays clean.
The approval & safety gate
Full detail on the four approval buttons, risk classification, and who can approve.
Enterprise & self-hosted
If your team uses a self-hosted or enterprise Slack App, configure the following URLs in your Slack App manifest under Event Subscriptions and Interactivity:app_mention, message.channels,
message.im.
Then invite the agent to your channels with /invite @tasksmind.
Troubleshooting
@tasksmind requests fail with a signature error
@tasksmind requests fail with a signature error
Cause:
SLACK_SIGNING_SECRET is missing or wrong in the agent configuration.Fix: Verify the signing secret matches the value in your Slack App → Basic Information →
App Credentials.@tasksmind mentions get no response
@tasksmind mentions get no response
Cause: The agent is not in the channel, or the
app_mention event is not subscribed.Fix: Run /invite @tasksmind in the channel. Then check Slack App → Event Subscriptions
and confirm app_mention is listed under bot events.connect github returns "workspace is not registered"
connect github returns "workspace is not registered"
Cause: The workspace was not installed via the OAuth flow, only a direct token was added.Fix: Re-install via the Add to Slack button on the Integrations page to complete the
OAuth install and register the workspace.
Agent returns "Repository appears to be empty or inaccessible"
Agent returns "Repository appears to be empty or inaccessible"
Cause: The GitHub token does not have access to the repository (common with fine-grained
tokens).Fix: Use a classic GitHub Personal Access Token (
ghp_...) with repo scope, or ensure
your fine-grained token explicitly includes the target repository.fix CI / review PR returns a 404 error
fix CI / review PR returns a 404 error
Cause: The GitHub token lacks read access to the repository, or the PR number does not
exist.Fix: Confirm the token has
repo scope and the PR number is correct. Merged PRs are still
accessible via the API.ping returns sdk=not loaded
ping returns sdk=not loaded
Cause: The tasksmind SDK module failed to import, usually a missing dependency or env
var.Fix: Check that
SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY are set in your deployment
secrets.Your setup guide
The full account-to-first-fix walkthrough.
API keys
Programmatic access for webhooks and custom integrations.