The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
update inventory docs with images
Justin D'Souzae66bb3dc3eee
diff --git a/docs/architecture/architecture.mdx b/docs/architecture/architecture.mdxindex 0e54e42d..43164908 100644--- a/docs/architecture/architecture.mdx+++ b/docs/architecture/architecture.mdx@@ -5,7 +5,7 @@ description: "How Beacon collects, normalizes, stores, and forwards agent harnes## Overview-Agent Beacon is the open-source telemetry layer for AI agents wherever they run: locally, in CI, or in the cloud. Supported [agent harnesses](/runtimes) emit activity through [OpenTelemetry](/concepts/core-concepts#otlp), native [hook](/concepts/core-concepts#hooks) payloads, CI wrappers, cloud sandbox hooks, or SDK instrumentation. Beacon collects those runtime-specific signals and normalizes them into a shared event model for inspection, retention, and customer-controlled forwarding.+Agent Beacon is the open-source telemetry layer for AI agents wherever they run: locally, in [CI](/concepts/core-concepts#ci-telemetry), or in the [cloud](/concepts/core-concepts#cloud-agent-telemetry). Supported [agent harnesses](/runtimes) emit activity through [OpenTelemetry](/concepts/core-concepts#otlp), native [hook](/concepts/core-concepts#hooks) payloads, CI wrappers, cloud sandbox hooks, or [SDK instrumentation](/concepts/core-concepts#observe-sdk). Beacon collects those runtime-specific signals and normalizes them into a shared [endpoint event](/concepts/core-concepts#endpoint-event) model for inspection, retention, and customer-controlled forwarding.The endpoint architecture is local-first: local endpoint telemetry can be inspected and forwarded without sending it to a hosted Beacon backend. CI and cloud-agent paths use the same normalized event model through surface-specific setup paths rather than a persistent endpoint service.@@ -16,8 +16,8 @@ The endpoint architecture is local-first: local endpoint telemetry can be inspec1. **Runtime surfaces:** Supported [agent harnesses](/runtimes) expose different [telemetry surfaces](/concepts/core-concepts#runtime-surface). Beacon uses the strongest surface available for each runtime instead of forcing every tool through one adapter.2. **Local collection:** Beacon receives OTLP gRPC, OTLP HTTP, or native hook payloads on the endpoint, depending on the runtime.3. **Normalization:** Logs, traces, metrics, resource attributes, and hook payloads are mapped into one endpoint event model with consistent event, endpoint, harness, session, tool, command, file, approval, policy, content, and destination context.-4. **Local storage and inspection:** Beacon writes one JSON object per line to `runtime.jsonl`. The local [dashboard](/cli/dashboard) reads recent runtime logs over a loopback-only service for rollout validation and investigation.-5. **Forwarding:** External SIEM, log, and storage destinations consume the same normalized JSONL stream, or receive events directly from optional collector exporters.+4. **Local storage and inspection:** Beacon writes one JSON object per line to the [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). The local [dashboard](/concepts/core-concepts#dashboard) reads recent runtime logs over a loopback-only service for rollout validation and investigation.+5. **Forwarding:** External SIEM, log, and storage destinations consume the same normalized JSONL stream through [customer-managed forwarding](/concepts/core-concepts#customer-managed-forwarding), or receive events directly from optional collector exporters.## End-to-End Flow@@ -53,7 +53,7 @@ On macOS, the collector runs under `launchd` in [user mode or system mode](/conc### Vector forwarding-Use Vector when you want a customer-managed host agent to tail `runtime.jsonl` and forward Beacon events without storing destination secrets in Beacon endpoint configuration.+Use [Vector forwarding](/concepts/core-concepts#vector-forwarding) when you want a customer-managed host agent to tail `runtime.jsonl` and forward Beacon events without storing destination secrets in Beacon endpoint configuration.- Beacon remains the local JSONL producer.- Vector tails the active log path, checkpoints offsets, batches events, and retries delivery.diff --git a/docs/architecture/system-architecture.mdx b/docs/architecture/system-architecture.mdxindex 534f9d92..5cca6d31 100644--- a/docs/architecture/system-architecture.mdx+++ b/docs/architecture/system-architecture.mdx@@ -3,7 +3,7 @@ title: "System Architecture"description: "Compare the open-source Agent Beacon architecture with the managed Asymptote platform architecture"----Asymptote supports two architecture paths: the open-source Agent Beacon architecture for supported local, CI, and cloud telemetry paths, and the managed Asymptote architecture for centralized visibility, governance, detections, and investigations.+Asymptote supports two architecture paths: the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) architecture for supported local, [CI](/concepts/core-concepts#ci-telemetry), and [cloud telemetry](/concepts/core-concepts#cloud-agent-telemetry) paths, and the [Asymptote Managed](/concepts/core-concepts#asymptote-managed) architecture for centralized visibility, governance, detections, and investigations.<Columns cols={2}><Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">@@ -18,8 +18,8 @@ Asymptote supports two architecture paths: the open-source Agent Beacon architec| Architecture | Use when || --- | --- |-| Open Source Architecture | You want open-source telemetry for supported local, CI, and cloud agent surfaces, with customer-controlled records and forwarding. |-| Managed Architecture | You want managed ingest, retention, search, detections, fleet visibility, policy controls, identity mapping, approvals, SSO, RBAC, audit trails, and investigation workflows. |+| Open Source Architecture | You want [open-source telemetry](/concepts/core-concepts#asymptote-open-source) for supported local, CI, and cloud agent surfaces, with customer-controlled records and forwarding. |+| Managed Architecture | You want [managed ingest](/concepts/core-concepts#asymptote-managed), retention, search, detections, fleet visibility, policy controls, identity mapping, approvals, SSO, RBAC, audit trails, and investigation workflows. |## Relateddiff --git a/docs/concepts/core-concepts.mdx b/docs/concepts/core-concepts.mdxindex 87cc2a21..a79a32b0 100644--- a/docs/concepts/core-concepts.mdx+++ b/docs/concepts/core-concepts.mdx@@ -3,9 +3,25 @@ title: "Core Concepts"description: "Core concepts for Asymptote, Agent Beacon, and agent runtime telemetry"----Beacon observes agent harness activity across supported local, CI, and cloud surfaces, normalizes it into a shared event model, and gives security teams records they can inspect, retain, or forward into existing pipelines.+Asymptote observes AI agent runtime activity across supported local endpoints, CI jobs, cloud-agent sandboxes, and SDK-instrumented applications. Agent Beacon is the open-source foundation for local-first collection and customer-controlled forwarding. Asymptote Managed builds on that foundation with hosted ingest, retention, search, detections, governance, and investigations.-Use this page as a quick reference for the concepts used across Asymptote and Agent Beacon docs.+Use this page as a quick reference for terms used across Asymptote and Agent Beacon docs.++## Asymptote Open Source++**Asymptote Open Source** is the open-source telemetry path built on Agent Beacon. It collects supported agent activity across local endpoints, CI jobs, and cloud-agent surfaces, normalizes that activity into Beacon-compatible records, and leaves storage and forwarding under customer control. See [Open Source deployment](/deployment/open-source).++## Agent Beacon++**Agent Beacon** is the local-first endpoint telemetry agent in the `agent-beacon` repository. Beacon configures supported agent harnesses, receives OTLP or hook telemetry, writes local JSONL, serves the local dashboard, and can generate forwarding content for customer-managed destinations.++## Asymptote Managed++**Asymptote Managed** is the hosted Asymptote operating model for centralized ingest, retention, search, detections, fleet visibility, policy controls, identity mapping, approvals, SSO, RBAC, audit trails, and investigation workflows. See [Managed deployment](/deployment/managed).++## Private Deployment++**Private Deployment** applies managed capabilities with stronger infrastructure ownership, data isolation, residency, or custom retention requirements. See [Hosting Options](/deployment/hosting-options).## Endpoint Agent@@ -13,12 +29,24 @@ The **endpoint agent** is the local Beacon service and configuration managed by## Runtime Surface-A **runtime surface** is the telemetry interface exposed by an agent harness. Beacon supports different surfaces because each [agent harness](/runtimes) exposes activity differently, including local OpenTelemetry configuration, hook adapters, CI wrappers, cloud sandbox hooks, SDK instrumentation, admin-configured OpenTelemetry, and gateway-configured OTLP/HTTP export.+A **runtime surface** is the telemetry interface exposed by an agent harness. Beacon supports different surfaces because each [agent harness](/runtimes) exposes activity differently, including local OpenTelemetry configuration, hook adapters, CI wrappers, cloud sandbox hooks, SDK instrumentation, admin-configured OpenTelemetry, and gateway-configured OTLP/HTTP export. See [Runtime Surface Overview](/runtimes).## Agent HarnessAn **agent harness** is the runtime or integration that produced an event. It can be a local coding agent, a CI job, a cloud-agent surface, an SDK-instrumented application, an admin-configured service integration, or a gateway-managed runtime surface. Examples include `claude`, `codex`, `gemini_cli`, `grok`, `opencode`, `devin-cli`, `devin-desktop`, `factory`, `cursor`, `claude_cowork`, and `openclaw_gateway`. Beacon stores harness context in normalized events so investigators can filter by the source that generated the activity.+## CI Telemetry++**CI telemetry** is agent runtime telemetry captured during ephemeral build jobs. Beacon can run a temporary collector through `beacon ci exec` or `beacon ci start` / `beacon ci finish`, write a completed `runtime.jsonl`, and export that file as an artifact or upload target. See [CI Telemetry Exports](/log-forwarding/ci-telemetry-exports).++## Cloud-Agent Telemetry++**Cloud-agent telemetry** is activity captured from provider-managed cloud agent sandboxes. Beacon cloud helpers print hook and storage setup so cloud sessions can produce Beacon-compatible `runtime.jsonl` artifacts, currently with self-serve Google Cloud Storage upload paths for supported cloud agents.++## Observe SDK++The **Observe SDK** is the `@asymptote/sdk` TypeScript package for instrumenting cloud-hosted agent applications, services, workers, serverless functions, and agent SDK integrations. It can export to Asymptote Managed hosted Observe or to a customer-managed OTLP collector. See [Asymptote Observe SDK](/sdk).+## Local CollectorThe **local collector** is Beacon's OpenTelemetry Collector pipeline on the endpoint. It receives OTLP from supported agent harnesses, batches and processes telemetry, writes normalized Beacon JSONL through the `beaconjson` exporter, and can optionally send collector signals to Splunk HEC or Falcon LogScale HEC.@@ -33,11 +61,19 @@ The **local collector** is Beacon's OpenTelemetry Collector pipeline on the endp## Endpoint Event-An **endpoint event** is one normalized Beacon JSON object describing runtime activity on a local machine. Endpoint events include a stable `event` action, endpoint context, harness context, severity, and any optional entities the source provides. CI and cloud telemetry paths use the same Beacon-compatible event model where their collection path emits normalized records.+An **endpoint event** is one normalized Beacon JSON object describing runtime activity. Endpoint events include a stable `event` action, endpoint context, harness context, severity, and any optional entities the source provides. CI and cloud telemetry paths use the same Beacon-compatible event model where their collection path emits normalized records. See [Endpoint event schema](/telemetry-schema/event-schema).## Entity Model-The **entity model** is Beacon's shared shape for runtime-specific payloads. Each event has an action plus typed context such as `endpoint`, `user`, `harness`, `origin`, `run`, `session`, `tool`, `file`, `command`, `mcp`, `approval`, `policy`, `prompt`, `content`, `gen_ai`, `destination`, and `health`.+The **entity model** is Beacon's shared shape for runtime-specific payloads. Each event has an action plus typed context such as `endpoint`, `user`, `harness`, `origin`, `run`, `session`, `tool`, `file`, `command`, `mcp`, `approval`, `policy`, `prompt`, `content`, `gen_ai`, `destination`, and `health`. See [Telemetry fields](/telemetry-schema/fields).++## Threat Rules++**Threat rules** are local detection rules that match Beacon endpoint events and produce findings. Beacon's `scan` command runs the active rule corpus over local or CI JSONL without requiring hosted ingest. See [Detections](/detections).++## Findings++**Findings** are detection results produced when threat rules match runtime activity. They summarize the matched event, rule metadata, severity, and evidence so operators can review suspicious agent behavior in the local dashboard or downstream systems.## Runtime JSONL Log@@ -63,6 +99,14 @@ The **Elastic content pack** is Beacon's generated Filebeat, standalone ElasticThe **Datadog content pack** is Beacon's generated Datadog Agent custom log collection content for shipping local Beacon JSONL into Datadog Logs. The pack reads the runtime log; Beacon itself does not store Datadog API keys or site configuration.+## Microsoft Sentinel Content Pack++The **Microsoft Sentinel content pack** is Beacon's generated Azure Monitor Agent and Log Analytics custom log content for shipping local Beacon JSONL into Microsoft Sentinel. The pack reads the runtime log; Beacon itself does not store Azure tenant IDs, client secrets, workspace IDs, DCR identifiers, or ingestion endpoints.++## AWS CloudWatch Logs Content Pack++The **AWS CloudWatch Logs content pack** is Beacon's generated Vector forwarding template, setup guidance, and sample events for shipping local Beacon JSONL into a customer-managed CloudWatch Logs log group. The pack reads the runtime log; Beacon itself does not store AWS credentials, IAM roles, log group retention, stream naming, or encryption settings.+## Sumo Logic Content PackThe **Sumo Logic content pack** is Beacon's generated setup guidance, upload smoke-test script, Vector forwarding template, and sample events for shipping local Beacon JSONL into a Sumo Logic Hosted Collector HTTP Logs & Metrics Source. The pack reads the runtime log; Beacon itself does not store Sumo Source URLs, tokens, or collector configuration.@@ -79,6 +123,10 @@ The **AWS S3 content pack** is Beacon's generated setup guidance, AWS CLI smoke-The **Google Cloud Storage content pack** is Beacon's generated setup guidance, GCS upload smoke-test script, Vector `gcp_cloud_storage` forwarding template, and sample events for shipping local Beacon JSONL into a GCS bucket. The pack reads the runtime log; Beacon itself does not store Google Cloud credentials, service accounts, workload identity settings, bucket IAM, lifecycle rules, retention policies, or encryption settings.+## Vector Forwarding++**Vector forwarding** means a customer-managed Vector host agent tails Beacon's local `runtime.jsonl`, parses each JSON line, and delivers events to a downstream destination such as Sumo Logic, Rapid7 InsightIDR, Falcon LogScale, AWS CloudWatch Logs, AWS S3, or Google Cloud Storage. Vector owns checkpointing, batching, retries, credentials, and destination-specific settings.+## Customer-Managed Forwarding**Customer-managed forwarding** means an existing shipper, agent, Vector host agent, or SIEM pipeline reads Beacon's runtime JSONL log and routes each line to a downstream destination.@@ -102,6 +150,9 @@ The **dashboard** is a loopback-only local view over Beacon runtime logs. It inc## Related<Columns cols={2}>+ <Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">+ Compare Asymptote Open Source, Managed, and Private Deployment paths.+ </Card><Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">See how runtime telemetry flows through collection, normalization, and local outputs.</Card>@@ -120,4 +171,7 @@ The **dashboard** is a loopback-only local view over Beacon runtime logs. It inc<Card title="Log forwarding" icon="tower-broadcast" href="/log-forwarding">Forward Beacon events into Wazuh, Splunk HEC, Falcon LogScale, Elastic, Datadog, Sumo Logic, Rapid7 InsightIDR, Microsoft Sentinel, AWS S3, Google Cloud Storage, or customer-managed pipelines.</Card>+ <Card title="Asymptote Observe SDK" icon="code" href="/sdk">+ Instrument cloud-hosted agent applications with hosted or customer-managed export.+ </Card></Columns>diff --git a/docs/deployment/hosting-options.mdx b/docs/deployment/hosting-options.mdxindex 0102b634..874d567e 100644--- a/docs/deployment/hosting-options.mdx+++ b/docs/deployment/hosting-options.mdx@@ -3,13 +3,13 @@ title: "Hosting Options"description: "Choose between Open Source, Managed, and Private Deployment paths"----Asymptote can start local-first with the open-source Agent Beacon endpoint agent, run as Managed Asymptote Cloud, or deploy privately for teams with stricter infrastructure requirements.+Asymptote can start local-first with the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) [endpoint agent](/concepts/core-concepts#endpoint-agent), run as [Asymptote Managed](/concepts/core-concepts#asymptote-managed), or deploy privately for teams with stricter infrastructure requirements.| Hosting Option | Use it when | Data and operations model || -------------- | ----------- | ------------------------- |-| Asymptote Open Source | You want endpoint telemetry, local JSONL, and customer-managed forwarding. | Beacon runs on the endpoint and writes local logs by default. |-| Asymptote Managed | You need centralized visibility, policy controls, investigations, SSO/RBAC, audit trails, and rollout support. | Asymptote provides managed ingest, retention, search, detections, and enterprise operations. |-| Asymptote Private Deployment | You want Managed capabilities with stronger isolation, residency, or infrastructure ownership requirements. | Asymptote works with you on dedicated infrastructure and custom deployment boundaries. |+| [Asymptote Open Source](/concepts/core-concepts#asymptote-open-source) | You want endpoint telemetry, local JSONL, and customer-managed forwarding. | Beacon runs on the endpoint and writes local logs by default. |+| [Asymptote Managed](/concepts/core-concepts#asymptote-managed) | You need centralized visibility, policy controls, investigations, SSO/RBAC, audit trails, and rollout support. | Asymptote provides managed ingest, retention, search, detections, and enterprise operations. |+| [Asymptote Private Deployment](/concepts/core-concepts#private-deployment) | You want Managed capabilities with stronger isolation, residency, or infrastructure ownership requirements. | Asymptote works with you on dedicated infrastructure and custom deployment boundaries. |## Asymptote Open Source@@ -47,7 +47,7 @@ Use Managed when you want hosted visibility, governance, and enterprise rolloutManaged adds centralized ingest, retention, search, detections, fleet-wide visibility, policy controls, identity mapping, approvals, investigation workflows, SSO, RBAC, audit trails, and enterprise onboarding on top of the open-source Agent Beacon foundation.-For cloud-hosted agent applications, install the SDK and initialize hosted export with an Asymptote API key:+For cloud-hosted agent applications, install the [Observe SDK](/concepts/core-concepts#observe-sdk) and initialize hosted export with an Asymptote API key:```bash title="Set the hosted Observe API key"export ASYMPTOTE_API_KEY=...diff --git a/docs/deployment/managed.mdx b/docs/deployment/managed.mdxindex 4db2c66b..fb04e2f6 100644--- a/docs/deployment/managed.mdx+++ b/docs/deployment/managed.mdx@@ -1,6 +1,7 @@---title: "Asymptote Managed"description: "Managed visibility, governance, and investigations for agent activity at scale"+tag: "Enterprise"---Asymptote Managed builds on the open-source Agent Beacon foundation for teams that need centralized operations, policy controls, and investigation workflows across a fleet.diff --git a/docs/docs.json b/docs/docs.jsonindex 2504ed1d..7aecb069 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -92,15 +92,6 @@"group": "Manage Asymptote","icon": "sliders","pages": [- {- "group": "Detections",- "root": "detections/index",- "pages": [- "detections/yaml-schema",- "detections/standard",- "detections/engine"- ]- },{"group": "Inventory","root": "guides/inventory",@@ -109,6 +100,15 @@"inventory/mcp-servers","inventory/skills"]+ },+ {+ "group": "Detections",+ "root": "detections/index",+ "pages": [+ "detections/yaml-schema",+ "detections/standard",+ "detections/engine"+ ]}]},diff --git a/docs/get-started/overview.mdx b/docs/get-started/overview.mdxindex 4b302889..b8ec3a0a 100644--- a/docs/get-started/overview.mdx+++ b/docs/get-started/overview.mdx@@ -35,9 +35,9 @@ In practice, teams usually run into a few problems:Asymptote is built as a progression rather than a single all-or-nothing product.-- **Asymptote Open Source** is the open-source foundation, built on Agent Beacon. It captures supported agent activity across local endpoints, CI jobs, and cloud-agent surfaces, then normalizes prompts, tool calls, file edits, commands, and related session events into records teams can inspect or forward into their own security tools.-- **Asymptote Managed** builds on that foundation with centralized ingest, retention, detections, fleet-wide visibility, policy controls, identity mapping, approvals, and investigation workflows.-- **Private Deployment** is for teams that need dedicated infrastructure, tighter data boundaries, or residency controls.+- **[Asymptote Open Source](/concepts/core-concepts#asymptote-open-source)** is the open-source foundation, built on [Agent Beacon](/concepts/core-concepts#agent-beacon). It captures supported agent activity across local endpoints, CI jobs, and cloud-agent surfaces, then normalizes prompts, tool calls, file edits, commands, and related session events into records teams can inspect or forward into their own security tools.+- **[Asymptote Managed](/concepts/core-concepts#asymptote-managed)** builds on that foundation with centralized ingest, retention, detections, fleet-wide visibility, policy controls, identity mapping, approvals, and investigation workflows.+- **[Private Deployment](/concepts/core-concepts#private-deployment)** is for teams that need dedicated infrastructure, tighter data boundaries, or residency controls.That gives teams a practical path:@@ -50,7 +50,7 @@ That gives teams a practical path:Use these rules of thumb:-- Choose **Asymptote Open Source** if you want open-source telemetry across supported local, CI, and cloud agent surfaces, normalized records you control, and customer-managed forwarding into your SIEM or observability stack.+- Choose **Asymptote Open Source** if you want open-source telemetry across supported local, [CI](/concepts/core-concepts#ci-telemetry), and [cloud agent](/concepts/core-concepts#cloud-agent-telemetry) surfaces, normalized records you control, and [customer-managed forwarding](/concepts/core-concepts#customer-managed-forwarding) into your SIEM or observability stack.- Choose **Asymptote Managed** if you need centralized operations across endpoints, users, and teams.- Choose **Private Deployment** if managed capabilities are right, but you need stronger infrastructure ownership or data-isolation requirements.diff --git a/docs/guides/inventory.mdx b/docs/guides/inventory.mdxindex be6d54ea..fdbcd594 100644--- a/docs/guides/inventory.mdx+++ b/docs/guides/inventory.mdx@@ -125,6 +125,10 @@ Inventory reads local endpoint state only. It does not authenticate to remote Sa## View Results+<Frame caption="Review runtime configurations, inventory status, and local telemetry coverage from the Inventory view.">+ <img src="/images/agent_runtime_configurations.png" alt="Beacon dashboard Inventory view showing agent runtime configurations and coverage state." />+</Frame>+### Runtime Coverage States- **Installed:** the runtime or executable appears to be present locally.diff --git a/docs/inventory/agent-harnesses.mdx b/docs/inventory/agent-harnesses.mdxindex e5e78a9f..ef34bc11 100644--- a/docs/inventory/agent-harnesses.mdx+++ b/docs/inventory/agent-harnesses.mdx@@ -16,6 +16,10 @@ Use it to answer:## Coverage States+<Frame caption="Use Agent Harness Inventory to compare installed, configured, managed, and observed state across supported runtimes.">+ <img src="/images/agent_harness_inventory.png" alt="Beacon dashboard Agent Harness Inventory view showing supported runtimes and coverage states." />+</Frame>+`beacon endpoint inventory` summarizes each supported harness with coverage states that are useful for deployment review:| State | Meaning |diff --git a/docs/inventory/mcp-servers.mdx b/docs/inventory/mcp-servers.mdxindex 4db8e938..29ccf08d 100644--- a/docs/inventory/mcp-servers.mdx+++ b/docs/inventory/mcp-servers.mdx@@ -38,6 +38,10 @@ sudo beacon endpoint inventory --system --all## Expected Versus Unexpected Servers+<Frame caption="Review MCP server inventory to see configured servers, source paths, scopes, and runtime context.">+ <img src="/images/mcp_server_inventory.png" alt="Beacon dashboard MCP Server Inventory view showing configured MCP servers and their source context." />+</Frame>+Treat MCP inventory as a local configuration review. For each server, compare the reported name, source path, scope, and runtime context with the server list your team expects.Common review questions:diff --git a/docs/inventory/skills.mdx b/docs/inventory/skills.mdxindex 9c9088ad..d98c92d6 100644--- a/docs/inventory/skills.mdx+++ b/docs/inventory/skills.mdx@@ -11,6 +11,10 @@ Beacon inventory can help identify local skill manifests under supported skill r## What Inventory Can Infer Today+<Frame caption="Use Skills Inventory to review local skill manifests, scopes, hashes, and parser status.">+ <img src="/images/skills_inventory.png" alt="Beacon dashboard Skills Inventory view showing local skill manifests and metadata." />+</Frame>+Use `beacon endpoint inventory --all` to review skill metadata alongside harness, MCP server, hook, and config state:```bash title="Show skill inventory"diff --git a/docs/log-forwarding/cloudwatch.mdx b/docs/log-forwarding/cloudwatch.mdxindex e2c90cdf..cd1fc604 100644--- a/docs/log-forwarding/cloudwatch.mdx+++ b/docs/log-forwarding/cloudwatch.mdx@@ -5,7 +5,7 @@ description: "Forward Beacon endpoint events into AWS CloudWatch Logs with custo## Forwarding Overview-Beacon `v0.0.42` added AWS CloudWatch Logs support for teams that want Beacon endpoint events forwarded into a customer-managed CloudWatch Logs log group for observability, security search, subscriptions, exports, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed Vector agent tails that file and writes parsed Beacon events to CloudWatch Logs.+Beacon `v0.0.42` added the [AWS CloudWatch Logs content pack](/concepts/core-concepts#aws-cloudwatch-logs-content-pack) for teams that want Beacon endpoint events forwarded into a customer-managed CloudWatch Logs log group for observability, security search, subscriptions, exports, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed [Vector forwarding](/concepts/core-concepts#vector-forwarding) agent tails that file and writes parsed Beacon events to CloudWatch Logs.Use this path when you want Beacon events forwarded to AWS CloudWatch Logs without storing AWS credentials, profiles, IAM roles, log group retention settings, stream names, or encryption settings in Beacon endpoint configuration.diff --git a/docs/log-forwarding/gcs.mdx b/docs/log-forwarding/gcs.mdxindex e889fb2c..6900f9f2 100644--- a/docs/log-forwarding/gcs.mdx+++ b/docs/log-forwarding/gcs.mdx@@ -5,13 +5,14 @@ description: "Forward Beacon endpoint events into Google Cloud Storage with cust## Forwarding Overview-Beacon `v0.0.38` added Google Cloud Storage support for teams that want Beacon endpoint events stored in a GCS bucket for data lake, SIEM, archive, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed Vector agent tails that file and uploads gzip-compressed NDJSON objects to GCS.+Beacon `v0.0.38` added the [Google Cloud Storage content pack](/concepts/core-concepts#google-cloud-storage-content-pack) for teams that want Beacon endpoint events stored in a GCS bucket for data lake, SIEM, archive, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed [Vector forwarding](/concepts/core-concepts#vector-forwarding) agent tails that file and uploads gzip-compressed NDJSON objects to GCS.Use this path when you want Beacon events forwarded to Google Cloud Storage without storing Google Cloud credentials, service accounts, workload identity settings, bucket IAM, lifecycle, retention, or encryption settings in Beacon endpoint configuration.<Info>- This page covers **local endpoint** GCS forwarding. For provider-managed cloud- agent sandboxes, see [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) or+ This page covers **local endpoint** GCS forwarding. For+ [provider-managed cloud agent telemetry](/concepts/core-concepts#cloud-agent-telemetry),+ see [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) or[Cursor Cloud Agents](/runtimes/cursor-cloud-agents). Cloud agents currently support GCSas the only self-serve artifact destination, with AWS S3 and SIEM destinationsplanned.diff --git a/docs/log-forwarding/index.mdx b/docs/log-forwarding/index.mdxindex 11fff1cf..42fb52dc 100644--- a/docs/log-forwarding/index.mdx+++ b/docs/log-forwarding/index.mdx@@ -5,13 +5,13 @@ description: "Forward Beacon endpoint events from local JSONL into SIEMs, log ag## Forwarding Overview-Beacon writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) as JSONL. The active [runtime log](/concepts/core-concepts#runtime-jsonl-log) is the handoff point for local review, customer-managed log pipelines, log aggregators, object storage exporters, and most SIEM content packs. Beacon can also enable optional collector exporters for [Splunk HTTP Event Collector (HEC)](/concepts/core-concepts#splunk-hec) and [CrowdStrike Falcon LogScale HEC](/concepts/core-concepts#falcon-logscale-hec) during endpoint install or repair.+Beacon writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) as JSONL. The active [runtime log](/concepts/core-concepts#runtime-jsonl-log) is the handoff point for local review, [customer-managed log pipelines](/concepts/core-concepts#customer-managed-forwarding), log aggregators, object storage exporters, and most SIEM content packs. Beacon can also enable optional collector exporters for [Splunk HTTP Event Collector (HEC)](/concepts/core-concepts#splunk-hec) and [CrowdStrike Falcon LogScale HEC](/concepts/core-concepts#falcon-logscale-hec) during endpoint install or repair.Use the subpages below by destination category. SIEM pages are for destinations that become investigation or detection systems. Log aggregation pages are for customer-owned pipelines and observability stores that tail local JSONL. Object storage pages are for archival or data lake export. Local pages cover the default runtime log and dashboard source.-For ephemeral CI jobs, see [CI Telemetry Exports](/log-forwarding/ci-telemetry-exports) for workflow artifacts, S3/GCS upload, and downstream handoff patterns over the completed CI `runtime.jsonl` file.+For [ephemeral CI jobs](/concepts/core-concepts#ci-telemetry), see [CI Telemetry Exports](/log-forwarding/ci-telemetry-exports) for workflow artifacts, S3/GCS upload, and downstream handoff patterns over the completed CI `runtime.jsonl` file.-For provider-managed cloud agents, see+For [provider-managed cloud agents](/concepts/core-concepts#cloud-agent-telemetry), see[Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) or[Cursor Cloud Agents](/runtimes/cursor-cloud-agents). Cloud agents currently supportGoogle Cloud Storage as the self-serve artifact destination; AWS S3 and SIEM@@ -239,7 +239,7 @@ See [Google Cloud Storage forwarding](/log-forwarding/gcs) for IAM, object layou### Vector log forwarding-Beacon `v0.0.26` added generated Vector configs to the Sumo Logic and Rapid7 content packs, Beacon `v0.0.37` added a Vector AWS S3 content pack, Beacon `v0.0.38` added a Vector Google Cloud Storage content pack, Beacon `v0.0.42` added a Vector AWS CloudWatch Logs content pack, and Beacon `v0.0.49` added a CrowdStrike Falcon Vector path. Use these templates when you want a customer-managed host agent to tail Beacon's local `runtime.jsonl` and forward events without storing destination secrets in Beacon endpoint configuration.+Beacon `v0.0.26` added generated Vector configs to the Sumo Logic and Rapid7 content packs, Beacon `v0.0.37` added a Vector [AWS S3 content pack](/concepts/core-concepts#aws-s3-content-pack), Beacon `v0.0.38` added a Vector [Google Cloud Storage content pack](/concepts/core-concepts#google-cloud-storage-content-pack), Beacon `v0.0.42` added a Vector [AWS CloudWatch Logs content pack](/concepts/core-concepts#aws-cloudwatch-logs-content-pack), and Beacon `v0.0.49` added a CrowdStrike Falcon Vector path. Use these templates when you want [Vector forwarding](/concepts/core-concepts#vector-forwarding) to tail Beacon's local `runtime.jsonl` and forward events without storing destination secrets in Beacon endpoint configuration.```bash title="Generate the integration pack"beacon endpoint sumo install-pack --system --output ./beacon-sumo-pack@@ -256,7 +256,7 @@ For managed endpoint deployments, install Vector through your normal endpoint to### Customer-managed forwarding-For another SIEM, observability store, archive, or pipeline, configure a customer-managed forwarder to read the Beacon runtime log and preserve each JSONL line as one event. See [Customer-managed log pipelines](/log-forwarding/customer-managed) for the dedicated forwarding contract.+For another SIEM, observability store, archive, or pipeline, configure a [customer-managed forwarder](/concepts/core-concepts#customer-managed-forwarding) to read the Beacon runtime log and preserve each JSONL line as one event. See [Customer-managed log pipelines](/log-forwarding/customer-managed) for the dedicated forwarding contract.Recommended settings:diff --git a/docs/log-forwarding/microsoft-sentinel.mdx b/docs/log-forwarding/microsoft-sentinel.mdxindex ca2c3736..6c4878d9 100644--- a/docs/log-forwarding/microsoft-sentinel.mdx+++ b/docs/log-forwarding/microsoft-sentinel.mdx@@ -5,7 +5,7 @@ description: "Forward Beacon endpoint events into Microsoft Sentinel with Azure## Forwarding Overview-Beacon `v0.0.32` added Microsoft Sentinel support for teams that want Beacon endpoint events in Log Analytics and Sentinel hunting workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Azure Monitor Agent tails that file and sends new records through a Data Collection Rule (DCR) into a custom Log Analytics table.+Beacon `v0.0.32` added the [Microsoft Sentinel content pack](/concepts/core-concepts#microsoft-sentinel-content-pack) for teams that want Beacon endpoint events in Log Analytics and Sentinel hunting workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Azure Monitor Agent tails that file and sends new records through a Data Collection Rule (DCR) into a custom Log Analytics table.Use this path when you want Sentinel ingestion without storing Azure tenant IDs, client secrets, workspace IDs, DCR identifiers, or ingestion endpoints in Beacon endpoint configuration.diff --git a/docs/log-forwarding/s3.mdx b/docs/log-forwarding/s3.mdxindex 8798d0b6..0e75180e 100644--- a/docs/log-forwarding/s3.mdx+++ b/docs/log-forwarding/s3.mdx@@ -5,7 +5,7 @@ description: "Forward Beacon endpoint events into AWS S3 with customer-managed V## Forwarding Overview-Beacon `v0.0.37` added AWS S3 support for teams that want Beacon endpoint events stored in an S3 bucket for data lake, SIEM, archive, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed Vector agent tails that file and uploads gzip-compressed NDJSON objects to S3.+Beacon `v0.0.37` added the [AWS S3 content pack](/concepts/core-concepts#aws-s3-content-pack) for teams that want Beacon endpoint events stored in an S3 bucket for data lake, SIEM, archive, or downstream detection workflows. Beacon remains the local JSONL producer and writes one source of truth, the active [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log). Your customer-managed [Vector forwarding](/concepts/core-concepts#vector-forwarding) agent tails that file and uploads gzip-compressed NDJSON objects to S3.Use this path when you want Beacon events forwarded to S3 without storing AWS credentials, bucket policy, lifecycle, retention, or encryption settings in Beacon endpoint configuration.diff --git a/docs/runtimes/index.mdx b/docs/runtimes/index.mdxindex e471471d..741aad60 100644--- a/docs/runtimes/index.mdx+++ b/docs/runtimes/index.mdx@@ -10,8 +10,8 @@ Asymptote supports multiple [runtime surfaces](/concepts/core-concepts#runtime-sThese 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.-- **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.+- **[CI](/concepts/core-concepts#ci-telemetry)**: 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](/concepts/core-concepts#cloud-agent-telemetry)**: Provider-managed cloud agents can write session telemetry from the cloud sandbox to customer-managed storage, while [SDK integrations](/concepts/core-concepts#observe-sdk) instrument agent applications that run in servers, serverless functions, workers, and hosted agent platforms.## Support matrixdiff --git a/images/agent_harness_inventory.png b/images/agent_harness_inventory.pngnew file mode 100644index 00000000..9cfee1b8Binary files /dev/null and b/images/agent_harness_inventory.png differdiff --git a/images/agent_runtime_configurations.png b/images/agent_runtime_configurations.pngnew file mode 100644index 00000000..1dd86b6fBinary files /dev/null and b/images/agent_runtime_configurations.png differdiff --git a/images/mcp_server_inventory.png b/images/mcp_server_inventory.pngnew file mode 100644index 00000000..20f44c50Binary files /dev/null and b/images/mcp_server_inventory.png differdiff --git a/images/skills_inventory.png b/images/skills_inventory.pngnew file mode 100644index 00000000..450e643cBinary files /dev/null and b/images/skills_inventory.png differ