Console and the Assistant
Find your way around the dvoid console, its Files navigator, workspaces and the built-in Assistant.
dvoid-io/workbench · public
Start the console with dvoid console (bare dvoid opens it too). Its menu is generated from the
CLI's commands, so what you see depends on your machine: its harnesses, profiles and workstreams.
Selecting an action does not run it; you press Enter.
The menu
The sections are Quick agents, Workstreams, Estate (Repos), Setup and Advanced / Troubleshoot. Advanced / Troubleshoot → Health check lists account and machine problems with their fixes and a request you can copy to your admin; the header's "⚠ N issues" opens it too.
Menus and choice screens have a Search box: click it, or press / in a menu. Arrows browse the
matches, Enter opens one, and Esc clears the filter before it goes back. Ctrl+G, a left-click or a
right-click opens the organization and project dropdown where there is one; your current
workstream is first and marked here, and a repo's aliases share one choice. The shortcuts
along the bottom are clickable, and the active pane and editor are tinted.
The top strip and workspaces
Across the top: Commands (the command palette, Ctrl+G, or Ctrl+Shift+P where your terminal
reports Shift; never Ctrl+P or Ctrl+K), the Home and Settings tabs, then your workspace tabs, with
+ New after the last one shown and the rest behind +N ▾. o opens Console windows. Home holds
the command menu and context-first Layouts. New empty console starts separate work with its own
saved state.
A workspace tab's right-click has New workspace, Layouts… (the context and layout desktop), Rename, Close, Color… (which marks the tab and its companions) and the rest:
- Pop out workspace gives the workspace a window of its own. Its panes and Files move there while this console keeps running them; its tab here shows a card with Focus it and Bring back. Closing that window, or Bring back, returns everything.
- Move to console (or Move to new console) hands the workspace to another console. A confirmation lists what restarts there: shells in their folders (ending what runs in them), agents resuming their exact conversations, pages reopening, the Assistant starting over. An unsaved editor blocks the move.
A companion window shares its primary's workspace. Closing a companion returns its views; closing
the primary ends its shells, browsers and companions. Switching workspaces never closes a
companion: one whose workspace is not shown dims and offers Show in primary (click, or
Ctrl+G p).
Files
F3 toggles the workspace's one Files navigator. Its root is the workspace's context; changing a
shell's directory does not move it, and Back/Forward navigate within that root. Enter or Right
expands a folder; Left collapses it or selects its parent. Search filters the loaded branches; F2
switches between list and preview. Dotfiles are listed; the eye on Hidden (Ctrl+H) hides them.
Go ▾ holds the path field (Ctrl+L), Home, the workspace root and your bookmarks.
Right, Tab, Ctrl+E or a click on a file's preview opens it in a basic editor beside the tree; Shift+Tab returns to the tree and leaves the file open. Ctrl+S saves, Ctrl+Z undoes, and Esc closes after offering Save, Discard or Cancel. Ctrl+Shift+E opens your external editor and returns. The editor takes UTF-8 files up to 128 KiB and notices changes on disk.
The preview tab (an italic filename, or Welcome) is replaced by the next file you preview, never when it holds unsaved work. Double-click, Keep Open, editing or moving it keeps it. Split out makes a new group; Join moves a tab into a neighbouring one. Files cannot detach. In a popped-out workspace, its window has the Files.
The Assistant
Every workspace has its own Assistant (F4 there): its own conversation, draft and model, started when you first use it and ended when the workspace closes. It sees and reaches only that workspace's panes. Home's docked Assistant has no terminal or browser tools.
- The integrated terminal (F5) belongs to Home; no Assistant reaches it.
- Tab opens it and switches between chat and menu; on a short screen chat takes the body and Tab
shows the menu. F4 or
Minimizehides it, even mid-reply; the alien avatar brings it back. Ctrl+F orExpand / Restoreresizes it. - Enter sends; Shift+Enter or Alt+Enter adds a newline (Ctrl+J also works). The wheel or PageUp/PageDown scroll, Shift+Up/Down scroll a line, Ctrl+Home/End jump. Click the transcript to scroll with the arrows, or the composer to edit with them.
Show result / Hide resultexpands a tool's output; Ctrl+O shows the latest one. Esc stops a reply, otherwise collapses chat. Ctrl+N starts a new chat. F2 shows the menu preview when narrow.- The header's
Modelbutton (or Ctrl+L) lists the fleet models your own key reaches and switches between turns; your choice is remembered.
Choice chips sit above the composer: starters in an empty chat, then 2–4 next steps after each reply. Click one or press Alt+1–4 to send it; your draft is kept. On macOS, Alt needs your terminal's "Option as Meta" setting; clicking always works.
To copy, drag to highlight, then Ctrl+C or Copy (Ctrl+Shift+C where your terminal forwards it);
your terminal must allow clipboard writes. Ctrl+A or All selects the whole input. Right-click
(or Shift+F10) offers Select all, Copy, Paste and a short in-memory history of what you copied.
Get help with this drafts a chat message for you to review; it never sends by itself.
The Assistant reads freely, but every change it proposes shows the complete command above Decline and Allow once. Enter declines at first; Y allows once, N or Esc declines. Reading or typing into one of your terminals asks the same way, showing the lines or the exact keys. Drafts and chat survive navigation and terminal handoffs; quitting or logging out ends the chat.
Secrets, sign-in and enrollment stay with you. The secrets browser is private: the Assistant cannot look at, navigate or run anything there. Never paste a credential, a secret screenshot or clipboard contents into chat.
Agents in your panes
Claude Code, Codex and the rest run in terminal panes. An agent there reads where it stands with
dvoid console context (--json for data): the pane and workspace, the workstream, machine
class, sign-in and harness, and the commands that apply, each naming its guide. dvoid console docs
lists these guides and prints one by topic.
An agent may ask for a Browser pane beside its own with dvoid console browser. The console shows
you who asks, the URL and the identity (your remembered profile, a copy of one of your Chrome
profiles signed in as you, or a fresh one); nothing opens until you allow it, and a request you
decline or leave for two minutes is refused.
When something is wrong, start with dvoid console context, then the guide it names, then
dvoid doctor.
Requests waiting on your other machines
The Inbox also lists requests waiting on your other machines (On <host>). You can read the
conversation that led to one, but you can only answer it on the machine where it waits. To read it,
pair this machine with that console once:
- On that machine, open Settings › Paired devices › Pair a device…. It shows a 6-digit code for 5 minutes.
- Here, on its row, choose Pair to read (P) and type the code.
Each code allows one try: a wrong guess uses it up, so ask for a new one. What is read is redacted on the machine where the request waits, sealed so that only this device can open it, and never stored here. Settings › Paired devices lists the devices a machine answers, and Remove ends a device's access. Settings › Console › Answer my other devices turns answering off altogether.
Reopening and layouts
Reopening restores paths, browser pages and fresh shells, never previous jobs. An agent pane resumes its exact saved conversation; one that was never used starts fresh; one that cannot be verified asks you first, never guessing. Reopening a primary relaunches the companion windows of the workspace it shows; other workspaces' come back the first time you show them. A popped-out workspace reopens as its card, and its window opens when you first show that tab.
Save as layout exports a portable recipe you review first. It leaves out environment, credentials, running processes and monitor positions.
Secure laptop runbook (partner-secure-dev)
The day-0 steps for a Linux Mint laptop of class partner-secure-dev, what each one asks, and what to check afterwards.
Customizing: templates, playbooks, layouts, workspaces
Make dvoid start, arrange and run your work the way you want, for you alone or for your whole org.