Toolbox
The Toolbox is a menu in the HudShelf that opens three kinds of floating utility windows — a Markdown Editor, a Web Browser, and a Terminal — each draggable, each independently scrollable, and each also reachable by agents via MCP tools.
How It Works
Section titled “How It Works”Click the Toolbox button on the bottom HudShelf to open the Toolbox menu, then pick a window kind. Each window opens as a floating panel that lives over the World Map; you can drag it by its title bar, resize it, and close it. Multiple windows of any kind can be open at once — you can have two Markdown Editors and a Terminal side by side without any of them fighting for focus.
Toolbox windows aren’t tied to a specific project, building, or agent. They’re general-purpose tools, but agents can pop them open too: any agent with the right MCP tool can call ui_open_markdown_window or ui_open_html_window to send you a document to review, and the same window machinery renders the result.
Markdown Editor
Section titled “Markdown Editor”The Markdown Editor opens a .md file from disk (or starts with a blank buffer) and gives you a familiar editor with live rendering. Edits are tracked locally; the title bar shows an unsaved-changes indicator when there are pending edits. Closing a window with unsaved changes triggers a confirmation dialog — Save, Discard, or Cancel — so you don’t lose work by accident.
Agents that produce documents (PRDs, summaries, reports) often hand them off through this window: the agent writes the file, calls ui_open_markdown_window with the path, and the editor pops open ready for you to review.
Web Browser
Section titled “Web Browser”The Web Browser embeds a webview inside the window. The default landing page is DuckDuckGo, but you can type any URL into the address bar at the top to navigate. Standard back, forward, and reload buttons sit in the toolbar. The window supports basic browser interactions — clicking, typing, scrolling — though some sites that block iframing won’t render.
Agents can open arbitrary URLs in a browser window via ui_open_html_window, which is how, for example, an Issue Resolver might surface a Linear ticket inline without making you switch apps.
Terminal
Section titled “Terminal”The Terminal opens a real PTY-backed shell rendered with xterm.js. It behaves like your system terminal: scrollback, copy-paste, ANSI colors, and your normal shell prompt. The shell launches in your home directory by default, but you can cd anywhere. Closing the window terminates the PTY.
Terminals are useful when an agent recommends a command and you want to run it yourself, or when you want to inspect git state in a project without leaving the app. They’re general-purpose — there’s no Viberia-specific scripting.
Multiple windows and layout
Section titled “Multiple windows and layout”Every Toolbox window obeys the same drag-and-resize rules. Grab the title bar to move, the bottom-right corner to resize, the X button to close. Windows remember their last position within a session. They don’t dock or split — they’re free-floating overlays on top of the World Map.
UI Indicators
Section titled “UI Indicators”- Toolbox button in the HudShelf with the wrench icon.
- Menu chips for each window kind: Markdown Editor, Web Browser, Terminal.
- Window header drag affordance — cursor changes to a move icon over the title bar.
- Unsaved-changes dot in the Markdown Editor title bar.
- Address bar focus ring in the Web Browser when the address bar is active.
- Cursor blink in the Terminal indicates an active PTY.
- Resize handle at the bottom-right corner of each window.
- Window count badge on the Toolbox button if there are open Toolbox windows.
Use Cases
Section titled “Use Cases”- Read a PRD an agent just produced. When the Planner opens a markdown window with the draft, read inline without switching apps.
- Look something up while an agent is working. Open a Web Browser to search docs, GitHub issues, or a vendor portal.
- Run a one-off command. Use the Terminal to check
git statusin a project folder or run a build by hand. - Side-by-side review. Open two Markdown Editors and a Web Browser to compare a PRD, a reviewer’s notes, and the relevant external doc.
- Sanity-check an agent’s output. The agent claims it ran a script — drop into the Terminal and run it yourself.
Limitations
Section titled “Limitations”- The Web Browser embeds a standard webview. Sites that block iframing (some banks, some SSO providers) won’t load.
- The Terminal launches a shell with your default environment. Don’t expect any Viberia-specific tooling in it — it’s the same shell as your system terminal.
- Toolbox windows don’t survive a full app restart. Close and reopen as needed.
- Unsaved-changes detection in the Markdown Editor is local to the editor. External edits to the file while the window is open may be overwritten if you save afterward — the editor will warn but won’t auto-merge.
- Windows are floating overlays; they don’t tile or snap. For multi-window setups, position them by hand.
The Toolbox windows are the same window machinery agents use when they need to show you a document or page via ui_open_markdown_window and ui_open_html_window. If you see a Markdown or Browser window appear without your having opened it from the Toolbox, an agent (or the Chief of Staff via its right pane) has invoked the tool.