Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/cline/kanban/llms.txt

Use this file to discover all available pages before exploring further.

Script shortcuts let you run any shell command from the Kanban navbar with a single click. Instead of switching to a terminal to run npm run dev or python manage.py runserver, you save the command once and run it from the UI whenever you need it.

​
What shortcuts are for

Common uses:
  • Start a local dev server (npm run dev, python manage.py runserver, cargo run)
  • Run your test suite (npm test, pytest, go test ./...)
  • Run a build (npm run build, make)
  • Run any kanban CLI command
Shortcuts run in the current project’s root directory, with the same environment Kanban inherited from your shell.

​
Creating a shortcut

1

Open Settings

Click Settings in the Kanban navbar.
2

Go to Script shortcuts

Select Script shortcuts in the settings panel.
3

Add a shortcut

Enter a name and a command, then save.
Name:    Dev server
Command: npm run dev
The name appears as a tooltip on the play button. The command is the exact shell string Kanban executes.
Once saved, a play button appears in the navbar for each shortcut. Click it to run the command.

​
First-run onboarding

If you have no shortcuts configured, Kanban guides you through creating your first one. The onboarding flow walks you through naming a command and saving it so the navbar play button appears right away.

​
Command execution

  • Commands run as shell strings (shell: true), so you can use pipes, redirects, and shell builtins.
  • The working directory is the project root.
  • Output streams to the terminal panel at the bottom of the Kanban UI.
  • Commands time out after 60 seconds.

​
Running kanban CLI commands

Script shortcuts can run any kanban subcommand, which lets you trigger Kanban automation directly from the navbar. For example: 
Name:    Create task
Command: kanban task create --prompt "Investigate build failure"

​
Managing shortcuts

Shortcuts are stored per-project in <repo>/.cline/kanban/config.json. Each shortcut has a label and a command. An optional icon field is also supported. You can edit this file directly if you prefer, but the Settings UI is the recommended way to manage shortcuts.
Removing all shortcuts from a project deletes the project config file entirely. This has no effect on global Kanban settings.

Build docs developers (and LLMs) love

Get started for freeTalk to us