octo-web

Name: octo-web
Author: Mininglamp-OSS

Verified

Web & desktop (Electron) client for the OCTO open workplace — one React + TypeScript codebase shipping browser and PC surfaces, with first-class AI agent UX.

1,182stars

180forks

TypeScript

Installation

# Add to your Claude Code skills
git clone https://github.com/Mininglamp-OSS/octo-web

Getting Started

Guides for using ai agents skills like octo-web.

Caveman: Cut Claude Token Use by 65%
How agent-side prompt compression works, when to use it, and when not to.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.
Getting Started with AI Skills

Security ReportVerified

Last scanned: 6/29/2026

{
  "issues": [],
  "status": "PASSED",
  "scannedAt": "2026-06-29T08:59:09.720Z",
  "npmAuditRan": true,
  "pipAuditRan": true,
  "promptInjectionRan": true
}

Compare with similar skills

See how octo-web compares with popular alternatives.

octo-web vs hermes agent

See comparison

README.md

Frequently Asked Questions

What is octo-web?

octo-web is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Mininglamp-OSS. Web & desktop (Electron) client for the OCTO open workplace — one React + TypeScript codebase shipping browser and PC surfaces, with first-class AI agent UX. It has 1,182 GitHub stars.

Is octo-web safe to use?

Yes. octo-web passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.

How do I install octo-web?

Clone the repository with "git clone https://github.com/Mininglamp-OSS/octo-web" and add it to your Claude Code skills directory (see the Installation section above).

What programming language is octo-web written in?

octo-web is primarily written in TypeScript. It is open-source under Mininglamp-OSS on GitHub, so you can review or fork the full source.

Are there alternatives to octo-web?

Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh octo-web against similar tools.

Agentic AI for Beginners

Build your first AI agent from scratch - tool use, ReAct pattern, memory, deployment

41 minBeginner

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

ECC

by affaan-m

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

268,059

awesome-gamedev-agent-skills Chorus

⚠️ Third-Party Software Notice

This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.

Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.

Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.

Read the Terms of Service

🌐 Read in: English · 简体中文

OCTO Web

Web & PC (Electron) client for the OCTO messaging platform — one React codebase, two shipped surfaces.

octo-web is the TypeScript / React front-end that talks to octo-server over REST + WebSocket. The same codebase ships two ways: as a browser build (the canonical OCTO chat surface), and as an Electron-packaged desktop PC client.

🌟 Why OCTO Web

One codebase, two products. Browser + PC (Electron) are built from the same src/ — no parallel React trees, no diverging UX. Branch switches happen at platform-capability boundaries only.
Lobster-ready UI. First-class surfaces for AI agent conversations: streaming replies, typing indicator, inline tool-call previews, read receipts, agent-vs-human identity chips.
Full bilingual shell. English and Simplified Chinese ship together out of the box; i18n keys live in src/locales/ and are enforced in CI.

🚀 Quickstart

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

By default the web build expects an octo-server instance reachable at http://localhost:8080. Point it at your own server by copying .env.example to .env.local and editing the VITE_API_* values.

📦 Modules / Architecture

Top-level layout:

Path	Purpose
`src/pages/`	Route-level React views (chat, channels, org, settings)
`src/components/`	Shared UI kit (message bubbles, inputs, agent chips, streaming renderers)
`src/store/`	Client state (auth, channels, draft, agent orchestration UI state)
`src/api/`	REST + WebSocket client talking to `octo-server`
`src/locales/`	i18n resources (English · 简体中文)
`electron/`	Electron main/renderer bootstrap for the PC build
`docs/`	Design docs, architecture notes, screenshots

Key build targets:

pnpm build        # build the browser bundle
pnpm pc:dev       # launch the Electron shell against the dev build
pnpm pc:package   # produce a distributable PC bundle (macOS / Windows / Linux)
pnpm test         # run unit + component tests

The PC Electron shell is intentionally thin — it hosts the same React app and forwards IPC for native capabilities (tray, notifications, file drop, auto- update). The browser build runs without any Electron dependency.

🔗 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

Repository	Language	Role
`octo-server`	Go	Backend API · business orchestration · Lobster agent scheduling
`octo-matter`	Go	Task / Todo / Matter micro-service
`octo-smart-summary`	Go	LLM-powered conversation summarisation
`octo-web`	TypeScript / React	Web & PC (Electron) client
`octo-android`	Kotlin / Java	Native Android client
`octo-ios`	Swift / Objective-C	Native iOS client
`octo-admin`	TypeScript / React	Admin console (tenant / org / user / channel management)
`octo-lib`	Go	Shared core library (protocol, crypto, storage, HTTP)
`octo-adapters`	TypeScript / Python	Third-party integrations (IM bridges, AI channels)

🧭 Philosophy

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

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.
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.
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.

🙏 Acknowledgments

octo-web owes its original scaffolding to:

TangSengDaoDaoWeb — our upstream, by the TangSengDaoDao team.
WuKongIM — the real-time messaging core that octo-server drives behind this client.

See NOTICE for the full attribution list and third-party component licenses.