How it works

From words to software

Describe what you want. An AI agent writes the code, builds the app, and launches it in your workspace, whether that workspace is hosted in the cloud or running locally on your desktop.

1

Describe it

Tell the AI what you want in plain English. Be as detailed or as vague as you like -- the agent asks clarifying questions, makes smart defaults, and starts building.

Create a habit tracker with daily streaks, a heatmap calendar, and emoji icons for each habit.
I'll build a Habit Tracker with a streak counter, heatmap calendar grid, and customizable emoji icons. Let me start scaffolding the app.
Write package.json
2
Write src/App.jsx
Write src/HabitGrid.jsx
Write src/Calendar.jsx
Bash npm install
Bash npm run build
// 12/12 tests pass ✓

Agent builds it

The agent writes React components, installs dependencies, runs the build, and self-verifies with a simulation subagent. No templates -- every line of code is generated for your specific request.

3

Launch & iterate

Your app opens in its own native window. Don't like something? Say "make the cells bigger" and it rebuilds instantly. Use undo to roll back any change. Every iteration is a conversation, not a deployment.

Add a weekly summary view
Write src/WeeklySummary.jsx
Done. Weekly summary added below the calendar.
Make the cells bigger
Write src/App.css
Cells enlarged. Rebuilt.
Preview Undo
Habit Tracker
Weekly Summary
18 of 28 habits completed (64%). 3-day streak on Exercise.
4
Zoom Notetaker
Recording...
send()
Notes
Auto-capturing
Orchestrator
You: When a meeting ends, send the notes to my email app and draft a follow-up.
2 apps modified and rebuilt

Connect everything

The Orchestrator sees all your apps. One prompt connects them: "When a meeting ends, send the notes to my email app and draft a follow-up." It modifies both apps, wires the IPC, and rebuilds everything.

Two-tier agent architecture

Workspace agents build individual apps. The Orchestrator connects them all.

Top Level Orchestrator
Sees all apps · Writes across directories · Manages inter-app communication
The Orchestrator has access to every app directory. It defines message contracts between apps, adds sending and receiving handlers, rebuilds both sides, and runs simulations to verify the pipeline works end-to-end.
Workspace Notes
Scoped to its own directory
~/llumos/apps/notes/
Each workspace agent can only read and write files inside its own app directory. It builds React components, styles, installs dependencies, and runs npm builds autonomously.
Workspace CRM
Scoped to its own directory
~/llumos/apps/crm/
Workspace agents write React 18 with JSX, plain CSS, and Vite for bundling. They use window.llumos APIs for persistence and inter-app messaging.
Subagent Simulation
Runs test harness · Validates builds · Reports results
Every app includes a sim/ directory with a Node.js test harness. It validates file structure, tests business logic, verifies state management, checks persistence patterns, and runs edge case tests.
Subagent Simulation
Runs test harness · Validates builds · Reports results
The simulation harness runs with plain Node.js -- no browser needed. It catches broken imports, missing files, logic errors, and persistence bugs before the app ever opens.

Apps talk through a simple API

Every app gets window.llumos injected at runtime. No configuration required.

// Send a message to another app window.llumos.send('notes', { type: 'new-entry', content: '...' }) // Listen for messages window.llumos.onMessage((fromAppId, msg) => { ... }) // Shared key-value store await window.llumos.store.get('user-prefs') await window.llumos.store.set('user-prefs', { ... }) // Broadcast to all apps window.llumos.broadcast({ type: 'theme-changed', theme: 'dark' })

Direct Messaging

Send targeted messages between specific apps. The Orchestrator wires the connections; apps just call send().

Shared Store

Persistent key-value storage. Apps share reference data through well-known key conventions like shared:contacts.

Event Broadcasting

Fire-and-forget messages to all running apps. Useful for system-wide events like theme changes or status updates.

From creation to connection

Every app moves through a clear lifecycle. Iterate as many times as you want.

Follow-up prompt
Creating
Agent scaffolds files and structure
Building
npm install, npm run build, tests
Error
Ready
Build passed, app can launch
Running
Open in its own BrowserWindow

Built on solid foundations

Electron-native

Apps run in their own BrowserWindow. Full OS access, native menus, system notifications. Not sandboxed web tabs.

React + Vite

Every generated app uses React 18 and Vite. Hot module replacement during development. Instant builds.

Local Storage

Apps live at ~/llumos/apps/<app-id>/. Metadata in apps.json. Your filesystem, your data.

GitHub Integration

Push any app to GitHub with one click. Version control built in. Share your source code.

Ready to build your first app?

One prompt, one app, your workspace. Start in the browser now or run it locally when you want full desktop control.