0.3.0-beta.33 - 2026-10-12

⚡ Performance Improvements

• Reduce SQLite contention and query costs (#723)

🎉 Features

• Render session tool calls as verb + object rows on a work rail (#716)
• Attribute agent session messages, wake senders with replies, and isolate subagents in worktrees (#722)

🐛 Bug Fixes

• Fold transcript entries incrementally instead of replaying each turn (#715)
• Resolve Windows runtime failures and desktop context menus (#725)
• Reduce session startup and attention overhead (#731)
• Bound scheduled claim attempts before contention backoff

Release Notes

Breaking Changes

An agent can no longer send a session message to its own session

compozy__session_prompt now refuses a call whose session_id is the calling session. The call fails with invalid_request ("session_prompt cannot target the calling session.") and nothing is admitted. A self-prompt could only queue into, steer into, or interrupt the caller's own turn, so it never did useful work. Now that every session message carries its sender and can request a reply, it would also make a session reply to itself.

• Only calls made from an agent session to that same session are refused. Messages to other sessions, operator prompts from the CLI and HTTP, and compozy session prompt behave as before.
• A send admitted before the upgrade and retried with the same message_id and idempotency_key still returns its original result.

Migration notes: this ships without the usual one-release deprecation window. The exception is recorded in the agent-collaboration spec (Business Rule 18, ADR-002). To keep working in the same session, end the turn. To schedule work, use a subagent (compozy__subagent_delegate) or compozy session prompt from the operator.

0.3.0-beta.32 - 2026-10-09

♻️ Refactoring

• Complete Modern Go adoption across module boundaries (#706)

🎉 Features

• Show nested child runs and a distinct awaiting-child state (#708)
• Merge Jobs and Triggers into one Automations area (#709)
• Remove the memory feature family and adopt agent-native session compaction (#710)
• Delegate tasks to subagents with live cards, durable wakes, and operator surfaces (#711)

🐛 Bug Fixes

• Classify teardown survivors by final process liveness (#713)

🧪 Testing

• Cut duplicated and misplaced tests across the pyramid (#707)

Release Notes

Breaking Changes

Remove memory, Dream, and Knowledge; sessions use native agent compaction

CompozyOS now centers on local agent sessions, Tasks, Loops, Goals, and explicit Gateway access.
Agent memory, Dream consolidation, the Knowledge app, and the workspace knowledge/ prompt injector
are removed from all product surfaces with no compatibility aliases. CompozyOS also stops compacting
sessions itself: the agent owns its context window, every rebuild of a session into a new agent
session is bounded, and the agent's native compaction is observed and can be requested.

Migration

Back up compozy.db and the daemon state before upgrading, and export any memory database state you
need (index, decisions, Dream history) with the previous release first. Nothing needs editing by hand
after the upgrade; the daemon starts normally:

• Migration 00130_retire_memory.sql permanently drops the memory tables and
  goose_db_version_memory, deletes memory.consolidated automation triggers (run history stays),
  and deletes legacy dream, memory-extractor, and checkpoint-summary sessions. Migration
  00009_unarchive_compaction_spans.sql restores history that the removed CompozyOS compaction had
  archived (including its transcript entries), so old compacted sessions show their full history again.
• config.toml is archived on load: [memory], [roles.dream], [roles.checkpoint_summary],
  [roles.memory_extractor], [roles.memory_controller], [session.compaction], memory.consolidated
  trigger entries, and the hook-matcher keys compaction_reason / compaction_strategy move, commented
  and lossless, to the end of the same file under # Archived retired memory and compaction settings; these values are inactive.
  The daemon logs config.retired_keys_archived once. If the file cannot be rewritten (it changed
  concurrently, or it is read-only), the daemon logs config.retired_keys_archive_failed, loads with
  the retired values inactive, and retries on the next load; the start is never blocked.
• memory_policy in SOUL.md, retired compozy__memory* tool and toolset IDs in tool policies, and
  extension manifest entries memory.backend, memory/*, and memory.read|write, extension
  automation resources triggered by memory.consolidated, and the hook-matcher keys
  compaction_reason / compaction_strategy in AGENT.md and SKILL.md hooks are ignored with a
  warning. Saved desktop layouts drop the Knowledge window.
• Markdown memory files, knowledge/ directories, and ledger.jsonl files stay on disk and are no
  longer read. No file is deleted, and the session directories of the deleted legacy sessions are never
  recataloged. The ignore and archive rules are removed in v0.6.0.

Port scripts and extensions off compozy memory, /api/memory*, compozy__memory_*, the Host API
memory/*, and the memory.backend capability; no replacement memory feature is provided. New and
changed surfaces, all experimental: compozy session compact, POST .../sessions/{session_id}/compact,
compozy__session_compact, the Compact now action, the compaction transcript item, the reshaped
session.compaction_fired payload and usage markers, and observation-only context.pre_compact /
context.post_compact hooks with a compaction_trigger matcher.

There is no in-place downgrade. Restore a complete pre-upgrade backup before running an older binary.
See the migration guide for the state disposition
and integration changes.

Features

One Automations window for schedules, events, and links

The Web UI's separate Jobs and Triggers windows are now one Automations window. Every automation reads as one sentence — how it starts, optional conditions, what it does — with its last-run result and an On/Off switch on the row, so a failed run is visible without opening anything. One detail page and one "New automation" dialog serve schedules, events, and links; the start you pick decides whether CompozyOS stores a job or a trigger.

• last_run (id, status, started_at, ended_at, skip_reason) is on every job and trigger from compozy automation jobs|triggers, GET /api/automation/{jobs,triggers} (HTTP and UDS), and compozy__automation_{jobs,triggers}_{list,get}. The CLI tables gain a Last Run column; -o toon adds last_run_status and last_run_started_at.
• The list commands, routes, and tools accept target=agent|loop|task (--target on the CLI).
• The dock has one Automations launcher; the command palette gains "New scheduled automation" and "New automation on an event"; Loop pages replace "Add trigger" and "Add schedule" with Automate ▾; Settings → Automation uses plainer labels and writes the same config.toml keys.
• CLI verbs, HTTP/UDS routes, tool ids, and [[automation.jobs]] / [[automation.triggers]] are unchanged.

compozy automation jobs --workspace checkout-api -o json | jq '.jobs[] | {name, last_run}'
compozy automation triggers --workspace checkout-api --target loop

Migration notes:

• Saved desktops migrate permanently (window-manager snapshot v5): every Jobs or Triggers window, tab, and recently closed entry reopens as an Automations window on the matching /automations/… path, in the same place. No window is closed.
• Exported layout documents and window_layout resources at version 4 keep loading: the daemon upgrades them to version 5 and rewrites their Jobs and Triggers windows the same way. Snapshots and layout documents are version 5 from now on.
• Command palette pins, recents, and usage for the Jobs and Triggers commands merge into "Open Automations" and the Automations view; usage counts add up and no pin is dropped.
• Old web links /jobs, /jobs/<id>, /triggers, and /triggers/<id> redirect to /automations, /automations/jobs/<id>, and /automations/triggers/<id>, carrying their filters. The redirects are removed in v0.5.0.
• The app ids jobs and triggers (compozy window open --app, window commands, window_layout resources) and the palette ids app.open.jobs, app.open.triggers, palette.view.jobs, and palette.view.triggers are accepted as automations with a deprecation warning (CLI stderr; WARN logs windowmanager.app_id_deprecated and cmdpalette.command_id_deprecated). They are removed in v0.5.0 and then fail like any unknown id. Use automations, app.open.automations, and palette.view.automations.
• Site docs: the Automation section is now Automations, with two tutorials. /docs/automation/jobs and /docs/automation/triggers moved to /docs/automation/schedules and /docs/automation/events and redirect permanently.

0.3.0-beta.31 - 2026-10-07

🐛 Bug Fixes

• Apply the chosen runtime to continued sessions and keep continue/fork top-level (#702)
• Keep live model catalogs current without releases (#701)

🧪 Testing

• Cover inactive loop routes with automatic approval (#703)

0.3.0-beta.30 - 2026-10-06

🐛 Bug Fixes

• Preserve loop results under SQLite contention (#690)
• Repair profile isolation, runtime recovery, and loop results (#691)
• Skills nested
• Upgrade dependencies and repair CI compatibility (#692)
• Repair release validation and desktop restoration (#694)
• Preserve profile recovery guidance and repair browser validation (#695)
• Preserve SQLite commit outcomes during cancellation (#696)
• Preserve profile entry across query reconciliation (#697)

Release Notes

Fixes

Updated runtime dependencies and preserved profile icons

Upgrade Go runtime dependencies and the web/desktop toolchain, including the native TypeScript
checker, Bubble Tea installation wizard and CEL expression engine. Source builds require
Go 1.27.1. Existing profile icons retain their appearance when Lucide renames their symbols.
Restored desktop window frames appear before layout-heavy contents finish mounting.

Migration notes: profile reads and writes translate album, book-marked, building-2,
flip-horizontal-2, flip-vertical-2 and trash-2 to their canonical Lucide names without
discarding profile state. The boundary decoder is scheduled for removal in v0.5.0 after the
persisted names have been migrated. No operator action is required for this release.

Preserve terminal cleanup ownership when canceling a lane

Canceling a run-agent lane now records terminal session cleanup before generic cancellation
cleanup, preserving the exact session and binding epoch throughout settlement.

Recover profile entry during daemon reconnection

Fixed a Web route error when daemon reconnection replaces an in-flight profile-selection read. Navigation now waits for the current workspace's profile before loading scoped work, including when the workspace changes during reconnection.

Keep profile recovery guidance visible during retries

Profile recovery details now remain visible while the browser retries its window-manager registration. A successful registration or an explicit context switch clears the previous failure.

Resource-only extension manifests retain their declared paths

Extension manifests using the published string-array syntax for skills, agents, Loops, automation,
and layouts load again in TOML and JSON. The decoder translates each string into an unplaced path;
explicit profile placements and strict unknown-field validation remain intact. Build output uses
the current path/profile object form.

Migration notes: string-array input is accepted through v0.3.0-beta.30 and removed in
v0.3.0-beta.31. In handwritten sources, replace agents = ["agents"] with
agents = [{ path = "agents" }], or [[resources.agents]] followed by path = "agents".
Apply the same conversion to the other static resource families. Omit profile to preserve
all-profile visibility. Existing source files and installed resource state are not rewritten.

Preserve successful SQLite commits during cancellation

A request or persistence deadline arriving during a successful SQLite commit no longer reports that committed write as failed. This prevents persistence retries from duplicating completed tool events. Cancellation observed before commit still rolls back the write.

Restore saved windows after layout configuration is ready

Fixed desktop restoration briefly mounting an empty composer before saved window layout configuration was ready.

0.3.0-beta.29 - 2026-10-01

♻️ Refactoring

• Retire Network, managed Sandbox, and Bridges (#681)

🎉 Features

• Calmer, plain-language web UI for everyday users (#683)
• Continue and fork sessions across agents, with fallback account routes (#684)
• Shell rail v2 with light and dark themes (#687)

🐛 Bug Fixes

• Wake creator on child turn completion (#685)
• Resolve reported runtime, catalog and delivery failures (#686)
• Restore release nightly coverage and package extension runtimes

Release Notes

Breaking Changes

Remove Network, Bridges, and managed Sandbox products

CompozyOS now centers on local agent sessions, Tasks, Loops, memory, and explicit Gateway access.
Network, Bridges, and managed Sandbox capabilities are removed from all product surfaces with no
compatibility aliases. HEARTBEAT, SOUL, Task autonomy, Goal nodes, session supervision, attention
notifications, task status cursors, and provider-native execution policies remain supported.

Migration

Back up the daemon state and workspace .compozy/ directories before upgrading. Export any retired
product history using the previous release first. Migration 00121_retire_network_bridges_sandbox.sql
permanently drops Network state and wake runs, Bridge instances/routes/deliveries and task subscriptions,
notification presets/delivery permits, Network-actor triage state, and retired fields on retained records. It clears retained Task
references to removed Network wake runs and removes Loop channel-message events. Retained local sessions,
Tasks, ordinary runs, workspaces, memory, SOUL, and HEARTBEAT state are preserved.

Remove Network, Bridges, and managed Sandbox configuration and request fields. Port scripts and extensions
to the current CLI, routes, tools, and SDK; no replacement messaging or remote Sandbox feature is provided.
Gateway requirements move to [gateway] with gateway.private / gateway.public permission atoms,
gateway_requirement_digest, and --confirm-gateway-requirement / confirm_gateway_digest confirmation.
The previous Gateway consent tuple remains recorded. Legacy network_participation manifests must
be rebuilt with [gateway] and their new requirement digest confirmed; no legacy manifest conversion
or implicit Gateway authorization is provided.

There is no in-place downgrade. Restore a complete pre-upgrade backup before running an older binary.
See the migration guide for the
state disposition and integration changes.

Highlights

A calmer desktop shell with light and dark themes

The CompozyOS desktop is redesigned around flat chrome and edge-to-edge windows, and it now comes in
light and dark.

• The dock moves to a slim rail on the left. Its foot holds your profile, the theme toggle, and
  Settings. Below 960px it becomes a bottom tab bar with the same controls.
• The top bar runs the full width. Desktop dots and an All desktops button sit in its tray, next
  to the bell and the command palette.
• Windows tile edge to edge with no gaps. A single hairline separates them: drag it, or focus it and
  use the arrow keys (hold Shift for bigger steps), to resize the panes on both sides.
• New windows open as a tab in the window you are working in instead of floating on top of it; on
  an empty desktop they fill it. Option-click a rail icon to open it split beside your window,
  Shift-click to open it on a new desktop, or right-click it for every destination, including a
  floating window. compozy window open --floating and the floating input of
  compozy__window_open ask for a floating window explicitly.
• Window › Arrange offers Main and stack, Columns, Grid, and Balance sizes, and Window › Move
  window to sends a window to another desktop by name. compozy layout arrange and the
  compozy__layout_arrange tool accept the new main_stack arrangement, and an optional
  --keep-frames / keep_frames that arranges each named tab deck whole. Without it, every named
  window is still its own participant.
• Tabs look and behave like browser tabs, and window controls are quiet icons at the end of the head.
• An empty desktop asks "What should we work on?" above the session composer. Type a prompt and press
  Enter to start a session right there, with your project's default agent already picked.
• Sessions use the full width of their window again, tool calls read as quiet rows, and the list of
  sessions is open by default.
• Choose Light, Dark, or System in Settings › Appearance, or flip the theme from the dock.
  Dark stays the default. The choice is saved in this browser and applied before the first frame,
  and the terminal follows it.
• The interface uses Inter for text and Geist Mono for code, with higher-contrast secondary text in
  both themes.

Migration

Three [window_manager] defaults change. Your saved layouts, profiles, and any value you set
explicitly in config.toml are kept as they are; only unset values pick up the new defaults.

new_window_policy now accepts tab (the new default) and beside_focus (tile new windows beside
the focused one) alongside floating. To keep the previous behavior, set the old values explicitly:

[window_manager]
new_window_policy = "floating"

[window_manager.gaps]
inner = 8
top = 8
right = 10
bottom = 8
left = 10

[window_manager.bindings]
bottom_center = "reserved"

Or apply them from the CLI, for example
compozy config set window_manager.new_window_policy floating. Changes apply live. The theme is a
per-browser preference, not a config.toml key, so there is nothing to migrate for it.

0.3.0-beta.28 - 2026-09-27

🎉 Features

• Give rendered Markdown a readable visual hierarchy (#660)
• Add safe bulk worktree cleanup to workspace lists (#656)
• Add provider-neutral ACP full-access preference (#674)

🐛 Bug Fixes

• Preserve profile scope when deleting sessions (#652)
• Discover Claude reasoning options for each exact model (#658)
• Bootstrap pinned Bun with npm for Vercel builds
• Honor workspace default in session launcher (#668)
• Fixing clarify tool call timeout with keep-alive pings (#661)
• Preserve declared awaited run-loop terminal output (#672)
• Preserve whitespace in session transcripts (#670)

🧪 Testing

• Wait for terminal command output before detaching
• Refresh credential assertions context after migration

0.3.0-beta.27 - 2026-09-15

♻️ Refactoring

• Quiet the Context rail and sessions row for everyday use (#649)

🐛 Bug Fixes

• Goal delete session
• Reopen private Gateway files safely on Windows (#646)
• Report checkpoint role availability from compaction configuration (#645)
• Recover marketplace sources and render catalog logos under CSP (#648)
• Repair marketplace CI fixtures and evidence capture
• Cancel unbound goals before deleting sessions (#647)

0.3.0-beta.26 - 2026-09-15

🎉 Features

• Bulk actions for the sessions list (#619)
• Add built-in open-design extension (#625)
• Show session context and confirmed prompt deliveries (#635)
• Unify marketplace catalog and plugin sources (#636)
• Add release video workspace and production skill

🐛 Bug Fixes

• Recover stopped session deletion and queue polling (#614)
• Hide internal Goal prompts from the operator queue (#618)
• Recover owned task work after supervised silence stops (#621)
• Repair agent runtime and Goal workflows found in QA (#624)
• Recognize structured Claude authentication status (#632)
• Discover and bind models in provider overlays (#633)
• Preserve zsh startup directory semantics (#630)
• Preserve nested raw terminal input visibility (#631)
• Preserve unicode terminal prompt redraws (#634)
• Complete overlay admission and integration checks
• Render cursor edits in terminal quote lines
• Resolve terminal cwd from the bound session worktree (#641)
• Repair release integration and catalog compatibility
• Stabilize release integration under concurrent startup

🧪 Testing

• Await completed automation run before daemon cleanup

0.3.0-beta.25 - 2026-09-11

🐛 Bug Fixes

• Load knowledge memories without enabling automation (#590)
• Allow resizing maximized internal windows (#589)
• Delegate bounded native tools to orchestrated workers (#591)
• Emit profile scope from memory extraction (#592)
• Recover layout settings saves and expose apply results (#596)
• Confirm terminal termination when closing windows (#597)
• Reduce excessive CPU in connected sessions (#599)
• Bound session summaries and preserve complete details (#600)
• Reconcile Goal context and session lifecycle (#601)
• Preserve terminal creation scope and accessible title actions
• Preserve exact window titles and wait for reasoning controls
• Deduplicate delivered skill context and gate input-only roles (#607)
• Verify private Tailscale endpoints through tsnet (#608)
• Report effective dream role in memory health (#609)
• Group reasoning and tools in session work segments (#610)
• Add durable notification acknowledgement (#611)
• Complete notification review and main integration repairs
• Keep unread title counts current in background tabs
• Resolve notification integration Go lint findings
• Preserve escalation acknowledgement across neutral events
• Restore finished notifications and timeline disclosure behavior
• Synchronize attention delivery and durable loop state

🧪 Testing

• Wait for connected idle Skills prompt readiness
• Supply valid origins in acknowledgement fixtures
• Label unscoped attention story notifications
• Retain explicit global scope in attention fixtures
• Create escalation fixtures through their lifecycle
• Project escalation events in acknowledgement fixtures
• Persist canonical escalation status in overview fixtures

0.3.0-beta.24 - 2026-09-10

🎉 Features

• Add herdr bridge to community catalog (#560)

🐛 Bug Fixes

• Honor profile in operator tool catalog (#551)
• Tolerate unmatched terms in memory recall (#569)
• Scope startup tool guidance to session roles (#572)
• Preserve migrated state during update recovery (#574)
• Unify spec-cycle task completion semantics (#575)
• Preserve provider command routing for spawned sessions (#576)
• Preserve prior session profiles and bound metadata warnings (#578)
• Preserve native model reasoning capabilities (#579)
• Make memory opt-in and preserve pressure compaction (#580)
• Resolve post-merge shutdown and verification failures
• Keep loop authoring editable during validation
• Preserve profile scope across loop run views (#583)
• Preserve profile ownership in loop and memory runtimes (#582)
• Reserve shutdown time for required cleanup (#581)
• Retain the Global desktop across workspace catalog changes
• Repair release integration contracts and lifecycle cleanup
• Stabilize release lifecycle races and integration fixtures
• Respect startup and shutdown lifecycle contexts
• Preserve interrupted session identity and bridge progress bursts
• Preserve cancellation delivery and pending activity deadlines

🧪 Testing

• Enable memory for the knowledge browser journey
• Keep noncooperative ACP prompts alive after cancellation
• Select the desktop workspace before awaiting its client

Release Notes

Fixes

Memory and dreaming require explicit opt-in

CompozyOS is a control plane, so it no longer starts persistent memory extraction or background
dreaming from omitted settings. memory.enabled and roles.dream.enabled now default to false.
To enable memory, set memory.enabled = true in config.toml and restart the daemon. Dreaming
requires the separate roles.dream.enabled = true opt-in; enabling memory alone leaves it off.

The enabled extractor now requests an explicit no-candidate result, accepts conventional empty
responses and JSONL fences, and preserves valid candidates from mixed output. Malformed lines
remain diagnosable failures instead of silently disappearing. Extraction failures and timeouts
appear in the configured DLQ and extractor failure listing. Child-stop details distinguish failed
or timed-out extraction from a parsed child response; successful inbox production owns the
memory.extractor.completed event.

Session pressure compaction remains independently controlled by session.compaction.enabled.
It reuses checkpoint coverage and may launch a summary child when an active session reaches the
pressure threshold, even with persistent memory disabled. Idle sessions and session-end memory
updates do not start that work. An explicit checkpoint-role opt-out or a failed summary leaves
uncovered events unarchived.

Migration notes

No configuration is rewritten and no stored memory is deleted. Existing explicit true or false
values retain their meaning; omitted values use the new disabled defaults. Profile and workspace
role overrides keep their precedence under the daemon memory master switch. Existing public keys,
tools, routes, and response shapes remain available. Raw extraction failures require a new
extraction; replay remains limited to normalized candidate inbox failures. (#561)

Previous-release sessions remain readable after upgrade

Sessions created by 0.3.0-beta.21 remain readable after upgrading. The persisted
creation-profile codec accepts versions 4 and 5, validates their fields, and keeps
historical profile references, policy digests, and creation digests unchanged.
New runtime profiles continue to use version 5.

Unreadable session metadata now produces a bounded scan summary with at most five
examples. An unchanged set repeats at most once every five minutes per scanner;
changed failures are reported immediately. compozy doctor --only runtime.session_metadata -o json reports live counts and a bounded sample,
including missing or invalid catalog creation witnesses.

Migration notes: the version 4 to 5 change added optional ACP selections. Version
4 profiles upgrade through the persistence codec with no selections, preserving
their original bytes and hashes instead of rewriting immutable witnesses. No SQL
migration, config change, session deletion, or manual reset is required. Unknown
versions and corrupted witnesses remain rejected and unchanged. This does not
change dreaming defaults or claim to reproduce the reported CPU/disk measurements.