Opta Help

Operating documentation for deploying, governing, and scaling Opta across local and hybrid runtime environments.

Canonical activation model: establish runtime policy (local LMX or cloud), activate Opta AI, then execute through Opta CLI or Opta Code under daemon-governed operational state.

Docs pages now support platform-aware rendering. Switch between macOS and Windows views to see the exact commands, paths, and lifecycle controls for your environment.

Activate OptaCLI ReferenceUser Guides ↗Runtime + Connection SetupChat + Autonomous Modes

Getting Started

System orientation, operating model, and production fit

  • Installation
  • LAN Setup
  • First Session

Ecosystem

Runtime topology, interfaces, and ownership boundaries

  • Synergies
  • Change Impact

Accounts

Identity architecture, SSO posture, and access control

  • Auth
  • Sync
  • Troubleshooting

CLI Reference

Command surface, lifecycle semantics, and platform support

  • Chat & Do
  • Model Management
  • Sessions
  • Configuration
  • Slash Commands

Daemon

Control plane role, guarantees, and execution boundaries

  • Lifecycle
  • HTTP API
  • WebSocket Events
  • Troubleshooting

LMX

Local inference runtime architecture for Apple Silicon

  • Setup
  • API Reference
  • Model Management
  • Monitoring
  • Voice & Audio

Local Web

Browser control surface for local operations

  • Dashboard
  • Chat
  • Remote Access

Code Desktop

Desktop operator surface for session orchestration

  • Session Management
  • Daemon Controls

Browser Automation

Agentic browser control stack powered by Playwright

  • Tools
  • Recording & Replay

Status

Fleet status interpretation and incident context

  • Service Cards
  • Releases
  • Feature Registry

Security

Security architecture and trust boundaries

  • Permissions
  • Privacy
  • Guardrails

Developer Guide

Integration patterns for building on Opta Local

  • MCP Integration
  • Daemon Client SDK
  • API Authentication

Support

Operational answers for high-frequency setup questions

    Feature Status

    Current implementation state across Opta surfaces

      The Opta Local Stack

      Runtime strategy feeds Opta AI, then execution is orchestrated through daemon, CLI, and desktop operator surfaces

      Cloud models / Opta LMX local runtime# Runtime source
      │
      Opta AI# Optimizer core
      │
      opta daemon127.0.0.1:<port># Activation + session orchestration
      │ HTTP v3 REST + WebSocket streaming
      opta chat / opta tui / opta do# Opta CLI surface
      │
      Opta Code DesktopTauri desktop + daemon bridge# Opta Code surface