! works the same way, but choosing a prompt runs it right away instead of filling the input. Save the prompts you use every day as macros, and routines like a code review or a session summary become a single short line. Use ? when you want to look first, and ! when you already know what you want.

Type ? followed by a few letters, for example ?commit, and a small list appears showing the prompts you have saved before, best match first. Choosing one puts its text into the input, so you can read it and change a detail before sending. It keeps you from typing the same long prompts over and over, and from trying to remember where you saved them.

• /dsi-prompts — Open prompt manager

The prompt manager is where your saved prompts live, so the ? and ! tricks above always have something to find. Search across everything you have kept, open a prompt to tweak its wording, flag the ones you use daily as macros, and send a keeper straight back into the input with one click. A prompt you were proud of today becomes a shortcut tomorrow.

• /dsi-plugins — Open plugin manager

Plugins add whole features to DSI — the plugin manager shows what is on the rack. A simple install tab lists what you can add, uninstall lists what is already on, and each row shows the plugin's state so you always know what is running. You never touch a config file to add or remove one.

• /dsi-skills — Open skill manager

Skills are the instructions your agents can follow, and this panel is their shelf. Browse what is installed group by group, tick the ones you want gone, and anything you remove can come back later. If a skill stopped being useful, it is two clicks away from being off the shelf.

• /dsi-terminal — Open a terminal session

One terminal is rarely enough when agents are working, so this one opens several, each in its own tab. Open a tab per task, keep a long build running in the background, and your tabs survive a page refresh — come back and they are still there. When a session has ended, the tab tells you instead of leaving you to guess.

The workspace explorer is DSI's window into the folder your agents are working in. Click the workspace chip at the top of a conversation — or a file name in one of the assistant's replies — and the panel opens with that file ready. A directory tree shows the whole project, every opened file keeps its own tab so several can sit side by side, and files your agents have changed are marked in the tree, so the work is visible at a glance. One click turns any tab into a before-and-after diff when you want to see exactly what was edited.

The Glass browser is a real browser living inside DSI. While you work, agents build and change DSI itself — plugins, panels, settings — and instead of telling you "it's done", they can prove it: the work runs right there in the Glass panel, and you watch it live. If a plugin breaks, you see exactly what broke with your own eyes instead of trusting a green test report — the browser is the receipt.

By default the glass browser's assistant (the MCP brain that lets an agent click and type in the browser) runs as its own separate helper process — if it fails, you lose only the glass panel. Adding --playwright-mcp moves that brain inside the DSI page server: one less background process and a faster start, but a brain failure can now touch the page server itself. DSI prints a banner saying so whenever you use the flag — drop the flag to go back to the helper process.

Example — a second, self-contained floor beside a live one (nothing on the running floor is touched):

DSI_PORT=5176 DSH_PORT=3081 GLASS_PORT=19515 npx @deepseek-insight/dsi@latest dsh --sync --playwright-mcp
# Page: http://localhost:5176 · host: 3081 · brain: http://127.0.0.1:19515/sse

Run DSI/DSH inside OrbStack (or any VM) while the Glass brain stays on your Mac — that is where the headed glass can be seen (Shift+Click opens a visible Playwright window, and only the host display can show one). The VM floor boots brain-less (no brain flag — never spawn a second, invisible brain) and exports GLASS_BRAIN_URL pointing at the host; OrbStack exposes the Mac to its VMs at host.internal:

# inside the VM — floor lives here, brain dials the host
DSI_PORT=5171 DSH_PORT=3081 GLASS_BRAIN_URL=http://host.internal:9515/sse npx @deepseek-insight/dsi@latest dsh --sync

sequenceDiagram
  participant M as host Mac
  participant V as VM floor (OrbStack)
  participant G as Glass brain (host 9515)
  M->>M: dsi dsh --sync with the brain flag — Glass lives here
  V->>V: dsi dsh --sync brain-less with GLASS_BRAIN_URL exported
  V->>G: preset dials the host stamp
  G->>G: Shift+Click opens a HEADED window on the host display
  V->>G: tabs, panels, viewport — driven over the wire

flowchart TD
  A[floor boots] --> B{GLASS_BRAIN_URL exported?}
  B -- yes --> C[dial that address — VM floor, host brain]
  B -- no --> D[dial 127.0.0.1:GLASS_PORT — same machine]
  C --> E[headed glass opens where the brain runs]
  D --> E

Second floors are fully drivable. At boot, a floor stamps its own addresses (DSI_UI, GLASS_BRAIN_URL) into everything it starts — so agents in that floor's conversations drive that floor's glass automatically, and the preset brain entry follows the stamped port. Nothing on the primary floor changes: without a stamp (a bare dsh web boot), the brain falls back to 9515 and the drivers probe 5175 → 5174 exactly as before. One conversation = one glass owner; the driver refuses to touch another conversation's glass, and a session busy in the live floor shows writer-held if you try to prompt it from the second window (watch it there, prompt it on its own floor).

The glass has two halves and each has its own stamp. The brain (GLASS_BRAIN_URL) is where agents dial in — the MCP endpoint. The chassis (GLASS_CHASSIS_URL) is where a Shift+click's visible window is born. By default both are "this machine" and nothing changes. When DSI runs on a machine with no screen (a VM) but your screens live on the host, stamp the chassis at the host and the window opens where you are looking:

# in the VM — the window is born on the host, the panel mirrors it
node bin/dsi-chassis.mjs --bind 192.168.1.9 --port 9525   # on the HOST: the chassis companion
DSI_PORT=5171 DSH_PORT=3081 GLASS_CHASSIS_URL=http://192.168.1.9:9525 pnpm dsi dsh --sync

The host-side companion (dsi-chassis) births each Shift+click glass on a fresh disposable profile — never your real Chrome profile — enforces the same one-conversation-one-glass rule on its side, binds only the address you name (never all interfaces), and bridges CDP back to the floor. When the stamp is set and the companion is down, the panel says so honestly instead of silently falling back to a screenless local launch; unset the stamp and every floor behaves exactly as before.