Commands

Commands are custom shell commands attached to a project. They appear in the ⋯ More actions menu in the activity bar while a thread is selected, giving you one-click access to frequently used scripts.

Creating a Command

1. Open Settings → Project → Setup → Commands.
2. Click Add New 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
   • Command Line — the shell command to execute (e.g. bun test, npm run lint)
   • Relative Folder: optional subfolder of the project where the command runs
4. Click Save.

The command appears immediately in the More actions menu for all workspaces of this project.

Running a Command

Click the command in the More actions menu. Tarsk runs it in the active workspace’s directory, or its configured Relative Folder, and opens the Terminal dock panel for output. Click the same command again to stop it.

Commands run against the workspace’s own copy of the repository:

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

Package.json Scripts

The Scripts control lives in the activity bar’s ⋯ More actions menu and in the chat-input toolbar menu, and lists scripts from the project’s package.json. Click a script to run it in the current workspace’s directory.

Editing and Deleting

Reopen Settings → Project → Setup → Commands and click a command row to edit it. Each row shows a trash button for deleting the command. Changes take effect immediately across all workspaces.

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

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

Use the Run Command with the Run/Stop button for the project’s dev server (e.g. bun dev). Custom commands can run one-shot scripts or long-running processes; stop a running command by clicking its toolbar button. See Dev Server.