Public Development Record

SAM Changelog

We build SAM in the open where it helps customers: clear improvements, honest release status, and a deliberate path from headquarters proof to field deployment.

How to read this page: “Candidate” means proven in a controlled test ring, not automatically installed for every customer. Planned work is never a release promise.

Latest

Reliable memory and monitoring

These August 2026 improvements make SAM more dependable without weakening privacy or deployment safeguards.

AUG 13, 2026
Candidate

Monitoring became more dependable

We hardened the memory-recall monitor for the way macOS background services actually start, and improved repeat-alert behavior. A missing proof remains visible; it is not silently converted into “all clear.”

  • Background execution now finds the approved runtime path reliably.
  • Repeat owner alerts are reduced without suppressing new or material failures.
  • Field promotion remains gated on a clean headquarters proof.
ObservabilityFail closedRelease gates
AUG 10–11, 2026
Candidate / Dogfood

Memory now captures the work that matters

SAM’s governed memory work progressed from deterministic recall into practical continuity for ordinary conversations and work products.

  • Unified memory is the authoritative path for permitted facts and assignments.
  • Natural questions can retrieve relevant business context without requiring a special “remember this” command.
  • Durable assignments, decisions, work products, and dated snapshots can be captured during normal work.
  • Protected data is excluded at the capture boundary; current correspondence and historical context are kept distinct.
Memory continuityPrivacy boundariesTelegram-ready
AUG 12, 2026
Candidate / Dogfood

Cost reporting became invoice-safe by design

Fleet metering now separates what a deployment used from provider reconciliation, headquarters operations, development capacity, and prepaid cash activity.

  • Missing coverage or an unresolved provider mismatch blocks a customer invoice instead of guessing.
  • Optional agent capacity and development work remain distinct from customer deployment usage.
  • Headquarters cash reconciliation is aggregate and privacy-safe; it cannot turn an unverified estimate into a bill.
Fleet meteringBilling controlsPrivacy-safe
AUG 8, 2026
Candidate / Dogfood

A controlled release loop for every SAM

SAM now has a versioned delivery path designed for safe repetition across headquarters, dogfood systems, and future customer deployments.

  • Each candidate carries an exact release identity and verified manifest.
  • Installers preserve backup and rollback state.
  • Each system can detect its approved update without silently installing it.
  • Fleet observation shows release drift without collecting customer conversation content.
Versioned deliveryRollback-awareFleet readiness

Foundation

ToggleLogic routing and cost governance

SAM uses governed model selection technology. The public ToggleLogic Free release history is maintained separately because its public version contract is distinct.

JUN–AUG, 2026
Public releases

ToggleLogic Free 1.0.0 through 1.0.6

The public Free tier added reliable model pins, explicit pricing visibility, safe handling for unpriced or missing-usage calls, and owner-pin expiry safeguards.

Read the ToggleLogic Free changelog →

Model routingCost visibilityOwner controls

Our release policy

Proof before promotion

  1. Build and test a customer-safe artifact with an exact release identity.
  2. Prove it on headquarters and record the evidence.
  3. Promote it separately to a dogfood system when the headquarters gate is clean.
  4. Only then make it eligible for a customer deployment, with backup, rollback, and owner gates.