This is an early release preview. You may encounter bugs.
Octop logo
Unclaimed

Tool interface connectors memory

Octop

A smarter, self-hosted AI assistant — multi-user, multi-agent.

Built by Tencent

A 88/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About Octop.

Octop is a self-hosted AI assistant platform for households and small teams. One process serves a web dashboard, a CLI, instant-messaging channels, and cron automation, and every surface shares one control-plane database (SQLite by default, PostgreSQL optional). Conversations, workspaces, and credentials stay on the host machine.

Each user gets a team of "experts": specialized agents with their own workspace, model providers, channels, and cron jobs. Experts come from a built-in library or an expert market, can take one of 16 MBTI persona templates, and can be shared with other users in the same deployment along with shared pools of skills and sub-agents. AgentTeams (in beta) lets a coordinator expert schedule member experts on multi-step tasks.

Octop runs on the Octop Harness stack: Octop Harness handles model routing, tools, skills, and conversation checkpointing, Octop Gateway bridges IM platforms into one message flow, Octop Memory provides hierarchical recall with full-text search, and Octop Browser automates the web over CDP. Web UI, IM, and cron messages all go through one in-process processor instead of an external queue, and the process rebuilds its state from the database on restart.

It supports the Agent Client Protocol in both directions: editors such as Zed and OpenCode can use an Octop agent as an ACP server, and Octop can delegate coding tasks to OpenCode, CodeBuddy, Claude Code, and Codex behind permission gates. Model providers include OpenAI-compatible APIs, DashScope (Qwen), and Ollama, configured per agent.

  • Messaging channels: Feishu, DingTalk, QQ, WeChat, Telegram, Discord, WeCom, and more, alongside HTTP, SSE, and WebSocket APIs
  • Multi-user isolation: JWT authentication with an admin role, tool approval, shell command guardrails, and PII redaction
  • Connectors: a Tencent suite (Docs, Meeting, News) plus OAuth and an MCP gateway for external resources
  • Workspace backends: expert files on local disk, a Docker sandbox, PostgreSQL, or COS/S3, separate from the control-plane database
  • Knowledge base: RAG over uploaded documents, optionally shared within a deployment
  • Plugins: third-party plugins, with bundled plugins toggled from the dashboard
  • Terminal AI+: a browser-based interactive shell with AI-assisted command execution and troubleshooting
  • Browser AI+: headless Chromium sessions for web automation, screenshots, and remote browsing
  • Remote desktop: live screen and input control of the host on Linux, Windows, and macOS, with an isolated desktop on headless Linux
  • Desktop clients: native Windows, macOS, and Linux apps plus FnOS packages for NAS devices
  • Natural-language cron: scheduled jobs defined in plain language or slash commands that push results or run tasks

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with Octop.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get Octop →

Browse the catalog