Terminal

Wrengle includes a built-in shell for working beside your notes, without leaving the app. Open it from the command palette, Voice Control, the persistent Terminal tab in the right panel's header bar, or Ctrl+`. Click the adjacent Agent tab whenever you want to go back to the assistant. Switching between Agent and Terminal keeps both your agent conversation and your running terminal sessions in place—neither one stops just because you looked away.

In the Run Terminal Command... palette mode, pressing Enter runs whatever command you've typed. Pressing Enter on an empty input does nothing, even if recent commands are showing—you have to select a recent command explicitly to run it.

When the Terminal itself is focused, Shift+Enter sends line-feed input, the same input as Ctrl+J. Programs such as Codex can use that to insert a newline without submitting the current prompt. The foreground program still decides what line feed means, so a regular shell may run the current command.

Launch profile

Terminal needs an open vault. Every new tab starts from your current vault's context and uses the per-vault profile you set in Settings → General → Terminal launch profile:

• shell path
• tab title prefix
• environment variable overrides

The shell itself is not sandboxed by Wrengle—it runs with your normal operating-system permissions. Environment overrides are local to Wrengle's terminal launch profile.

Tabs and restore

Wrengle stores terminal metadata locally, so it can restore your terminal tab layout for each vault. That metadata is a limited set of tab state—title, working directory, status, size, and timestamps. It lives in private app configuration, capped per vault, and you can clear it from the terminal metadata controls.

The terminal opens automatically once the panel becomes visible and its saved metadata is ready, unless you've suppressed terminal restore for that vault.

Appearance

Terminal background, text, muted text, borders, hover states, cursor, and selection all follow your active Wrengle theme. If a custom theme explicitly defines advanced terminal color overrides, those take precedence. ANSI colors used by prompts and command output stay controlled by your shell and terminal programs, not by Wrengle.

Output, search, and links

Terminal scrollback is controlled by Settings → General → Terminal scrollback. Wrengle also keeps a limited recent-command list, and it caps how much selected terminal output it captures before handing it to agent or workflow surfaces.

Terminal search uses the built-in terminal search UI. HTTP and HTTPS URLs shown in terminal output become clickable links that open through your system's browser opener; other URL schemes are ignored.

Privacy and safety

Commands run on your machine with the same practical access as your chosen shell. Terminal output stays local app state unless you explicitly copy it, select it for an agent or workflow, or run a command that sends data somewhere else yourself.

Workflow terminal nodes create command drafts, not commands that run themselves. A draft only runs once you press Run in Terminal, and orchestration does not sandbox it.

Voice Control runs a terminal trigger immediately, with no confirmation step—unlike a workflow draft. Saying it followed by a run command runs that command right away, in your open shell. It carries the same operating-system permissions and the same possible external side effects as anything you'd type directly, and voice Undo cannot reverse it.