Embedded terminal (desktop)
In Code task type, the Windows desktop app embeds an xterm.js terminal bound to the workspace directory.
Looking for a full-screen terminal agent? That’s
zagens-tui— a separate binary, not this WebView panel.
Shortcuts & entry points
| Action | Shortcut / entry |
|---|---|
| Open and focus terminal | Ctrl+` (macOS: Cmd+`) |
| New terminal session | Ctrl+Shift+` |
| Files context menu | Open in terminal (cwd = that folder) |
Leaving the terminal Workspace tab keeps the panel mounted (hidden). Resizing syncs PTY size.
Shell & appearance
- Shell picker — default / PowerShell / pwsh / cmd (as installed)
- Optional PowerShell profile
- Theme, font size, copy on select, clear, search (
@xterm/addon-search) - Workspace-change banner with reopen here; exit badge when the process exits
When to use it
- Watch long-running agent commands
- Run commands yourself alongside the agent
- Tail build/test logs live
Agent automation still uses exec_shell / run_tests (sandbox + approval). This panel is a human PTY.
Office mode has no terminal — use read_office / write_office.
Safety
On Windows, shells and agent exec_shell are constrained by the Windows sandbox — plus execution policy (sandbox_mode) and approval dialogs.
Configure under sidebar Sandbox and Settings → System → Security.
Tips
- One workspace per repo so cwd stays correct.
- If output stalls, check runtime connection in the sidebar.
- For local frontends, pair with Built-in Browser and
.zagens/preview.json.
Related: Terminal TUI · Built-in Browser · Code mode · Workspace overview