Terminal

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

Opening the Terminal

Open the Terminal window from the chat dock Window launcher.

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

Interactive Shell

Unlike the dev server’s tool block in the chat (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 dev server tool block and the Terminal tab.

Queued Commands

When you run a project command from the toolbar, the command executes in the Terminal window. Tarsk appends its output to the terminal’s output lines.

Running a package.json script from the toolbar streams its output to the same terminal.

Auto-Open Behaviour

Tarsk leaves the Terminal window closed for queued commands. The activity bar’s Terminal button pulses for about 2 seconds when output arrives, and the session keeps running in the background whether or not you switch to it.

Tarsk opens the Terminal window on its own only while it installs a project’s setup scripts.

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

Dev Server — Run/Stop button and the chat tool block that streams server output
Project Commands — toolbar commands that may queue to the terminal
Git Operations — git workflow from the Git Ops menu