One window for every app you run. Multidex hosts modular apps, tools & skills on the embedded Dexus engine, wires them into one App API, and puts an AI agent at the deck that builds new modules — and drives the ones you have. In the neon window or straight in your terminal. Shared peer-to-peer — signed, verified, yours.
Every capability is an isolated module you command from one deck — install, launch, build, wire together and distribute without leaving the window.
Every module runs isolated on the embedded Dexus engine — own port, logs and lifecycle — and lands in one of three grades: full apps, atomic tools and multi-step skills.
Ask for “a real-time stock market monitor” — the agent writes, signs and installs it as a live module. Then keep asking: it answers, operates your modules and calls their capabilities.
Modules declare tools, events and skills once — in the manifest. The agent, neighbour apps and paired peers call them through one bus: schema-checked, permissioned, journaled.
A built-in MCP gateway projects every declared capability to external agents — Claude, IDEs, scripts — behind a Bearer token. Destructive calls still stop for a human yes.
One binary, four modes. Open the neon window, or add --console for a full pseudographic workspace — Library, agent chat, sharing and settings in plain text. --server runs headless, --daemon detaches.
The deck agent thinks on the built-in local engine out of the box — or your API provider, or a full coding agent: Claude Code, Codex, Cursor. CLI agents run in the terminal, GUI agents plug in via Multigen.
Publish modules as signed .qbox packages — one package carries Windows, Linux and macOS binaries — pull apps from other instances, or serve your own catalog.
Expose your catalog to the internet with a built-in tunnel — remote instances install your shared apps in one click.
Translation packs baked into the binary — switch instantly. Three shells: quardex neon, matte dark, calm light. Modules follow the theme live.
Every package is Ed25519-signed and SHA-256 verified on install. Releases are immutable, trust keys are baked into the binary. All of it enforced in the compiled backend.
Chat with the deck agent right inside Multidex — in the window or the terminal. Say what you want — the agent generates a complete module, signs and installs it, streaming every file into the chat as a live, collapsible card. Already installed? It calls that module's API instead: answer first, operate second, build only when asked.
The Library holds every installed module — icon, live status and port — grouped into Apps, Tools and Skills. Launch, configure and remove them — or open any app right inside the nexus.
A module ships its API in the manifest — tools, events and multi-step skills. Multidex turns that one declaration into a control surface for every caller: the deck agent, neighbour modules, the terminal workspace, external agents over MCP, even paired peers.
| Caller | Capability | Status |
|---|---|---|
| agent | notes.create | ✓ 12 ms |
| market-pulse | calendar.add | ✓ grant |
| mcp · claude | radio.play | ✓ 8 ms |
| agent | library.purge | confirm? |
| peer · office | media.scan | denied |
Under the deck runs Dexus — a process engine that supervises every module: spawn, port allocation, health, logs, autostart. The same engine sits behind the window, the terminal and the headless server. You see everything. You control everything.
| Module | Status | Port | PID |
|---|---|---|---|
| radio | stopped | — | — |
| media-manager | stopped | — | — |
| market-pulse | stopped | — | — |
| ferinar-steam | stopped | — | — |
The same binary that opens the neon window renders the whole nexus as pseudographics: pass --console and the deck is right there in your terminal — Library, agent chat, sharing, settings. Pseudographic boot logo included.
Pulled straight from the official Dex store. Install any of these into your nexus in one click.
Download Multidex and start building — and commanding — your own hub of apps. One download for your desktop: window, terminal, server and daemon included.