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”

Open the Terminal window from the chat dock taskbar (dimmed terminal icon or + → Terminal).

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 window. Tarsk opens the Terminal panel automatically so you can see the output.

package.json scripts from the toolbar also stream output to the terminal without switching away from your current window.

Auto-Open Behaviour

Section titled “Auto-Open Behaviour”

Tarsk opens the Terminal window when a queued project command runs (for example, from the project commands toolbar). You can switch back to Chat or another window at any time. The terminal session keeps 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”