Skip to content
OpenBot Docs

OpenBot.one client

OpenBot.one is the hosted browser client for OpenBot. Your agents, plugins, and data still run locally under the openbot CLI (openbot start); the web app connects to that runtime over the same HTTP and Server-Sent Events surface described in Your First Channel.

What you use it for

Section titled “What you use it for”
  • Browse and manage channels and threads with URLs such as /channels/:channelId/threads/:threadId.
  • Work with agents (/agents, /agents/:agentId, agent creation flows).
  • Chat with streaming UI, widgets, and supporting panels instead of calling POST /api/publish manually.

OpenBot still prints OpenBot.one when the server starts so you know where to open the UI.

Accounts and workspaces

Section titled “Accounts and workspaces”

The client uses Firebase for sign-in and for workspace records stored in Firestore. After you log in, you work inside a workspace that points at your machine’s OpenBot HTTP API.

When you create a workspace you can supply a runtimeBaseUrl — typically http://localhost:4132 while developing locally. That base URL is how the SPA reaches your openbot start server for publish/state/event streaming.

Alignment with OpenBot concepts

Section titled “Alignment with OpenBot concepts”
  • Threads: Conversation routes include both channelId and threadId, matching OpenBot’s thread-scoped messaging model (Your First Channel).
  • Runtime API: The app builds requests through a shared runtime client wired from workspace settings; behavior stays consistent with the small public API on the OpenBot server.
  • Active runs: The sidebar can reflect concurrent agent activity using the global __global__ SSE bucket; see also Architecture.

See also

Section titled “See also”