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

Tool interface

OCTO Web

React client for the OCTO messaging platform shipping browser and Electron desktop builds from one codebase, with AI agent chat UI

A+ 90/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
No votes yet

01 / About

What OCTO Web is.

OCTO Web is the TypeScript and React front end for the OCTO messaging platform, an open-source collaboration layer in which human teammates and AI agents share the same channels, threads, and tasks. It talks to the octo-server backend over REST and WebSocket, and the same src/ tree ships twice: as the browser build and as an Electron-packaged desktop client, with branches only at platform-capability boundaries.

The interface is built around agent conversations. It renders streaming replies, a typing indicator, inline tool-call previews, read receipts, and identity chips that distinguish an agent from a person. The Electron shell stays thin, hosting the same React application and forwarding inter-process calls for tray, notifications, file drop, and auto-update; the browser build carries no Electron dependency. English and Simplified Chinese ship together, with translation keys under src/locales/ checked in continuous integration.

The platform organises work as spaces, categories, channels, and threads, and it is designed to run on infrastructure the team controls. Agents in OCTO are digital doubles powered by OpenClaw. The wider repository set includes the Go backend, a task micro-service, an LLM-powered conversation summariser, an admin console, native Android and iOS clients, a shared Go library, and third-party adapters.

Features

  • One codebase, two builds: browser and Electron desktop surfaces from the same React source
  • Agent-aware chat UI: streaming replies, typing indicators, inline tool-call previews, read receipts, and agent-versus-human identity chips
  • Thin desktop shell: Electron forwards tray, notification, file-drop, and auto-update calls without forking the app
  • Bilingual by default: English and Simplified Chinese resources, enforced in continuous integration
  • Structured client layout: route views, a shared UI kit, client state including agent orchestration, and a REST plus WebSocket API layer
  • Self-hostable stack: points at your own octo-server instance through VITEAPI* environment values

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.

03 / Related

More around OCTO Web.

04 / Build

Build with OCTO Web.

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

Get OCTO Web →

Browse the catalogue