OCTO — the open workplace built for humans × AI agents.
_{Let Lobsters (OpenClaw-powered digital doubles) do the thinking and doing. You focus on taste.}

🏠 OCTO Home · 🚀 Quickstart · 📦 Ecosystem · 🤝 Contributing

🌐 Read in: English · 简体中文

OCTO Admin

Admin console for the OCTO platform — tenants, organisations, users, channels, and Lobster agent configuration from a single pane of glass.

octo-admin is the TypeScript / React console that platform operators use to manage an OCTO deployment. It is a thin front-end over octo-server's admin APIs — no business logic of its own, no side database. Everything you see or click turns into a call into the main OCTO backend.

🌟 Why OCTO Admin

• Operator console, not a second product. octo-admin only exposes what octo-server already supports through its admin APIs. No shadow schema, no drift between "what the admin UI can do" and "what the backend actually enforces".
• Separate surface, separate deploy. The admin UI is a distinct bundle so ops can publish it on an internal URL (VPN-only, SSO-gated) while the user-facing octo-web goes on the public edge.
• Built for day-2 work. Tenant bootstrap, org / user audit, channel moderation, Lobster agent feature-flag toggles, webhook rotation — the screens are tuned for the "run OCTO in production" workflow, not the first-demo one.

🚀 Quickstart

git clone https://github.com/Mininglamp-OSS/octo-admin.git
cd octo-admin
pnpm install
pnpm dev

By default the dev build points at http://localhost:8080 (the same octo-server instance you'd run for octo-web development). Copy .env.example to .env.local and edit VITE_ADMIN_API_* to aim it at a different backend.

For a production build:

pnpm build        # emits static assets under ./dist
# serve ./dist behind an SSO-aware reverse proxy (nginx / envoy / ...)

📦 Modules / Architecture

Top-level layout:

octo-admin talks to octo-server over the /admin/* REST surface. It never talks to the primary database directly. Operator authentication is delegated to octo-server (SSO or admin-token), and every mutation must pass backend-side RBAC before it is persisted.

🔗 OCTO Ecosystem

graph TD
  subgraph Clients[Clients]
    Web[octo-web<br/>Web / PC]
    Android[octo-android<br/>Android]
    iOS[octo-ios<br/>iOS]
  end

  subgraph Core[Core Services]
    Server[octo-server<br/>Backend API]
    Matter[octo-matter<br/>Task / Todo]
    Summary[octo-smart-summary<br/>AI Summary]
    Admin[octo-admin<br/>Admin Console]
  end

  subgraph Shared[Shared Libraries & Integrations]
    Lib[octo-lib<br/>Core Go Library]
    Adapters[octo-adapters<br/>Third-party Adapters]
  end

  Web --> Server
  Android --> Server
  iOS --> Server
  Admin --> Server
  Server --> Matter
  Server --> Summary
  Server --> Adapters
  Server -.uses.-> Lib
  Matter -.uses.-> Lib
  Adapters -.uses.-> Lib

🧭 Philosophy

OCTO ships under three shared principles that apply to every repository in this matrix:

1. Local-first. Anything that can run on the user's own box — chats, embeddings, agents — should. Your data stays yours; cloud is a choice, not a requirement.
2. Humans judge, AI thinks and acts. Humans focus on taste (what matters, what's right, what to ship). Lobster agents — OpenClaw-powered digital doubles — carry the thinking and execution load.
3. Release-as-product. Every open-source cut is shipped as a self-contained product, not a code dump: one squash per release, Apache 2.0, no internal baggage, reproducible from this repo alone.

🤝 Contributing

We love pull requests! Before you open one, please read:

• CONTRIBUTING.md — workflow, branch model, commit style
• CODE_OF_CONDUCT.md — community expectations

For security issues please follow SECURITY.md instead of the public tracker.

📄 License

Apache License 2.0 — see LICENSE for the full text and NOTICE for third-party attributions.

_{Made with 🐙 by OCTO Contributors · Mininglamp-OSS}