public active Last verified 2026-04-28

Topolo Agent

Public overview of the Cloudflare-first agent and automation platform in the Topolo portfolio.

Owners
ai-platform
Source Repos
PlatformApplications/TopoloAgent, PlatformApplications/TopoloDocs
Systems
Agent, Topolo Auth
Tags
agents, automation, workflows

What It Is

Topolo Agent is the platform surface for agent execution, workflow orchestration, approvals, inbox work, and workspace-linked automation.

Architecture

The system combines a Cloudflare-backed backend with a browser application and shared packages, using Topolo Auth for login and request validation. Its connector catalog now references the Developers-owned mobile app catalog for installable Android and iOS app metadata instead of a standalone app-library service.

Runtime Surfaces

See /systems/topolo-agent for the current repo and deployment inventory.

API Reference

The current contract is curated rather than OpenAPI-backed in the docs platform. Use /systems/topolo-agent and the internal handbook for the active route families and workspace surface.

Auth and Permissions

Topolo Agent relies on Topolo Auth for frontend login and backend validation. Workflow, thread, and workspace operations are scoped by the authenticated user and org context. The browser app now uses the shared Topolo browser auth client contract with cookie-backed refresh, callback-code redemption on auth.topolo.app, and the canonical service identifier svc_topolo_agent. Browser SSO callbacks delegate Auth /sso/exchange handling to the shared client, so callback URLs carry one-time sso_code values rather than bearer tokens. The backend worker validates operator bearer tokens through Topolo Auth and does not retain an Agent-local JWT secret verification path.

Data Ownership

Topolo Agent owns threads, workflow state, inbox items, approvals, reports, monitors, and workspace-linked execution state.

Deployments

Topolo Agent deploys as a Cloudflare-first application with separate frontend and backend surfaces.

Failure Modes

  • workspace or workflow state drifts between frontend and backend
  • auth service registration is missing or incorrect
  • agent route contracts change without corresponding docs updates

Debugging

Start with /systems/topolo-agent, then verify the backend route family and the frontend auth configuration for the failing flow.

Change Log / Verification

  • Moved the Agent mobile app catalog connector to the Developers-owned catalog on 2026-04-22.
  • Removed the Agent backend local HS256/JWT secret verification path on 2026-04-18
  • Delegated Agent browser callback-code redemption to the shared Topolo Auth client on 2026-04-18.
  • Promoted Agent browser SSO callbacks to Auth /sso/exchange on 2026-04-17 so callback URLs require a one-time sso_code instead of bearer tokens
  • Standardized the Topolo Agent browser auth layer on the shared Topolo browser auth client on 2026-03-31
  • Standardized the public product label to Agent, aligned the frontend launcher/catalog source with Auth-managed metadata, and recorded the frontend Pages target in CloudControl on 2026-04-04
  • Added canonical Topolo Agent coverage and retired repo-local product docs on 2026-03-30