Skip to main content

​
Overview

beacon memory is the local review workflow for turning selected Beacon traces into approved project memory. The commands are grouped by resource:
  • beacon memory evaluations run|list|show
  • beacon memory candidates list|show|approve|reject|supersede
  • beacon memory skills preview|install
All subcommands accept the common endpoint and project-scope flags: Beacon stores learning artifacts in memory.db next to the resolved endpoint base directory for the runtime log. The store is durable local state and is scoped by the resolved project ID, so approved memory for one repository is not automatically returned for another.

​
Evaluate traces

Preview selected traces and estimated Jev calls without a network request:
Evaluate one trace with TypeSafe Jev:
Useful flags:
  • --trace <id> evaluates one trace ID.
  • --harness <name> filters traces by harness.
  • --since <rfc3339> and --until <rfc3339> bound the trace window.
  • --limit <n> and --page <n> page through selected traces.
  • --query <text> or -q <text> searches trace text before evaluation.
  • --jev-model <model> selects the Jev model, such as jev-latest or a pinned version.
  • --jev-endpoint <url> overrides the TypeSafe System One endpoint.
  • --jev-api-key <key> overrides API key lookup.
  • --jev-cost-per-trace <usd> changes the dry-run cost estimate.
  • --timeout <duration> sets the Jev request timeout.
  • --json prints machine-readable output.
--jev-api-key defaults to TYPESAFE_API_KEY, then BEACON_JEV_API_KEY. --jev-endpoint can also come from BEACON_JEV_ENDPOINT, and the model can come from BEACON_JEV_MODEL. List and inspect stored evaluations:

​
Review candidates

List generated candidates:
Filter candidate review queues:
Inspect one candidate:
Approve a candidate into project memory:
Reject or supersede candidates:
Approving creates an approved memory record for the resolved project. Rejecting and superseding preserve the review transition with the optional --reason so later reviews can explain why a candidate was not installed.

​
Install Agent Skills

Preview the skill content without writing:
Install the skill into the project:
Beacon writes:
Existing files are not overwritten unless you pass --force. Skill files include Beacon provenance so future reviewers can trace the generated instruction back to the approved memory and source trace. Installation is a write to the current project or the path passed with --project; it is never triggered by endpoint hooks or MCP reads.

​
MCP retrieval

beacon mcp serve exposes approved memory as read-only MCP tools:
  • search_memory
  • get_memory
  • get_memory_context
These tools let future agents retrieve approved project knowledge regardless of which harness originally produced the trace. The local dashboard also includes a read-only Memory page showing evaluation, candidate, and approved-memory counts. Mutating actions still live in this CLI workflow.

​
Network boundary

beacon memory evaluations run is the only command in this workflow that can call Jev, and only when it is not run with --dry-run. Beacon hooks and normal endpoint capture remain local-only and do not call Jev.