Commands

Commands are custom shell commands attached to a project. They appear as buttons in the toolbar at the top of any thread belonging to that project, giving you one-click access to frequently used scripts — linting, test runs, code generation, deployments, or anything else.

Creating a Command

1. Open the Commands dialog: click the Commands icon in the top toolbar (or open it from Project Settings).
2. Click Add Command.
3. Fill in the fields:
   • Name — the label shown on the toolbar button (e.g. “Run Tests”)
   • Icon — choose a Lucide icon from the picker to visually distinguish the button
   • Command Line — the shell command to execute (e.g. bun test, npm run lint, ./scripts/generate.sh)
4. Click Save.

The command button appears immediately in the toolbar for all threads of this project.

Running a Command

Click the command button in the toolbar. Tarsk runs the command in the context of the active thread’s directory — so file paths, environment, and working directory are specific to that thread. The output streams in the output panel below the chat.

Commands run against the thread’s own copy of the repository, which means:

• Running tests in thread A and thread B simultaneously produces independent results
• Changes made by the agent in a thread are visible when the command runs in that thread

Editing and Deleting Commands

Open the Commands dialog again:

• Click the Edit (pencil) icon next to a command to modify its name, icon, or command line
• Click the Delete (trash) icon to remove it

Changes take effect immediately across all threads.

Command Use Cases

Use Case	Example Command
Run tests	bun test
Lint code	bun run lint
Type-check	tsc --noEmit
Format code	prettier --write .
Build for production	bun run build
Run a custom script	./scripts/seed-db.sh
Open API docs	open http://localhost:3000/docs

Tip

Commands are great for verifying agent work. After the agent makes changes, click your test command to confirm they pass — without switching to a terminal.

Relationship to the Dev Server

Commands are distinct from the Run Command used by the Run/Stop button. The Run Command is a long-running dev server process (e.g. bun dev). Commands are one-shot scripts that execute and return output. See Dev Server for details on managing the long-running server.