Terminal

Boltise has a proper terminal, not a command box. It runs a real shell with a real PTY, so interactive programs, colours, progress bars and Ctrl+C all behave the way they do anywhere else.

Open it with Ctrl+`. On Windows it starts PowerShell; elsewhere it uses your login shell.

Several at once

Click New Terminal to open more. Each keeps its own working directory and scrollback, and they stay alive when you hide the panel — a build you started does not die because you went back to the editor.

Terminals start in your project folder.

Inline AI assist

Press Ctrl+Enter in a terminal to ask for a command in plain English.

The prompt takes the visible terminal output as context, so it can answer against what actually just happened — a failed command, an error message, an unfamiliar output format. The suggestion streams in, and you choose: run it, copy it, or dismiss it. Nothing runs until you say so.

This is the fastest path for the commands you use twice a year: git surgery, ffmpeg flags, finding what is holding port 30120.

The assistant can read your terminal

The AI panel can read terminal output as a tool, which means you can paste nothing and still ask “why did that fail?”. It sees the same scrollback you do.

It can also run commands, but that is the most heavily guarded thing it does — every command shows an approval card first, and a hard floor refuses catastrophic operations regardless of what you approve. See Approvals & Safety.

Scrollback

Terminals keep 3,000 lines by default. That is a deliberate trade: two always-open terminals each pre-allocating a 10,000-line buffer is a memory cost most sessions never use.

If you need more, set boltise.terminal.scrollback in local storage to any value between 1,000 and 10,000. A settings field for it is still to come.

Terminal or server console?

They are different panels and it is worth knowing which you want:

• The Terminal is your shell. Use it for Git, package managers, scripts, and anything you would normally run in a command prompt.
• The Console is FXServer’s own output, with an input that sends server commands. See Server Management.

Starting your server from the Terminal instead of the Console works, but Boltise then does not own the process — the profiler, live server tools and resource controls all need a server Boltise started itself.