You lose track of workers
Several agents can be running, waiting, failing, or asking for input. A single chat transcript hides that operational state.
Open source command deck for parallel AI work
Stop losing context between agents, browser, files, and terminal.
DroidMaster solves the messy part of AI building: your agent, browser, files, terminal, voice notes, and tool output all live in different places. It brings them into one command deck so every action has visible context.
- 4+
- live work surfaces
- QWER / ASD
- keyboard-native control
- Local or cloud
- operator-owned runtime
The core problem
AI work fails when context is scattered across too many windows.
You keep switching surfaces
The browser shows the result, the terminal shows the process, files show the change, and chat holds the instruction. The work is split before it starts.
You lose causality
When tool calls, screenshots, prompts, and output are separated, it becomes harder to know which instruction caused which result.
Features by problem solved
Every feature exists to remove one source of friction.
Problem 01
The agent changes the app, but the browser is in another window.
You end up alt-tabbing between the prompt, the local site, screenshots, and terminal logs. DroidMaster keeps the agent and browser view in the same workspace so you can ask for a change while looking at the result.
Problem 02
Multiple agents become invisible background processes.
The deck gives each agent a pane with status, current context, tool calls, and an input row. You can compare workers without reopening terminals or scrolling through one giant chat.
Problem 03
Mouse-driven AI work is slow when the surface is dense.
QWER and ASD turn the deck into a physical control surface. Move focus, scroll histories, switch workspaces, and trigger voice without hunting for tiny controls.
Problem 04
Long prompts interrupt your flow.
Voice notes let you explain the change while staying inside the active workspace. The resulting prompt card appears in context, next to the work it affects.
Problem 05
Agent tools force you into one provider workflow.
DroidMaster wraps the tools you already use, including Codex and Claude Code, so the operating surface is separate from your model subscription.
Problem 06
Cloud convenience can make local trust unclear.
Run locally or on your own VPS, expose only the workspaces you choose, and keep credentials scoped to the runtime you control.
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.
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.