Oh My Subagents v0.3.2

Operator and provider reliability

• Operator tool rejections now return concrete validation guidance and are distinguished from genuinely uncertain outcomes, so a rejected request can be corrected without unsafe replay.
• Workflow authoring uses a faster, leaner action path, treats supplied Workflows as structural references, and can discover the current Codex model catalog instead of inventing model names.
• Background Codex and Claude provider processes no longer open visible console windows on Windows.

Configuration and CLI fixes

• Task starts preserve configured provider defaults when a Member does not explicitly override them.
• Guided setup remains compatible with Click 8.5 prompt typing.

Upgrade

Upgrade an existing OMS installation with pipx upgrade oh-my-subagents.

This release does not add a database schema migration.

Oh My Subagents v0.3.1

Migration safety fix

• oms init now stops before creating a second default controller database when legacy Banksia state exists.
• Migration preflights every destination before copying files or changing a service.
• Migration refuses to copy state while a foreground or unmanaged controller still owns the API bind target.
• systemd uninstall preserves its unit and surfaces the native error when disable --now fails.
• The README now separates fresh installation from the required Banksia upgrade order and links accidental 0.3.0 recovery.

Upgrade

Existing OMS installation: pipx upgrade oh-my-subagents

Existing Banksia installation: do not run oms init first. Install oh-my-subagents, run oms migrate-from-banksia, then oms db upgrade and verify service status.

Oh My Subagents 0.3.0

Highlights

• Completes the canonical backend rename to Oh My Subagents across the Python package, default application directories, SQLite database, provider environment, new Task roots, prompt documents, MCP bindings, native services, development infrastructure, documentation, and release verification.
• Adds oms migrate-from-banksia, an explicit and idempotent migration that copies legacy default state into canonical OMS locations, renames banksia.persistence to oms.persistence, renames banksia.env to oms.env, and replaces an installed legacy native service while preserving whether it was running.
• Retains the legacy source state for rollback and refuses to overwrite conflicting OMS state. Custom data paths, database URLs, and existing PostgreSQL schemas remain configured in place.
• New Tasks use .oms/. Existing Tasks keep their persisted .banksia/ roots and remain readable without rewriting immutable file references.
• Keeps the deprecated banksia command and BANKSIA_* environment compatibility during the 0.3.x migration window; new output and configuration use OMS identities.
• Installed-distribution verification now covers the migration twice, canonical package resources, Console serving, API health/readiness, durable Task readback, and native user-service lifecycle.

Upgrade from 0.2.0

Migration is explicit; ordinary startup never moves existing state automatically.

pipx upgrade oh-my-subagents
oms migrate-from-banksia
oms db upgrade
oms service status --json

For a pre-0.2 Banksia installation, custom paths, PostgreSQL, rollback details, or manual service handling, follow the migration guide.

Full changelog: v0.2.0...v0.3.0

Oh My Subagents 0.2.0

Highlights

• Banksia is now Oh My Subagents: a local runtime that turns ad-hoc parent/subagent delegation into durable, supervised, accountable work.
• The new PyPI distribution is oh-my-subagents, with oms as the canonical CLI.
• The runtime now presents the OMS identity consistently across the CLI, Console, API metadata, prompts, docs, examples, packaging, and CI.
• The README now explains the durable delegation model and shows a concrete multi-wave bug-fix example.
• OMS_* environment variables are canonical. Existing BANKSIA_* variables and the banksia CLI remain supported during 0.2.x with deprecation warnings and conflict detection.
• Existing data remains in the stable Banksia protocol locations: the banksia Python import, .banksia Task workspaces, banksia.persistence, configured PostgreSQL schemas, and native service identifier are intentionally unchanged.
• Installed-distribution verification now covers wheel/sdist identity, both CLI entry points, isolated initialization and reset, server health/readiness, packaged Console assets, durable Task restart, and Windows service lifecycle.

Upgrade from Banksia

Stop the existing controller before replacing the distribution:

banksia service stop
pipx uninstall banksia
pipx install oh-my-subagents
oms service install

Then confirm the migrated installation:

oms --version
oms service status

No database reset, data copy, or workspace rename is required. See Migrate from Banksia for compatibility details and rollback guidance.

Banksia 0.1.7

Highlights

• Reworked the Windows service lane behind a dedicated Task Scheduler 2.0 COM boundary, and taught it to recognize wrapped not-found errors so status, stop, and uninstall no longer misreport an already-absent task.
• Hardened background services across all three host lanes. banksia service restart now stops, waits for genuine controller shutdown, and only then starts, with the same shutdown wait shared by systemd, launchd, and Task Scheduler.
• Added workspace availability probing and per-workspace admission coordination. Task admission serializes recovery and commit for each workspace, and an unreachable Task root is detected without creating or repairing workspace files.
• Fixed ACL handling for existing Windows directories, plus native workspace file and security path handling.
• Added a real macOS background-service lifecycle probe to CI, exercising install, start, restart, and uninstall against an isolated per-run home.
• Refined the Run Studio member context layout in the Console, and updated js-yaml to a patched release.

