Core Structure

• Electron desktop app (React + TypeScript)
• Codex-only execution (no multi-model, no routing, no fallback)
• App = UI + runtime + lifecycle + browser layer
• Codex = reasoning + device use + execution

Execution Mannequin

• chat:ship returns instantly → { conversationId, runId }
• Codex runs asynchronously (non-blocking)
• Every execution = remoted runId
• In-memory run registry tracks:
  • standing: working / accomplished / failed / cancelled
  • AbortController for cancellation

Lifecycle Occasions

• Express occasions:
  • RUN_START
  • streaming (textual content + instruments)
  • RUN_END (accomplished / failed / cancelled)
• Renderer is absolutely event-driven (not promise-driven)
• Cancellation targets particular runId

Persistence

• SQLite:
  • conversations
  • messages
• Codex thread IDs saved for session continuity
• Person message → saved instantly
• Assistant message → saved on success solely
• Cancelled runs → no assistant write
• Failed runs → optionally available partial persistence

Streaming

• Token streaming works from first message
• Shopper-side conversationId era prevents dropped streams
• Textual content + device exercise streamed incrementally

Browser System

• Embedded Chromium (Electron BrowserView)
• MCP + HTTP bridge exposes browser instruments
• Core capabilities:
  • navigate
  • snapshot (DOM)
  • click on / sort / scroll
  • extract textual content / hyperlinks
  • execute JS
  • screenshots
  • tab administration

Tab Mannequin (Deterministic)

• All instruments assist optionally available tab_id
• Refs saved per-tab (no world _active)
• Snapshot → motion sequences stay steady throughout tab switches
• Tab shut → ref cleanup

Execution Visibility

• Software exercise rendered inline with responses
• Auto-expanded outputs for significant outcomes
• Inline previews for fast inspection
• Errors clearly highlighted
• Output limits to guard UI

OS / Shell Capabilities

• Full shell entry by way of Codex CLI
• Can:
  • learn/write recordsdata
  • run instructions
  • handle processes
• App does NOT but present structured OS-level APIs
• Restricted impartial visibility into precise system modifications

Present Strengths

• Express run lifecycle (main improve)
• Deterministic browser automation (tab-scoped)
• Secure streaming system
• Persistent conversations + Codex session continuity
• Improved execution visibility

Present Limitations

• No true verification layer (trusts Codex output)
• No filesystem/browser state diffing but
• No persistent run historical past (in-memory solely)
• No app-quit course of cleanup (attainable orphan processes)
• Browser determinism will depend on Codex utilizing tab_id
• No structured OS-agent layer past shell entry

System Classification

• Not a chat app
• Not a multi-agent system
• Execution host for a single autonomous agent (Codex)