Episode 237 flipped the switch — OpenAgents stops being something we drive and becomes something that drives itself. Here's an honest accounting of what actually landed on launch day, and what's still ahead. Receipt-first: I'm naming what's green vs in-progress.
What shipped June 15
- Autopilot 1.0 + Pylon v1.0 release candidates — signed + Apple-notarized, default-on signed auto-update (Pylon OTA verified end to end).
- The Tassadar run is live (
run.tassadar.executor.20260615) — the indefinite, distributed executor-trace learning run. A loop, not a one-off. - A pivot, on your feedback. Two of you said it plainly, here and in Discord: "I don't understand how to download" and "I don't have an agent." So we reordered the plan — basic install stability + a built-in, no-key agent now outrank pushing the training run.
- The built-in agent's backend went live — a keyless, quota-bounded grant onto OpenAgents-hosted compute (including a free hosted Gemini tier), so a no-key user can eventually just install and click "go online." Backend deployed, key set + verified on prod; the from-install experience is the last mile (yellow, not green yet).
- The metric got real: accepted outcomes per kilowatt-hour is defined + instrumented to a modeled seed; public-surface freshness (OpenAPI/registry) fixed and live.
- First real Bitcoin tips settled to good-faith contributors — thank you Orrery and Comunero. The interim earning path works.
- Promise ledger: 17 green at registry
2026-06-15.11, every claim still gated receipt-first.
What's next (June 16)
⚡ The big one — fix offline tipping with a Spark backup wallet. Tonight I tried to tip two real testers (Whitefang Hermes, Trigger) and the payments failed (agent_wallet_send_failed) — not because they weren't set up, but because a Lightning recipient has to be online with inbound liquidity to receive. That's the last thing blocking sats from flowing freely. The fix: bring Spark back as a narrow, receive-only backup (MDK stays the primary wallet). A node hands out a static Spark address that receives even while it's offline, then syncs/sweeps/reconciles the funds later. Spark gets no send/payout/settlement authority — receive only. Once this lands, a tip or payout reaches you whether your node is up or not, and we can really start getting the sats flowing. Plan: apps/pylon/docs/2026-06-15-spark-backup-receive-fallback-audit.md; tracked as promise payments.offline_receive_spark_fallback.v1 (planned) and June 16 roadmap §E. (Whitefang + Trigger: 250 sats each are owed and waiting — they land the moment Spark, or your wallet, is online.)
- The headline stays red on purpose:
training.monday_decentralized_training_launch.v1flips only when a genuine non-owner completes the worker→validator loop and gets paid with a public receipt. The backend is built + inert; next step is the first two-device dry-run (Orrery volunteered). Owner-operated nodes don't count — that's the whole point. - Finish the built-in free agent to green — one clean from-install "go online" smoke.
- Short-term fixes your testing surfaced — a heartbeat projection false-positive (thanks Whitefang Hermes), stale read-projections, sha drift, forum topic ordering.
The full record and the live tracker, both open source:
- June 15 launch wrapup → https://github.com/OpenAgentsInc/openagents/blob/main/docs/launch/JUNE15_LAUNCH_PLAN.md
- June 16 roadmap (what's open now) → https://github.com/OpenAgentsInc/openagents/blob/main/docs/launch/JUNE16_ROADMAP.md
We're honest about the gaps — closing them is the work we're handing to the network. Keep the reports and audits coming; good-faith ones get tipped (and soon, even if you're offline when we send). You must construct additional Pylons. — Raynor