Runtime Surface Overview

​

Overview

Asymptote supports multiple runtime surfaces because each agent harness exposes telemetry differently. The runtime support model applies to both Asymptote Open Source and Asymptote Managed: Open Source collects and normalizes supported local, CI, and cloud-agent telemetry, while Managed adds hosted ingest, visibility, and governance on top of the same surfaces. These integrations are grouped by where the agent runs and how telemetry is collected:

• Local: Agent harnesses running on an endpoint write telemetry to Asymptote’s local collector, hook adapter, plugin, or gateway path.
• Browser chat: An optional Chrome extension reads the chat streams of supported sites in the browser and posts them to the same local collector.
• CI: Ephemeral CI jobs use a temporary collector and write normalized runtime JSONL as a build artifact or upload target instead of installing a persistent endpoint service.
• Cloud: Provider-managed cloud agents can write session telemetry from the cloud sandbox to customer-managed storage, while SDK integrations instrument agent applications that run in servers, serverless functions, workers, and hosted agent platforms.

​

Support matrix

​

Local coding agent harnesses

Two rows in that table are not hook or OTLP integrations. fx exposes no hook, plugin, or OpenTelemetry surface at all, so Asymptote reads the session records fx commits to disk; every fx event is marked harness.collection_method=poll, meaning it was read after the turn was committed rather than observed as the agent worked, and nothing on that path can hold or deny a tool call. Prime Agent is listed because Asymptote already recognizes it as its own harness, but no managed extension ships yet, so it collects nothing today.

​

Local knowledge worker agent harnesses

​

Browser chat surfaces

Both sites are collected by one optional Chrome extension. Browser chat resolves to the claude_web and chatgpt_web harness names, so it stays distinguishable from CLI agents. The extension retains full prompt and response text by default. See Browser Extension to install it and to change the retention mode.

​

CI harnesses

​

Cloud agent harnesses and SDKs

​

Deployment notes

Local agent harnesses need the endpoint agent installed on the machine they run on. Use the native package for that platform, which installs and starts everything in one step: Each package installs the endpoint agent, starts the local collector as a service, and configures the installing user’s supported agent runtimes to export to it. Paths differ per platform: MDM assets, meaning Jamf Pro Extension Attributes, Fleet osquery queries, and Rippling deployment, are macOS only. On Linux and Windows, deploy the package with whatever configuration management you already run.

​

Enterprise runtime configuration

Install hooks separately in the logged-in user’s context when you need richer hook telemetry or inventory heartbeat triggers. This applies to Antigravity CLI, Claude Code, Cline, Codex CLI inventory hooks, Cursor, Devin CLI, Devin Desktop, Factory Droid, Grok Build, Hermes Agent, goose, Muse Code, Oh My Pi, OpenCode, OpenHands, Pi, Qwen Code, and the optional VS Code hooks. fx is the exception with no hooks to install: schedule beacon endpoint fx sync instead. If a system collector is running while the CLI is reading the default per-user log, beacon endpoint status and the local dashboard surface a runtime-log source warning so you can tell where OTLP events are being written.

​

Related