v0.7.6

What's Changed

• Installer and sweep never require host PyYAML to read streaming keys (ST1-F1) by @shiftedx in #381
• Rooms on a gateway with no Hermes endpoint (R1, V1-F1) by @shiftedx in #380
• Release v0.7.6 by @shiftedx in #382

Full Changelog: v0.7.5...v0.7.6

v0.7.5

What's Changed

• fix(provisioner): edit the live box config, force the recreate, own the URL by @shiftedx in #354
• fix(provisioner): recreate the box gateway only when its env or config changed by @shiftedx in #355
• docs: add CHANGELOG and a release policy by @shiftedx in #356
• docs: handoff for the single-gateway dev topology by @shiftedx in #357
• fix(bots): a create Hermes accepted never answers 404 by @shiftedx in #358
• Add per-chat workspace execution and provider connections by @shiftedx in #359
• Recover Hermes creation and correct idle bot status by @shiftedx in #360
• test(config-lane): pin the runtime bot providers shape and fix contract drift for rows 36 and 41 by @shiftedx in #361
• Support silent additive Windows installs for Hermes and CozyAgents by @shiftedx in #363
• Stop owned retry launchers during Windows gateway repair by @shiftedx in #364
• feat: carry scoped MCP repair proposals through approvals by @shiftedx in #367
• Make fresh Windows prerequisites and Hermes launchers reliable by @shiftedx in #365
• feat: declare per-server MCP repair policy metadata by @shiftedx in #368
• Add durable Task lifecycle and commands (capability 64) by @shiftedx in #369
• Add durable Artifact records and independent delivery (capability 65) by @shiftedx in #370
• Typed scoped approvals with payload binding and category policy (capability 66) by @shiftedx in #371
• CozyApps dashboard records: saved values, action receipts and the typed document envelope (cozyapps 2, row 67) by @shiftedx in #372
• Derive Artifact records from legacy attachment deliveries (capability 65, additive) by @shiftedx in #373
• Typed phone capability request lifecycle and Task completion push (capability 68) by @shiftedx in #374
• Join declared Artifacts to their Task by Run identity; unstated mark stays unstated (capability 65, additive) by @shiftedx in #375
• Hermes attach plugin: consistent session keys, typed failures for dropped turns and unheld steers (HF1) by @shiftedx in #376
• Never lose a reply to a stale native turn: hello reconciliation, steer promotion, orphan rescue (capability 69, HF2) by @shiftedx in #377
• Phone-created Hermes bots stream by default; sweep and installer repair existing profiles (ST1) by @shiftedx in #378
• Release v0.7.5 by @shiftedx in #379

Full Changelog: v0.7.4...v0.7.5

v0.7.4

Fixed: bots created from CozyChat now become ready on their own

On a native install (install.sh), creating a Hermes bot from the phone used to hang on the incubation screen and then show "gateway setup needed" forever. The gateway created the profile but nothing on the machine provisioned its attach binding, and cozygateway repair aborted on such a profile because Hermes copies the launch profile's token into every new one.

The gateway now runs the installer's own provisioning unattended after a bot is created or deleted from the phone, and the installer mints a fresh token instead of reusing a copied one. The row moves setup_required → starting → ready with nobody at a terminal. The run restarts the gateway service once; the app already tolerates that. (#353)

Also in this release

