Skip to content
Tarsk

Terminal

Every thread has a Terminal tab — a full interactive shell scoped to that thread’s working directory.

Opening the Terminal

Section titled “Opening the Terminal”

Click the Terminal tab at the top of the thread view (alongside Chat, Files, Review, Browser, and Tasks).

The terminal starts in the thread’s directory, so git status, npm test, and other project commands work without changing directory first.

Interactive Shell

Section titled “Interactive Shell”

Unlike the dev server Output panel (which shows read-only stdout/stderr from the Run button), the Terminal tab is fully interactive:

  • Type commands and see live output
  • Use your shell history (up/down arrows)
  • Run any command available in your system shell

See Dev Server for the difference between the Output panel and the Terminal tab.

Queued Commands

Section titled “Queued Commands”

When you run a project command from the toolbar, the command executes in the Terminal tab automatically. Tarsk switches to the Terminal tab so you can see the output.

package.json scripts from the toolbar also stream output to the terminal, but they do not auto-switch tabs. A notification dot appears on the Terminal tab instead.

Notification Dot

Section titled “Notification Dot”

If a command runs in the terminal while you are on another tab, a notification dot appears on the Terminal tab label. Switch to Terminal to view the output; the dot clears when you open the tab.

Auto-Switch Behaviour

Section titled “Auto-Switch Behaviour”

Tarsk automatically switches to the Terminal tab when a queued project command runs (for example, from the project commands toolbar). package.json scripts show a notification dot but leave you on the current tab. You can switch back to Chat or another tab at any time — the terminal session stays running in the background.

Typical Uses

Section titled “Typical Uses”
  • Inspect files: ls, cat, head
  • Run migrations: bun run migrate
  • Check git state: git status, git log
  • Install a package the agent referenced: bun add some-package
  • Run tests manually after agent changes
Section titled “Related”