Skip to content

Changelog

Notable changes to the Telbox developer platform — the Agents API, the official SDKs, and this documentation site. Consumer-app changes live elsewhere; this log tracks only what a developer building on Telbox needs to know.

Developer preview — nothing here is GA yet

The external surface (REST, MCP, OAuth) is gated behind the apikey_auth_enabled flag and is off in production until launch, so versions below are preview milestones, not general-availability releases. The Agents OpenAPI spec is versioned by date (currently 2026-06-14); the SDKs are at 0.1.0 and publish at launch. Once the platform is GA, this page moves to dated, semver-tagged releases.

Unreleased

  • Scoped API keys for the Agents API. The /v1/agents* endpoints now accept a scoped API key (agents:read / agents:write) in addition to the developer session JWT. (2026-07-22)
  • Docs accuracy + styling pass: docs.telbox.ai unified with the telbox.ai dark theme, TypeScript SDK build fix, MCP tool-schema corrections, honest developer console copy. (2026-07-22)

2026-06-16 — Docs site

  • Rebranded docs.telbox.ai to the Telbox dark navy + gradient theme, with a light-scheme toggle as a fallback.
  • Made the developer docs deployable as their own Cloudflare Pages project (committed OpenAPI specs, no live-API export at deploy time).

2026-06-15 — OAuth

  • Implemented the OAuth 2.0 device-code token grant (RFC 8628), for clients that authorize on a second screen.

2026-06-14 — Agents API, SDKs & docs

  • First public cut of the Agents developer docs (this site), with the Agents OpenAPI 3.1 spec as the single source of truth (spec version 2026-06-14).
  • Official Python (telbox) and TypeScript (@telbox/sdk) SDKs, plus a generator that scaffolds clients for other languages from the same spec.
  • The verified agent principal: each agent gets its own Ed25519 identity, signs the messages it sends, and acts within an authority leash (draft_only → ask_before_action → auto_act_limited).

2026-06-13 — MCP & voice

  • MCP in both directions: expose an agent as an MCP server, and consume external MCP servers through the outbound broker.
  • Agent voice output: agents can synthesize audio replies with the built-in voice.

Building the wire history behind these milestones (OAuth DCR, /authorize + /token with PKCE, the MCP server's six tools, Connected Apps, and the OpenClaw channel adapter) is detailed across the Concepts and Guides sections. For live availability, see Status.