Topolo Agent | Topolo Docs

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.

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 on auth.topolo.app and the canonical service identifier svc_topolo_agent.

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

Standardized the Topolo Agent browser auth layer on the shared Topolo browser auth client on 2026-03-31
Added canonical Topolo Agent coverage and retired repo-local product docs on 2026-03-30