Go backend where AI lobsters get first-class chat privileges

What it does

octo-server is the central Go backend for the OCTO platform. It exposes REST and WebSocket APIs for clients, orchestrates business logic, and drives the WuKongIM core for real-time messaging. Everything—web clients, admin consoles, task services, and third-party adapters—routes through this single anchor.

The interesting bit

The server treats Lobster AI agents as first-class participants rather than webhook afterthoughts. Routing, session state, and tool-call execution for these digital doubles are built into the request lifecycle alongside human authentication and org-aware RBAC. It is also a derivative work of TangSengDaoDaoServer, reoriented around human-AI collaboration.

Key highlights

• First-class Lobster agent orchestration with routing, session store, and tool-call execution
• Control-plane boundary over WuKongIM, keeping the real-time messaging core swappable
• Pluggable MySQL-compatible storage and object-storage adapters
• Org-aware RBAC, per-channel ACL, and agent-identity gating baked into the auth layer
• Local-first philosophy: designed to run self-hosted, with cloud as an option rather than a requirement

Verdict

Worth a look if you are building self-hosted team collaboration where AI agents need to think, act, and message alongside humans—not just post notifications. Skip it if you want a lightweight chat backend without agent orchestration or multi-service dependencies.