Terminal

Wrengle includes an embedded local shell for working beside your notes. Open it from the command palette, Voice Control, the persistent Terminal tab in the right panel's header bar, or Ctrl+`. Choose the adjacent Agent tab to return to the assistant. Switching between Agent and Terminal keeps both the active agent conversation and running terminal sessions in place.

The Run Terminal Command... palette mode runs the typed command when you press Enter. Empty Enter is inert, even when recent commands are visible; select a recent command explicitly to run it.

Launch profile

Terminal requires an open vault. New tabs start from the current vault context and use the per-vault profile in Settings -> General -> Terminal launch profile:

• shell path;
• tab title prefix;
• environment variable overrides.

Environment overrides are local to Wrengle's terminal launch profile. The shell itself runs with your normal OS permissions and is not sandboxed by Wrengle.

Tabs and restore

Wrengle stores terminal metadata locally so it can restore terminal tab structure for the vault. The metadata includes bounded tab state such as title, working directory, status, size, and timestamps. It is stored under private app configuration, capped per vault, and can be cleared by terminal metadata controls.

The terminal auto-opens when the panel becomes visible and saved metadata is ready, unless terminal restore has been suppressed for that vault.

Appearance

Terminal background, text, muted text, borders, hover states, cursor, and selection follow the active Wrengle theme. Advanced terminal color overrides take precedence when a custom theme defines them explicitly. ANSI colors used by prompts and command output remain controlled by your shell and terminal programs.

Output, search, and links

Terminal scrollback is controlled by Settings -> General -> Terminal scrollback. Wrengle also keeps a bounded recent-command list and limits captured selected terminal output before it can be handed to agent or workflow surfaces.

Terminal search uses the embedded terminal search UI. HTTP and HTTPS URLs shown in terminal output become clickable links and open through the system browser opener. Other URL schemes are ignored.

Privacy and safety

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

Workflow terminal nodes create command drafts. A command runs only when you press Run in Terminal for that draft, and orchestration does not sandbox the command.

Voice Control is different from a workflow draft: saying a terminal trigger followed by a run command executes it in the open embedded shell. The command has the same OS permissions and possible external side effects as typed terminal input, and voice Undo cannot reverse it.