For Individual Developers

Validate a local Beacon setup and inspect AI agent activity on your own machine

Use this path when you want to try Asymptote Open Source on your own machine before a team rollout.

The developer setup uses per-user paths and writes endpoint events to ~/.beacon/endpoint/logs/runtime.jsonl.

1. Install Beacon

brew tap asymptote-labs/tap
brew install beacon
beacon endpoint install

See Asymptote Open Source for install details and runtime-specific notes.

2. Confirm collection health

beacon endpoint status
beacon endpoint discover

status confirms the local collector is running. discover shows the supported agent harnesses Beacon can see on your machine.

3. Inspect local activity

Open the dashboard to review runtime inventory, timelines, filters, and event details from local Beacon logs.

beacon endpoint dashboard --open

Beacon writes supported prompt, tool, command, file, approval, and runtime context when source runtimes emit it. See Endpoint event schema for event fields and examples.

4. Add hooks if needed

Some runtimes need user- or project-scoped hooks for richer telemetry.

beacon endpoint hooks install --harness cursor
beacon endpoint hooks status --harness cursor

Restart the selected runtime after installing or removing hooks. See Runtime hooks for supported harnesses, setup, status checks, and uninstall steps.

5. Clean up

Remove endpoint service files when you are done testing. Use --keep-logs if you want to preserve local runtime logs.

beacon endpoint uninstall --keep-logs

Related

Asymptote Open Source

Install Beacon and understand the files it manages.

Endpoint agent

Install, repair, inspect, and uninstall the local endpoint agent.

Runtime hooks

Install, check, and remove supported hook-based endpoint telemetry.

Local testing

Validate endpoint health, events, dashboard access, MCP access, and logs.