OpenOcta (Octopus)
China's first open-source personal desktop AI agent — double-click to install, run locally, starts in milliseconds, data stays on your machine.
Evidence: README claims local-first and data stays on machine, but no permission model, user confirmation, data flow transparency, or sensitive data handling details are provided. Dependency security, external effects, rollback, and source attribution are undocumented. Deductions: all trust criteria lack evidence; claims alone are insufficient.
Evidence: README is consistent, but no error handling or failure message documentation. Dependency availability only mentions Go 1.24+ and Node≥18, without specific dependencies or versions. Deductions: self-consistency has basic description but no details; dependency availability incomplete; failure messages no evidence.
Evidence: Clear target users (office, IT ops, marketing) and scenarios, multi-platform installers, good environment fit. Capability boundaries only mention built-in tools and MCP, not detailed. Trigger precision undocumented. Deductions: capability boundaries and trigger precision lack specifics.
Evidence: README well-structured, install notes, documentation links, examples and FAQ (partial), Apache-2.0 license clear. Naming stability not mentioned, known limitations missing, versioning changelog not provided, maintenance responsibility only community. Deductions: naming stability, known limitations, versioning changelog, and maintenance responsibility insufficient evidence.
Evidence: Output usability has UI screenshots and examples, marginal value has comparison table, cost-benefit has lightweight claims. But no actual performance data or user feedback. Deductions: output usability evidence limited, cost-benefit based on claims only.
Evidence: Claims in README have some doc links (architecture, config), but no tests or independent verification. Cross-source corroboration missing, facts vs inferences not clearly separated. Deductions: lack of verifiable test results and independent sources.
- Trust criteria lack evidence, especially permission model, user confirmation, and data flow transparency.
- Dependency security not mentioned; dependency list should be reviewed.
- Known limitations and versioning changelog missing, may affect maintenance decisions.
What does this agent do, and when should you use it?
OpenOcta is an open-source, personal desktop AI agent developed entirely in Go by a Chinese team, licensed under Apache-2.0. It offers a complete desktop client that installs in about 30 seconds, runs with low memory usage, and is suitable for 24/7 operation. Core components (Gateway, Agent, Channels) are natively implemented in Go, with the Control UI embedded in a single binary, eliminating the need for Node.js or Python in production. It supports remote control via WeChat, WeCom, DingTalk, and Feishu, integrates built-in tools plus MCP protocol and a skills marketplace, and features a four-tier memory system with a local Knowledge Vault for autonomous evolution. The installer is around 30MB and supports Windows, macOS, and Linux, with data stored locally for intranet deployment.
OpenOcta runs an agent runtime locally that parses user-described tasks and executes operations via built-in tools (file system, terminal, browser) and MCP servers. It calls LLMs (e.g., Moonshot, DeepSeek, Qwen, Doubao) for dialogue and task execution, and accepts commands through IM channels (WeChat, WeCom, DingTalk, Feishu). It includes a skills library (766+ skills), a digital employee marketplace (e.g., Zabbix, Prometheus, MySQL DBA), and an Obsidian-compatible knowledge base supporting semantic retrieval. Users interact via the Control UI or configure via a JSON config file. Developers can trigger tasks from CLI: ./openocta agent -m "...".
- Office workers: Let AI summarize weekly email key points and generate a weekly report, reducing repetitive work.
- IT ops: Have the agent monitor logs around the clock and suggest remediation, shifting from firefighting to prevention.
- Marketers: Quickly produce Xiaohongshu copy based on product materials for multi-channel promotion.
- Knowledge managers: Search local knowledge base for specific standards and auto-summarize, retaining team expertise.
- Developers: Ask the agent to read a repository's README and list pending changes, aiding code review and project maintenance.
What are this agent's strengths and limitations?
- Go single-binary runtime with ~30MB installer and low memory footprint, suitable for always-on operation.
- Local-first: data and memory stay on the machine, supports intranet deployment, no Node/Python needed in production.
- Integration with Chinese IM platforms (WeChat, WeCom, DingTalk, Feishu) and domestic LLMs.
- Four-tier memory + L4 Evolution + Knowledge Vault provide autonomous personalization.
- As a new project, community size and ecosystem maturity may lag behind projects like OpenClaw.
- Desktop-focused; cloud or team collaboration deployment may require custom extensions.
- Documentation and examples are primarily in Chinese; English support is limited.
- Some features (skills marketplace, digital employee marketplace) depend on online resources, which may be restricted in offline environments.
How do you install or deploy this agent?
Download the installer for your platform from GitHub Releases or the openocta.com download page: Windows .exe, macOS .dmg, Linux .deb/.rpm/.tar.gz. Double-click to install (about 30 seconds) and open the desktop client.
How do you use this agent?
After installation, configure an LLM API key: open the client's 'Model' tab or follow the first-run configuration wizard to enter the API key and select a model. Alternatively, edit the config file at ~/.openocta/openocta.json (Linux/macOS) or %APPDATA%\openocta\openocta.json (Windows). Restart the client and describe tasks in the 'Messages' tab. Developers can run from source: make build && ./openocta gateway run, then access the Control UI at http://127.0.0.1:18900.
How does this agent compare with similar options?
Compared to OpenClaw, OpenOcta emphasizes personal desktop: double-click install, built-in Control UI, Go single-binary runtime, whereas OpenClaw is Node.js-based with CLI deployment. Compared to Hermes (Python/CLI), OpenOcta is fully Go-implemented with built-in knowledge base and evolution. It also adapts to Chinese IM and domestic models.
FAQ
Does OpenOcta require internet?
Do I need programming experience?
Which LLMs are supported?
Where is data stored?
~/.openocta or %APPDATA%\openocta.