Release Notes

Scion release notes are published weekly.

Latest: Week of September 28 – October 4, 2026

Raw keystroke messaging was replaced by a dedicated agent keys API (scion keys), and raw message delivery is now removed. A timezone overhaul pinned servers, storage and APIs to UTC and made the Hub the only source of an agent’s TZ. Agent delete became asynchronous and failure-aware, and asynchronous create arrived as an opt-in. Kubernetes gained per-agent NFS workspaces, Workload Identity and a new Substrate runtime. Security work continued with user access token boundaries, frozen delegation ceilings and project access granted only through role bindings.

Read the full release notes for this week ->

Timezone handling changes

During the week of September 28 (release notes), timezone handling changed: the Hub sends every timestamp in UTC with Z, the web dashboard has a per-user display timezone and a 24-hour clock, and cron schedules are UTC only. The runtime-profile timezone setting introduced the week before (release notes) has been removed: an agent’s TZ now comes from its pin, TZ environment variables on the Hub, or the Hub default timezone. See Times and Timezones for the full behaviour and the operator steps after upgrading.

Deleted built-in harness configs and templates stay deleted

A deleted built-in harness config (for example claude) or the built-in default template no longer comes back when the Hub restarts or is upgraded (ptone/scion#3544). This also applies to harness configs left unselected in the setup wizard. The Hub records each built-in it has seeded in the builtin_resources_seeded Hub setting, and startup only creates built-ins that are not in that record. Built-ins that are new in a release are still added, and built-ins you keep still receive content updates.

Until the explicit restore command arrives (scion harness-config restore and scion templates restore, the second phase of ptone/scion#3544), the only way to bring a deleted built-in back without re-creating it by hand is to remove the ledger row directly in the Hub database (DELETE FROM hub_settings WHERE section = 'builtin_resources_seeded';) and restart the Hub. This is not available through the admin settings API. The restart re-creates every missing built-in, including others you deleted and harness configs left unselected in the setup wizard, so delete any you do not want again afterwards.

Upgrade note: on the first start after upgrading, the Hub has no record yet, so built-ins you deleted since the last restart before the upgrade reappear once. Delete them again and they stay deleted.

Migration guides

Migrating from raw message delivery: raw keystroke delivery through messages is removed. scion message --raw fails before sending anything, and any message request that still carries raw is refused with 422 raw_input_removed. Use scion keys or POST .../keys instead.
Migrating from grove names: the grove→project rename.

Previous Weeks

Looking for older release notes? See the Prior Release Notes Archive for daily entries from the early development period (Feb–Jul 2026).