Upgrade

pipx upgrade banksia
banksia service restart

This release registers no schema change, so an existing database needs no banksia db upgrade. The Windows host contract is unchanged: Windows 11 x64 on a local NTFS volume, with UNC, network, device, non-NTFS, and reparse-point workspace paths remaining unsupported.

Banksia 0.1.6

Highlights

• Added native Windows 11 x64 support for local NTFS workspaces, including handle-relative filesystem safety, protected private-path ACLs, Job Object process-family control, and a per-user Task Scheduler service.
• Kept one portable workspace contract across Linux, macOS, and Windows, including slash-separated logical file references and deterministic line-ending behavior.
• Strengthened database reset/upgrade verification, SQLite handle cleanup, Command Run process identity, and installed-distribution proof across supported Python versions.
• Added complete Windows CI for Python 3.12, 3.13, and 3.14, plus package, Console, runtime, and installed service-lifecycle verification.
• Updated Console dependencies to patched releases and cleared the known npm audit findings.

Upgrade

pipx upgrade banksia
banksia db upgrade
banksia service restart

banksia db upgrade creates a backup before applying an eligible schema change. Windows support requires Windows 11 x64 and a local NTFS workspace; UNC, network, device, non-NTFS, and reparse-point workspace paths remain unsupported.

Banksia 0.1.5

Highlights

• Added live Steer for active Members. A bounded message reaches the exact
  running Codex or Claude session and is preserved in Banksia Activity.
• Run Studio now loads complete paginated Activity and Command history instead
  of stopping at the initial summary window.
• Failed and timed-out Commands remain visible in Command history without being
  mislabeled as user action required.
• Retired the experimental OpenClaw provider route. Banksia Tasks and Operator
  now use the managed Codex and Claude integrations only.

Upgrade

pipx upgrade banksia
banksia service restart

This release does not require a database upgrade. Installations that previously
selected OpenClaw must choose Codex or Claude before starting new work.

Banksia 0.1.4

Highlights

• Added safe database backups and a supported forward upgrade path for existing
  Banksia controller data.
• Made watchdog recovery resumable: a user Resume refreshes the replacement
  budget while preserving historical Dispatch records.
• Made Task workspaces version-control neutral. Banksia no longer rejects,
  modifies, or assumes a Git policy for .banksia/ content.
• Stabilized Workflow and Run Studio interactions and added always-available
  YAML export for the visible Workflow draft.
• Upgraded the Console to React Router 8.3.0, closing the three prior Dependabot
  alerts.

Upgrade

pipx upgrade banksia
banksia db upgrade
banksia service restart

banksia db upgrade verifies the exact predecessor and creates a backup before
changing an existing controller database. Fresh installations can continue with
banksia init.

Building the Console from source now requires Node.js 22.22 or newer. Ordinary
PyPI installations receive the prebuilt Console.

Banksia 0.1.3

Banksia 0.1.3

Banksia 0.1.3 is a macOS compatibility and packaging reliability release.

Highlights

• Fix banksia init on macOS when the native ACL API reports that no extended
  ACL exists, addressing #4.
• Make concurrent first-time configuration more robust against a transient
  lock-file creation race on macOS.
• Treat macOS /var and /private/var temporary paths as the same canonical
  workspace, including Codex isolation checks.
• Install SQLAlchemy's required async runtime dependency on all supported
  architectures.
• Add real-macOS GitHub Actions coverage for focused initialization and the
  complete backend unit and integration suites.

Verification

• 642 backend unit tests pass on macOS.
• 488 backend integration tests pass on macOS, with 37 intentional skips.
• The release wheel and source archive pass twine check and the complete
  disposable installed-distribution verifier.

Upgrade

pipx upgrade banksia
banksia --version
banksia init

The expected version after upgrading is 0.1.3.

Banksia 0.1.2

Banksia 0.1.2 adds managed provider extension modes for Task Members.

Highlights

• Inherit enabled user and project Skills plus configured MCP servers for
  trusted Codex and Claude Tasks.
• Automatically narrow inherited extensions to isolated mode when filesystem or
  network access is restricted.
• Keep Operator isolated while preserving Banksia sandbox, approval,
  controller-authority, and banksia_node checks.
• Record requested and effective extension-mode provenance plus a sanitized
  Skill/MCP inventory on each managed Dispatch.
• Add Codex max reasoning support while preserving provider-native settings
  such as service_tier = "fast".
• Upgrade Claude Agent SDK to 0.2.128.
• Extend the Workflow schema, CLI, Console, OpenAPI contract, documentation,
  examples, and verification coverage.

Upgrade note

This release changes the controller schema. Back up any controller history that
you need to retain, then run banksia db reset before using an existing
nonempty database with 0.1.2.