Many agents stay visible
Each pane is a live worker with status, context, tool calls, and a prompt row. You can compare progress without opening separate terminals.
Open source command deck for parallel AI work
Run your agents, browser, files, and terminal from one surface.
DroidMaster is intentionally dense: it keeps multiple coding agents visible while you steer them with keyboard commands and voice prompts. The interface is not a chat box. It is an operations deck for builders running real work in parallel.
- 4+
- live work surfaces
- QWER / ASD
- keyboard-native control
- Local or cloud
- operator-owned runtime
Why the UI is dense
The job is not to hide complexity. The job is to keep it navigable.
Controls are physical
The keyboard model makes the dense layout operable. QWER and ASD move focus, scroll histories, and trigger voice input without mouse hunting.
Voice compresses commands
Voice notes turn long operator instructions into work items while keeping the active pane and resulting tool calls visible.
The simplified animation
One loop: move focus, speak intent, watch the workspace change.
The mock keeps only the parts that teach the mental model. The real app can stay loaded because the controls remain simple.
What ships with it
A real operating surface, not another agent chat wrapper.
Bring your own model tools
Use existing Codex or Claude Code workflows while DroidMaster provides the command deck around them.
Keep runtime ownership
Run locally or on a VPS and expose only the workspaces, credentials, and folders needed for the job.
Inspect the product as agents work
Keep browser state, file context, terminal output, generated media, and agent histories in the same visible workspace.
Install
Start from the terminal, then operate from the deck.
npx droidmaster web
FAQ
Frequently asked questions
Is the dense interface intentional?
Yes. DroidMaster is for operators running several AI workstreams at once. The design goal is controlled visibility, not minimal chat.
Do I need a new AI subscription?
No. Bring the model tools you already use, then run them through the DroidMaster operating surface.
Why keep the animation?
The animation explains the control model: move focus, record intent, insert work, and watch the workspace update.