Getting Started
Run Locally
Section titled “Run Locally”Use Zig 0.16 on Windows. For offline local development without the optional account service, set $env:MULTIPROMPT_NO_LOGIN="1" before launching. Configure remote host slots using the SSH aliases documented in CONTRIBUTING.md.
Build the stable binary:
zig build.\zig-out\bin\multiprompt.exeBuild the DEV binary:
zig build dev.\zig-out\bin\multiprompt-dev.exeStable and DEV use separate session files so experiments can be tested without damaging the normal workspace.
First Workflow
Section titled “First Workflow”- Start multiprompt.
- Use
Ctrl+Shift+1for a local CMD tab orCtrl+Shift+3for a remote tmux tab. - Use
Ctrl+Kto switch sessions, open workspace actions, or run Multibot commands. - Use
Ctrl+Shift+Oto open or reconnect the browser pane for the current shell. - Use
multiprompt-browser navigate "https://example.com"to drive the docked browser pane (zsbremains a compatibility alias).
Files Multibot Uses
Section titled “Files Multibot Uses”Multibot deliberately continues storing runtime state under the legacy %APPDATA%\ZigShell path so the rename preserves every existing session and browser binding.
| File | Purpose |
|---|---|
session.json |
Stable default workspace sessions |
session-dev.json |
DEV sessions |
session-{id}.json |
Named workspace sessions |
windows.json |
Stable workspace registry |
windows-dev.json |
DEV workspace registry |
inbox-*.json |
Live cross-window inbox snapshots |
panewin-*.txt |
Browser pane binding for multiprompt-browser |
browserwin-*.txt |
Edge window id binding |