Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Update FAQ and v0.0.72 changelog

shukieshahb8ed2eb0862e
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index a6c9df4b..47ba8bcd 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -11,6 +11,12 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
## June 2026
+### v0.0.72 · June 18, 2026
+
+- **Inventory state separated from runtime activity** · Inventory heartbeat and snapshot telemetry now write to `inventory_state.jsonl`, keeping agent runtime activity in `runtime.jsonl` while preserving customer-managed forwarding paths.
+- **Claude Code MCP and skill inventory fixes** · Beacon inventories Claude Code MCP servers from `~/.claude.json` and follows symlinked Claude skill directories, so shared skill stores such as `.agents/skills` appear in endpoint inventory.
+- **Jamf S3 runtime and inventory forwarding** · The Jamf S3 Vector flow now forwards runtime and inventory JSONL to distinct S3 prefixes, supports MDM-injected AWS provider settings, normalizes older `.../runtime` prefixes, and reads initial inventory snapshots reliably.
+
### v0.0.71 · June 18, 2026
- **Inventory heartbeat telemetry** · Beacon can now emit metadata-only inventory heartbeat events for local agent harnesses, hooks, MCP servers, and skills, making endpoint coverage drift easier to inspect from the runtime log without collecting skill contents.
diff --git a/docs/concepts/faq.mdx b/docs/concepts/faq.mdx
new file mode 100644
index 00000000..11a6c727
--- /dev/null
+++ b/docs/concepts/faq.mdx
@@ -0,0 +1,65 @@
+---
+title: "FAQ"
+description: "Common questions about Asymptote Open Source, Agent Beacon, local telemetry, inventory, and forwarding"
+---
+
+## What telemetry does open-source Beacon capture?
+
+Open-source Beacon captures supported AI agent activity from configured local, CI, and cloud-agent surfaces. Depending on the runtime and integration mode, endpoint telemetry can include prompts, tool calls, shell commands, file activity, approvals, MCP-like tool use, model/session context, token usage, runtime-reported cost, and related event metadata.
+
+Beacon can also capture metadata-only local inventory for supported agent harnesses. Inventory can include detected runtimes, hook/config status, local MCP server metadata, and skill manifest metadata. For example, Beacon can inventory Cursor MCP servers from `mcp.json`, Claude Code MCP servers from `~/.claude.json`, and local skills under Cursor or Claude Code skill roots.
+
+Inventory is intentionally metadata-only. Beacon does not retain `SKILL.md` instruction bodies, MCP secret values, full environment values, full command arguments, or unrelated config contents in inventory events.
+
+## Where does open-source Beacon write data?
+
+For endpoint installs, Beacon writes runtime activity to `runtime.jsonl`.
+
+Inventory heartbeat telemetry is written separately to `inventory_state.jsonl` so runtime activity and configuration inventory can be routed or reviewed independently.
+
+Default user-mode paths:
+
+```text
+~/.beacon/endpoint/logs/runtime.jsonl
+~/.beacon/endpoint/logs/inventory_state.jsonl
+```
+
+Default system-mode paths:
+
+```text
+/var/log/beacon-agent/runtime.jsonl
+/var/log/beacon-agent/inventory_state.jsonl
+```
+
+## Does open-source Beacon require a hosted account?
+
+No. Beacon endpoint collection is local-only by default. It does not require a hosted Beacon account, remote policy fetch, or external network dependency during normal local hook execution.
+
+You can keep logs local, inspect them with the local dashboard and CLI, or forward them to customer-managed destinations such as S3, Wazuh, Elastic, Datadog, Sumo Logic, Rapid7, Falcon LogScale, Splunk HEC, or Microsoft Sentinel.
+
+## Does Beacon send secrets or skill contents downstream?
+
+Beacon applies redaction, sanitization, truncation, and event-size controls before writing endpoint events.
+
+Inventory records are conservative by design:
+
+- Skill inventory includes names, paths, hashes, scope, modified time, and parser status, but not skill instruction bodies.
+- MCP inventory includes server name, source config path, transport, command basename, argument count, safe environment key names/counts, and hashes, but not secret values or full environment values.
+- Config inventory includes file metadata, hashes, parser status, and counts, but not full unrelated config contents.
+
+## How do I forward Beacon logs to S3?
+
+Use the Beacon S3 content pack or the packaged Jamf helper for managed macOS deployments.
+
+The S3 forwarder writes runtime and inventory logs to separate prefixes under the same bucket root:
+
+```text
+s3://<bucket>/<prefix>/runtime/date=YYYY-MM-DD/<object>.jsonl.gz
+s3://<bucket>/<prefix>/inventory/date=YYYY-MM-DD/<object>.jsonl.gz
+```
+
+For Jamf Pro deployments with MDM secret injection, see [Deploy Beacon With Jamf And S3](/guides/jamf-s3-mdm).
+
+## When should I use Asymptote Managed instead?
+
+Use open-source Beacon when you want local telemetry and customer-managed forwarding. Consider Asymptote Managed when you need centralized ingest, retention, search, detections, fleet-wide visibility, policy controls, identity mapping, approvals, SSO/RBAC, or investigation workflows operated as a managed service.
diff --git a/docs/docs.json b/docs/docs.json
index 5b45b0cf..65c01725 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -69,6 +69,7 @@
"icon": "book-open",
"pages": [
"concepts/core-concepts",
+ "concepts/faq",
{
"group": "System Architecture",
"root": "architecture/system-architecture",