Using tasksmind Outside Slack

Slack is the default surface, not the only one. A CLI and a local agent for when you’d rather stay in your terminal.

The CLI

The tasksmind npm package gives you the same run/status/incidents primitives from your own terminal or scripts:

tasksmind run "checkout fails on Safari" --repo your-org/your-repo
tasksmind status <run-id>
tasksmind watch <project-id>

Command	What it does
`tasksmind init`	Set up the CLI for a project
`tasksmind run`	Start a fix run against a repo
`tasksmind status`	Check the status of a run
`tasksmind logs`	Stream logs for a run
`tasksmind incidents`	List and inspect incidents
`tasksmind replay`	Re-run a past incident
`tasksmind watch`	Watch a project for new activity
`tasksmind serve`	Run the local agent daemon
`tasksmind handoffs`	Manage local-agent handoffs
`tasksmind fixes`	List and inspect generated fixes
`tasksmind health`	Check connectivity to your account
`tasksmind update`	Update the CLI itself

The local agent

tasksmind serve runs a daemon on your own machine that claims fix “handoffs” from the cloud queue and works the fix locally instead of in a remote sandbox, useful when a fix needs something only your machine has access to.

tasksmind serve

There’s no MCP server yet. If your workflow depends on Claude Code, Cursor, or another MCP client talking to tasksmind directly, the CLI and local-agent daemon are the current way in, not an MCP endpoint.

The approval & safety gate

The same gates apply whether a run started here or in Slack.

See everything tasksmind can do

Back to the full use-case index.

Get Started

What You Can Do

Reference

Using tasksmind Outside Slack

The CLI

The local agent

The approval & safety gate

See everything tasksmind can do

​The CLI

​The local agent

The approval & safety gate

See everything tasksmind can do

The CLI

The local agent