Desktop runtime boots the worker
Electron owns desktop startup, attaches to or launches the local Python backend, opens the shared session, and exposes voice/text interaction without a phone-style pairing flow.
Open-source runtime under Kraitos
EmploAI
A local-first AI employee runtime for desktop execution, mobile command, and manager-controlled worker fleets.
The desktop owns real computer work. The cloud control plane handles identity, pairing, shared state, and routing. Mobile, Telegram, and future fleet dashboards become command surfaces for the same worker brain.
Desktop
Execution owner
Tools, files, browser, screen vision, shell, cron, and local runtime state.
Control plane
Identity and routing
Login, device records, pairing, websocket fan-out, shared state, and presence.
Fleet
Manager and workers
Task queues, reports, grants, locks, audit events, and worker supervision.
Current focus
Desktop-first runtime
Remote path
Public HTTPS/WSS control plane
North star
Fleet-scale AI employee OS
How it works
Execution stays local. Coordination moves through the cloud.
EmploAI is not a phone app pretending to be a desktop agent. The paired desktop is the machine that performs work; remote surfaces send instructions and receive synchronized state.
Control plane keeps surfaces aligned
The VPS control plane owns accounts, device records, pairing tokens, current session state, desktop presence, and websocket fan-out for mobile and desktop.
Mobile commands the paired desktop
Mobile v1 is text-first. It signs in, pairs to a desktop, displays mirrored sessions and task state, and sends turns through the control plane to the desktop runtime.
Fleet mode turns agents into workers
The long-term model adds manager and worker roles, enrollment codes, queues, structured reports, grants, locks, audit events, and manager-side verification.
Last major changes
The system moved from one desktop app toward a distributed agent runtime.
Remote control plane became the product path
Desktop and mobile now target a public HTTPS/WSS control plane for identity, pairing, shared state, realtime sync, and desktop presence instead of manual LAN backend entry.
Desktop app became the real local operator
The Windows path uses Electron around the existing renderer and Python backend. Runtime ownership lives in Electron main, with attach-or-launch startup and shared-session bootstrap.
Shared runtime reliability improved
Context compaction moved into the shared runtime so desktop and Telegram use the same memory pressure behavior, status display, and manual compact command path.
Manager/worker architecture was defined
EmploAI now has a concrete V1 fleet model: one account owns workers, managers dispatch tasks, workers queue and report, and grants/locks keep execution scoped.
Engineering blog
Notes from the EmploAI rebuild.
Short public notes for people following the open-source system as it turns into the first Kraitos project.
Why EmploAI is becoming an open-source system
Opening the repo makes the runtime inspectable: people can read the desktop, mobile, cloud, and fleet code while official builds remain assigned through Kraitos.
Desktop, mobile, and cloud now share one control story
The current architecture is simple to reason about: the desktop executes, the control plane routes, mobile commands, and shared state keeps every surface synchronized.
The fleet direction: from personal agent to AI employee OS
The `Other Computers` idea is becoming a real fleet dashboard with manager roles, workers, queues, structured reports, scoped grants, locks, and audit history.
Source and builds
Public code, controlled official releases.
The open-source repository is where the system can be read, forked, discussed, and improved. Official MSI/APK builds stay managed through Kraitos so testers receive the right bundle for the current runtime.