• Installs interrupted mid-way are recovered on the next run, and an update preserves the existing listener, public origin, tokens, and owned services. (#347, #348)
• Windows: the installer records the Node identity it installed and starts Hermes compatibly after a reboot or logoff. (#352)
• Runners: the gateway sends a complete hello acknowledgement, so a paired computer attaches on the first try. (#346)
• Public readiness: bounded WebSocket and Compose ingress, verified CozyAgents installer, pinned supply chain, attested release artifacts. (#340)

What to do

Re-run the one-liner or cozygateway repair on each machine. A bot that is already stuck at "gateway setup needed" becomes ready after the update's repair run; if it does not within a minute, delete it from the phone and create it again.

Windows installs still do not auto-provision phone-created bots; run cozygateway repair after creating one.

Full changelog: v0.7.3...v0.7.4

v0.7.3

Durable installation and maintenance

Installation, update, and repair are now transactional: every step records what it owns, a failed or interrupted run rolls back to the previous working state, and the next run finishes the job instead of starting over. Gateway maintenance status is persisted and exposed to the app. (#335)

Known issue, fixed in v0.7.4

A Hermes bot created from CozyChat on a native install stays at "gateway setup needed" and cozygateway repair fails on it with "Hermes profiles must have distinct CozyGateway attach tokens". Update to v0.7.4.

Full changelog: v0.7.2...v0.7.3

v0.7.2

Built and qualified locally under Node.js 24. Build, typecheck, unit, contract, conformance, bundle, installer, provisioner, and plugin rollout gates passed. The native Windows installer suite was not executed on this macOS host and remains explicitly unverified for this tag.

Full Changelog: v0.7.1...v0.7.2

Full Changelog: v0.7.1...v0.7.2

CozyGateway v0.7.1

Built and qualified locally on Node 24 from commit 7e7dbcc. Full monorepo build, typecheck, tests, bundle, attach-health, Hermes installer dry-run, harness-choice, bot-provisioner, and plugin-rollout gates passed. Capability 61 adds authenticated, exact-bot recovery for a terminal failed CozyAgents runtime. It atomically preserves identity, credential, runner assignment, generation, and the original stored runtime spec while minting one fresh operation, with replay and clock-skew fencing. Windows validation remains explicitly unverified on this release host.

Full Changelog: v0.7.0...v0.7.1

v0.7.0

Built and qualified locally on Node 24 from commit 55a1e84. Full monorepo build, typecheck, tests, bundle, attach-health, Hermes installer dry-run, harness choice, bot provisioner, and plugin rollout suites passed. Capability 60 adds durable session deletion and memory ownership with old-peer compatibility and privacy-safe scheduled payload cleanup. The Windows installer suite was not run on a Windows host for this tag; Windows validation remains explicitly unverified.

What's Changed

• feat(runners): runner pairing, roster, multi-tenant runner lane, CozyAgents-only gateway (capability 52) by @shiftedx in #326
• feat(bots): POST /bots/:name/routines/:id/run (capability 53) by @shiftedx in #328
• feat(installer): all-in-one flow with a harness choice (CozyAgents by default) by @shiftedx in #327
• feat(bots): a create picks a computer, and the queue is per runner (capability 54) by @shiftedx in #329
• feat(installer): offer the CozyAgents harness on Windows (I8b) by @shiftedx in #330
• feat(runner-v1): a person can rename a paired runner (capability 55) by @shiftedx in #331
• feat(attach-v1): approval events can carry a sanitized detail sentence (capability 56) by @shiftedx in #332
• feat(bots): capability 57, the per-bot guardrail level on the profile lane by @shiftedx in #333
• feat(bots): capability 58, the operator guardrail ceiling on the profile read by @shiftedx in #334

Full Changelog: v0.6.5...v0.7.0

What's Changed

• feat(runners): runner pairing, roster, multi-tenant runner lane, CozyAgents-only gateway (capability 52) by @shiftedx in #326
• feat(bots): POST /bots/:name/routines/:id/run (capability 53) by @shiftedx in #328
• feat(installer): all-in-one flow with a harness choice (CozyAgents by default) by @shiftedx in #327
• feat(bots): a create picks a computer, and the queue is per runner (capability 54) by @shiftedx in #329
• feat(installer): offer the CozyAgents harness on Windows (I8b) by @shiftedx in #330
• feat(runner-v1): a person can rename a paired runner (capability 55) by @shiftedx in #331
• feat(attach-v1): approval events can carry a sanitized detail sentence (capability 56) by @shiftedx in #332
• feat(bots): capability 57, the per-bot guardrail level on the profile lane by @shiftedx in #333
• feat(bots): capability 58, the operator guardrail ceiling on the profile read by @shiftedx in #334

Full Changelog: v0.6.5...v0.7.0

v0.6.5

What's Changed

• Wave 2: runtime bots in rooms, auditable ids, config lane (capabilities 46 to 48) by @shiftedx in #314
• fix(media): let runtime bots use the media side channel by @shiftedx in #315
• feat(runner): create runtime bots from CozyChat through a runner lane (capability 49) by @shiftedx in #317
• feat(history): bot history lane for runtime bots (capability 50) by @shiftedx in #318
• fix(memory): tell the app when a runtime bot negotiated memory_setup (#319) by @shiftedx in #320
• feat(rooms): approval, clarify, and tool activity on runtime members' room turns (capability 51) by @shiftedx in #322
• feat(attach): advertise the bots capability version on hello_ack by @shiftedx in #323
• fix: stop Windows gateway supervisor during updates by @shiftedx in #321
• chore: release v0.6.5 by @shiftedx in #324

Full Changelog: v0.6.4...v0.6.5

v0.6.4

What's Changed

• Native runtime Bots: config-declared, Hermes-free roster rows (capability 45) by @shiftedx in #311
• Release 0.6.4 with model setup and gateway controls by @shiftedx in #312
• Keep gateway maintenance alive with a locked-down sidecar by @shiftedx in #313

Full Changelog: v0.6.3...v0.6.4

v0.6.3

What's Changed

• Fix CozyApps detail responses for strict clients by @shiftedx in #310

Full Changelog: v0.6.2...v0.6.3