v0.6.0

BitCadence v0.6.0: the plain-language redesign

Why this release

BitCadence should feel like a calm control room, not a config file. v0.6.0 is the owner-approved redesign (design/redesign-v1/): plain words everywhere, no JSON, YAML, tokens or ports on screen in normal use, colour never the only signal, and every old mco command still working.

It was built the way BitCadence is meant to be used. A Score run had one AI build each slice and another review it, and a human-issued grant was required before anything touched the repository. Five slices were built and reviewed, then shipped as one pull request.

What's new

• Quiet start: bitcadence start runs in the background with a tray status light (a word plus green, amber or red), a one-time sign-in link instead of a pasted token, and start-at-sign-in for your user only, with no administrator needed.
• Home: what needs you, and what's running.
• Ask for something replaces the drag-and-drop builders. Type a request ("fix the login bug, then ask me before deploying"), see the plan drawn as steps with approval gates, and approve once. The console and bitcadence ask share one planner.
• Helpers: every AI helper with a health light and a word ("Ready", "Working", "Stuck", "Not connected"), what it's doing in plain words, Add a helper, and Fix it, which shows a dry run first and repairs only after you confirm.
• Connect an AI: one tap per app (Claude, Codex, Gemini/Antigravity, Cursor). It finds the app and adds BitCadence to its connection settings, keeping a backup of the original first.
• Schedules: "Every weekday at 2:00 AM" pickers instead of cron lines.
• Approvals: no raw permission errors. A missing approver right gives one sentence and a one-key fix.
• Settings: plain labels; addresses and masked sign-ins only under Show advanced.
• Shared GPU nights: an exclusive resource lease arbiter, so long jobs on one GPU don't trample each other.

Reliability fixes

• Score jobs dispatch above normal board traffic, and a late completion event no longer blocks a run (15-minute grace).
• A blocked or failed Score run pushes the owner one notification; stale alerts no longer replay.
• The push-notification topic lookup has a timeout and a cache, so a slow cloud call can't hold up startup.
• Helpers no longer mistake a Windows venv launcher and its child process for two copies.

License change

From v0.6.0, BitCadence Core is licensed under the Prosperity Public License 3.0.0, from Batoncadence LLC. It's source-available: free for personal and noncommercial use, and a business may use it for a 30-day trial, then needs a commercial license (see COMMERCIAL-LICENSE.md).

Not retroactive: releases up to and including 0.5.0rc1 were MIT and stay MIT for anyone who received them.

Upgrading

• Every old mco command and flag keeps working; --json stays on read commands, and exit codes are unchanged.
• The Flow Control page (/flow) and the visual workflow builder are removed. Workflow YAML still runs through bitcadence ask --file and mco workflow.

Full details are in CHANGELOG.md.

v0.5.0rc1

BitCadence v0.5.0rc1 — Jev public preview

This is a GitHub prerelease, not the stable 0.5.0 release. The documented
live AWS release-candidate chaos board remains the stable-release gate.

Why this release

The agent doing deep work should not spend its context on every small routing
or relevance judgment. BitCadence now has an optional two-speed path: TypeSafe
Jev returns typed, bounded semantic advice; Codex, Claude, and other workers
handle the longer work. Deterministic policy still owns capacity eligibility,
leases, budgets, human approval, and effects. Jev is not an approver or
autonomous conductor. We are not claiming a measured speed or cost gain.

What is in this preview

• Advisory Codex task routing, including deterministic model/capacity rules and
  a narrow mco_jev_route MCP entry point.
• Advisory Claude model routing and annotation-only Jev checks for Drumline,
  watchdog symptoms, and notification quality.
• Decision receipts and safe deterministic fallback when Jev is disabled,
  unavailable, or abstains. Jev remains disabled by default.
• The updated website and
  setup/authority guide.

Start safely

Install BitCadence as usual; no TypeSafe account is required for core work.
If you want Jev, configure the server-side key and shadow mode using the
PowerShell walkthrough,
then call the explicit connection test. Do not put the key in a browser, web
page, agent job, or repository. Keep shadow mode while reviewing receipts and
fallbacks. The dedicated Jev key form in the Admin Console is not yet shipped.

The Python package version is 0.5.0rc1; the CLI remains mco, with existing
MCO_* settings and ~/.mco paths unchanged. GitHub Actions attaches the
source distribution and wheel and builds the matching GHCR image. PyPI
publication is best-effort until trusted publishing is configured.

v0.3.0

What's Changed

• Governance close-out: audit trail, approval gates, escalation, workflow DSL, dashboard by @mastalink in #1
• BatonCadence Console + enterprise connectors + Mythos shared context by @mastalink in #2
• SaaS foundation: multi-tenant org isolation, guardrails, any-cloud packaging, CI, farm-out workflows by @mastalink in #3
• Rebrand MCOrchestr8 → BatonCadence (branding only; mco command/package unchanged) by @mastalink in #4
• Merge external audit remediations (Drumline hardening, dedup, retries) by @mastalink in #13
• UI/CLI parity phases 1+2: Drumline everywhere, live console, fleet admin by @mastalink in #14
• Operator polish + v0.3.0 release readiness (phases 3+4) by @mastalink in #17
• fix(security): stop POST /api/workflows from reading arbitrary local files by @mastalink in #18

New Contributors

• @mastalink made their first contribution in #1

Full Changelog: https://github.com/mastalink/Batoncadence/commits/v0.3.0