Octop is Tencent Cloud’s MIT-licensed, self-hosted AI assistant platform: one Python process serves a web dashboard, a CLI, native desktop clients, and eight-plus IM channels for a multi-user household or team, and each member gets their own team of specialized “experts”.
Octop is what the assistant-runtime wave looks like when an incumbent vendor builds it: multi-user by default, Tencent-enterprise-IM first, and composed from four small sub-repos (harness, gateway, memory, browser) instead of one monolith, at about 9k stars within three months of launch.
What it is #
A Python 3.12+ FastAPI application that runs as a single restart-safe process: state lives in a control-plane database under ~/.octop/ (SQLite by default, PostgreSQL optional), and every surface (web dashboard, IM, cron) routes through one in-process HarnessProcessor.
Users get “experts”, per-user agent profiles with their own workspace, providers, channels, and cron, plus 16 MBTI persona templates, an expert market for sharing configurations, and an AgentTeams beta where a coordinator schedules multiple experts on multi-step work.
The IM bridge (octop-gateway) normalizes Feishu, DingTalk, QQ, WeChat, WeCom, Telegram, and Discord into one processing pipeline, and ACP works in both directions: octop acp serves your Octop agent to Zed or OpenCode, and outbound runners delegate to OpenCode, Claude Code, CodeBuddy, or Codex with permission gates.
Providers are OpenAI-compatible APIs, DashScope (Qwen), Ollama, and other presets configured per agent, with a RAG knowledge base, CDP-based browser automation, remote desktop, and plugins rounding out the surface.
It is published under the TencentCloud GitHub org and built from four focused sub-repos: octop-harness (the agent runtime), octop-gateway, octop-memory, and octop-browser.
Status #
Fast out of the gate and young: 9,156 stars and 1,125 forks in its first three months as of 2026-10-14 (created 2026-07-08), 687 open issues with the last push on 2026-11-15 as of 2026-11-15, MIT.
The beta line ended the way it should: v1.0.2, the first stable release on GitHub, published 2026-10-18 and uploaded to PyPI the same day, after the v1.0.2b4-through-b9 prerelease run (2026-09-27 through 2026-10-17) that PyPI tracked in parallel, and the v1.0.3 line opened as a beta on 2026-10-25 (v1.0.3b1, on GitHub and PyPI the same day: a default expert created alongside each new user, and permissions split per page tab), with v1.0.3b2 extending that line on 2026-11-02 (TOTP and passkey sign-in beside passwords, a RagFlow knowledge-base connector, and chat and session fixes), v1.0.3b3 on 2026-11-04 (PostgreSQL now storing skill packages and knowledge bases shared across multi-instance deployments, slim Docker images, a Volcano Engine TOS storage backend, LDAP account pre-provisioning, and octop-harness upgraded to 1.0.7), and v1.0.3b4 on 2026-11-06 (a workbench cloud-host page that inspects Tencent Cloud CVM through a resident ops expert after authorization, system notifications for background scheduled reminders, Tencent Cloud authorization moved into the control plane for multi-instance deployments, the default Docker image flipping to the slim variant, and octop-harness upgraded to 1.0.8), and v1.0.3b5 on 2026-11-11 (the desktop client moving from Wails to an Electron shell with automatic session renewal after login expiry, custom MCP credentials completing OAuth authorization, new octop migrate openclaw and octop migrate hermes commands importing an existing assistant into one expert, document and folder moves in the knowledge base, conversation sharing on shared experts, curated defaults in the expert market with per-user usage views for admins, and octop-harness upgraded to 1.0.9), the four newest betas each on GitHub and PyPI the same day, and the README carrying a Trendshift trending badge.
The adoption curve is the fastest first quarter in this category after the 2026 wave, and the scrutiny record is the exact AstrBot profile at a third of the age: one 1-point Hacker News thread, zero English-language technical coverage, so the vetting so far has happened in Chinese-language channels you are probably not reading.
Strengths #
- Multi-user from day one: household and team accounts with JWT isolation, expert sharing, and a shared skill pool, which every other runtime in this category treats as an afterthought or omits.
- The Tencent enterprise IM matrix (Feishu, DingTalk, WeCom, QQ, WeChat) through a normalizing gateway, alongside Telegram and Discord.
- ACP in both directions, serving your agent to IDEs and delegating out to coding agents, a symmetry no other member offers.
- The composable sub-repo architecture (harness, gateway, memory, browser) keeps the pieces independently evaluable.
Cautions #
- Zero English-language technical scrutiny: the only independent trace this run found is a 1-point Hacker News thread from 2026-10-06.
- The first stable release only landed 2026-10-18 after three weeks of beta tags, so pin versions deliberately on a project this young.
- The one-line installer pulls its script from a Tencent Cloud COS bucket, and the docs, community, and channel gravity are China-first like AstrBot and QwenPaw.
- The runtime sub-repo (octop-harness) stands at 39 stars, which says the ecosystem is the org’s own code rather than a community.
Pricing #
N/A, free and open source under MIT, self-hosted. Your costs are model keys and the machine you run it on; a managed-agents cloud option is on the roadmap, not shipped.
Compared to #
- AstrBot: the older IM-platform veteran with the wider platform table and the 1,000-plugin marketplace; choose AstrBot for platform breadth and community, Octop for multi-user expert teams and the Tencent-suite connectors.
- QwenPaw: the other China-channel runtime; choose QwenPaw for the offline path through its own trained small models and the five-layer security stack, Octop for multi-user accounts and ACP.
- OpenClaw: the single-operator ecosystem root; choose OpenClaw for channel and companion depth, Octop when the assistant must serve a household or team with separate accounts.
Bottom line #
Recommended for households and small teams whose assistant must live in Feishu, DingTalk, QQ, or WeChat, and who want per-user expert isolation under an MIT license. Not for anyone who needs independent security scrutiny before adopting, or a Western-IM-first deployment. The disagreeable claim I will defend: multi-user is the assistant category’s next battleground, and an incumbent vendor shipped it first while every community favorite still assumes one operator.
Changes #
- 2026-10-07 - Created from the entrant scan as the category’s fifteenth member.
- 2026-10-11 - Corrected the PyPI claim (v1.0.2b6 is now published there while the stable channel stays at 1.0.1), with refreshed adoption numbers.
- 2026-10-13 - Recorded v1.0.2b7 (2026-10-12) extending the beta line on GitHub and PyPI, with refreshed adoption numbers.
- 2026-10-16 - Recorded v1.0.2b8 (2026-10-14, on PyPI the same day) extending the beta line, with refreshed adoption numbers.
- 2026-10-17 - Recorded v1.0.2b9 (2026-10-17, on PyPI the same day) extending the beta line, with refreshed adoption numbers.
- 2026-10-19 - Recorded v1.0.2 (2026-10-18), the first stable release, published on GitHub and uploaded to PyPI the same day, graduating the beta line, with refreshed adoption numbers.
- 2026-10-25 - Recorded v1.0.3b1 (2026-10-25, a default expert at user creation, permissions split per page tab) opening the v1.0.3 line on GitHub and PyPI the same day, with refreshed adoption numbers.
- 2026-10-31 - Rotation re-verification: every cited URL re-fetched live (repo and README, the releases API, the PyPI registry, the octop-harness sub-repo, the HN thread, the Trendshift page), v1.0.3b1 (2026-10-25) confirmed still the newest release with the PyPI stable channel at 1.0.2, and the open issues-and-PRs count refreshed to 789.
- 2026-11-03 - Recorded v1.0.3b2 (2026-11-02, GitHub and PyPI the same day: TOTP and passkey sign-in beside passwords, a RagFlow knowledge-base connector, and chat and session fixes) extending the v1.0.3 beta line, with refreshed adoption numbers.
- 2026-11-07 - Recorded v1.0.3b3 (2026-11-04, PostgreSQL-backed skill packages and knowledge bases shared across multi-instance deployments, slim Docker images, a Volcano Engine TOS storage backend, LDAP account pre-provisioning, octop-harness to 1.0.7) and v1.0.3b4 (2026-11-06, the workbench cloud-host page inspecting Tencent Cloud CVM through a resident ops expert, system notifications for background scheduled reminders, Tencent Cloud authorization in the control plane for multi-instance deployments, the default Docker image flipping to the slim variant, octop-harness to 1.0.8), both extending the v1.0.3 beta line on GitHub and PyPI the same day, with refreshed adoption numbers.
- 2026-11-11 - Recorded v1.0.3b5 (2026-11-11, GitHub and PyPI the same day: the desktop client moving from Wails to an Electron shell with automatic session renewal, custom MCP OAuth credentials,
octop migrate openclawandoctop migrate hermesimport commands, knowledge-base item moves and conversation sharing on shared experts, expert-market curated defaults with admin per-user usage views, octop-harness to 1.0.9), with refreshed adoption numbers.
See also #
- AstrBot - the IM-platform veteran it most overlaps with
- QwenPaw - the other China-channel matrix, with the offline counterbet
- OpenClaw - the single-operator root of the category
- Assistant Runtimes Feature Matrix - the category comparison this note joins
References #
https://github.com/TencentCloud/Octop - repository, license, and adoption numbers as of 2026-10-10
https://raw.githubusercontent.com/TencentCloud/Octop/main/README.md - architecture, experts, channels, ACP, roadmap, install paths
https://api.github.com/repos/TencentCloud/Octop/releases?per_page=3 - v1.0.3b5 (2026-11-11) extending the v1.0.3 beta line, following v1.0.3b4 (2026-11-06) and v1.0.3b3 (2026-11-04), after v1.0.3b2 (2026-11-02) and the v1.0.2 stable (2026-10-18)
https://pypi.org/pypi/octop/json - the PyPI stable channel at 1.0.2 since 2026-10-18, with the v1.0.3 betas uploaded as prereleases on their GitHub release days (b3 2026-11-04, b4 2026-11-06, b5 2026-11-11)
https://github.com/TencentCloud/octop-harness - the agent-runtime sub-repo and its 39-star footprint
https://hn.algolia.com/api/v1/items/49976872 - the single 1-point Hacker News thread (2026-10-06), the zero-scrutiny evidence
https://trendshift.io/repositories/95504 - the Trendshift trending badge the README carries