How feder-cr/dots works
invisible_dots runs persistent AI agents, each with its own QEMU computer, on the user's PC. The main workflow is a message or scheduled task arriving through a web, CLI, API, or channel interface; the host API and scheduler coordinate durable state and VM lifecycle; the guest engine reasons with a model, applies permission gates, and uses computer, file, and browser tools; results return as messages and events. The README documents several interfaces and capabilities not fully represented in sampled source, so those branches are shown at subsystem-directory level; links without direct source evidence are omitted.
Main entry points: engine.py Agent engine · server.ts HTTP API · channels/src Channel adapters · scheduler/src Scheduler
Components 26
Host control plane
- HTTP API
apps/api/src/server.ts - Scheduler
apps/scheduler/src - Host database
packages/database/src/database.ts - Event stream
packages/events/src/event-log.ts
Guest agent
- Guest relay
guest/dot-agentd/cmd/dot-agentd/main.go - Guest API
invisible_engine_dots/nanobot/dots/server.py - Agent engine
invisible_engine_dots/nanobot/dots/engine.py - Permission gates
invisible_engine_dots/nanobot/dots/permissions.py - Model provider
invisible_engine_dots/nanobot/dots/provider.py - OpenAI-compatible
invisible_engine_dots/nanobot/providers/openai_compat_provider.py - Guest state store
invisible_engine_dots/nanobot/dots/store.py - Computer control
invisible_engine_dots/nanobot/dots/computer.py - Browser identities
invisible_engine_dots/nanobot/dots/browser.py - Agent tools
invisible_engine_dots/nanobot/agent/tools - Guest automations
invisible_engine_dots/nanobot/cron/service.py
Computer runtime
- VM manager
apps/vm-manager/src/vm-manager.ts - Guest client
apps/vm-manager/src/guest-client.ts - QEMU VM
Messaging channels
- Channel adapters
packages/channels/src
Other components
- User
- OpenRouter model
- Websites
- Telegram
Connections 29
- User → Web UI: uses
- User → CLI: uses
- User → HTTP API: uses
- User → Channel adapters: messages
- Web UI → HTTP API: requests
- CLI → HTTP API: requests
apps/cli/src/api-client.ts - Channel adapters → HTTP API: delivers messages
- HTTP API → Scheduler: routes work
apps/api/src/server.ts - HTTP API → Host database: configures
- HTTP API → Event stream: streams events
apps/api/src/server.ts - Scheduler → Host database: persists state
- Scheduler → VM manager: controls lifecycle
- VM manager → QEMU VM: starts VM
- VM manager → Guest client: creates client
apps/vm-manager/src/vm-manager.ts - Guest client → Guest relay: calls guest
apps/vm-manager/src/guest-client.ts - Guest relay → Guest API: relays requests
guest/dot-agentd/cmd/dot-agentd/main.go - Guest API → Agent engine: serves engine
invisible_engine_dots/nanobot/dots/server.py - Agent engine → Guest state store: reads and writes
invisible_engine_dots/nanobot/dots/engine.py - Agent engine → Model provider: requests completion
invisible_engine_dots/nanobot/dots/engine.py - Model provider → OpenAI-compatible: selects provider
invisible_engine_dots/nanobot/dots/provider.py - OpenAI-compatible → OpenRouter model: sends prompts
- Agent engine → Permission gates: checks actions
invisible_engine_dots/nanobot/dots/engine.py - Agent engine → Agent tools: dispatches tools
invisible_engine_dots/nanobot/dots/engine.py - Agent tools → Computer control: controls computer
- Agent engine → Browser identities: uses identities
invisible_engine_dots/nanobot/dots/engine.py - Browser identities → Websites: browses
- Agent engine → Guest automations: runs automations
- Channel adapters → Telegram: connects
- Channel adapters → WhatsApp: connects