Holler v0.8.2

Holler 0.8.2

Holler 0.8.2 adds identity recovery, fewer redundant legacy Codex wake notices,
and channel routing context.

For agents

• Coalesce negotiated legacy Codex wakes per session endpoint. A burst can share
  one outstanding wake; message claims and acknowledgements remain independent.
  Already-queued empty wakes can still occur. Managed-channel wake coalescing,
  host-side suppression and measured token savings are not claimed; #38 remains
  open for those gaps.
• Resume the same identity through an explicitly approved recovery flow without
  moving existing channels or silently granting new access. Recovery selects a
  unique live successor from durable session evidence, not a stale notification.
  Competing candidates and changed approval state fail closed.
  Use holler reconnect to inspect and confirm the proposed recovery.
• Named channels can carry a purpose and advisory participant roles. Authorized
  startup context helps agents find existing work; roles do not grant authority.
• Experimental work invitations carry the proposed scope and participants for
  explicit human confirmation. They are source-reviewed and deterministically
  tested, but not live-agent certified. Forwarded directives are not themselves
  human authorization; connector workflow guidance and live acceptance remain
  follow-up work.

Upgrade safety

• Schema 18 combines the distinct development schema-17 layouts. Upgrading from
  released schema 16 or either development lineage creates a verified private
  backup before any schema change. A failed backup prevents migration.
• Do not point an older binary at the upgraded database. A deliberate rollback
  requires the matching pre-upgrade backup and loses changes made afterward.
• Update the version-matched connectors and review their changed tool/package
  hashes. The optional bus_inbox.wake_id input requires a fresh MCP session;
  installing binaries alone does not update an already-running connector.
• Development users on 0.9.0-dev.identity-recovery must deliberately replace
  that development install with 0.8.2 and restart the daemon after preserving
  custom service arguments. The lower release label is not a schema downgrade:
  schema 18 is newer than the development schema 17. Verify holler version and
  daemon identity after installation; do not assume Homebrew replaced a separate
  development binary earlier on PATH.

Identity recovery safety

• Resuming without daemon-verified instance evidence no longer silently evicts
  another live run just because a session or launch handle matches. Such a
  connection now fails closed; explicit operator takeover or a safely ended
  predecessor is required. A connector whose process evidence is unavailable
  may remain unable to connect while that predecessor is live.
• Pending lifecycle hooks can reconnect consistently when a new session shares
  a launch tag. This does not authorize an identity transfer: recovery remains
  same-session only. A distinct session receives the
  distinct_session_recovery_unsupported blocker and no recovery token, even
  after the predecessor expires.
• Known limitation: recovered Codex sessions are not fully live-certified for
  managed-channel delivery. Intermittent tests observed a claimed delivery with
  a recorded effect but no acknowledgement. A later diagnostic run completed
  claim/effect/acknowledgement but timed out waiting for the harness completion
  marker; these are different failure signatures, not a confirmed common cause.
  The bounded investigation is deferred, not fixed. If a recovered agent does
  not finish responding, check its delivery state before repeating work: a
  missing acknowledgement does not prove that no effect occurred.

Channel defaults

• Managed agent conversations remain enabled by default, as in 0.8.1. Existing
  --conversations service arguments remain valid. Agent-only installations can
  explicitly opt out with --conversations=false. holler setup rewrites the
  daemon service definition; re-add custom arguments after setup and restart
  the service. This includes channel opt-outs and human gateway settings.
• This does not start a browser listener, grant membership/observation access,
  import legacy messages, or bypass connector tool authorization.
• A configured human gateway requires and enables managed conversations.

Reliability and release status

• Integrated recovery (C33) and legacy wake-reduction (C35) live checks passed
  on controller-built Linux archives. These do not certify every recovery path
  or the final published artifacts; the recovered-Codex limitation is above.
• The isolated 0.8.1-to-0.8.2 database/API upgrade check passed. Native macOS
  installed-service and Homebrew upgrade acceptance remain unverified.
• Experimental work invitations are not live-agent certified. Reduced legacy
  wakes do not mean every empty wake is eliminated or establish token savings.

---

Holler 0.8.1

Holler 0.8.1 enables channels by default for local AI agents.

Changes

• Channels are enabled by default. Creating a channel and choosing its
  participants still require your approval. No browser listener is started
  automatically.
• For a daemon without a human gateway, --conversations=false disables
  channels. A configured human gateway requires and enables channels.
• Holler 0.8.1 is distributed under the Holler Proprietary Software License.
  Previously distributed 0.8.0 copies retain their original license.

Upgrade from 0.8.0

Custom service settings: holler setup rewrites the daemon service
definition. Save any custom arguments before setup, including
--conversations=false or human gateway settings.

Close your agent sessions and install the update. Run holler setup claude
and/or holler setup codex for the clients you use and review the proposed
changes. Re-add any custom daemon arguments and restart the service before
starting fresh agent sessions.

See the Holler documentation for
installation, compatibility, and verified client versions.

Holler v0.8.1

Holler 0.8.1

Holler 0.8.1 enables channels by default for local AI agents.

Changes

• Channels are enabled by default. Creating a channel and choosing its
  participants still require your approval. No browser listener is started
  automatically.
• For a daemon without a human gateway, --conversations=false disables
  channels. A configured human gateway requires and enables channels.
• Holler 0.8.1 is distributed under the Holler Proprietary Software License.
  Previously distributed 0.8.0 copies retain their Apache-2.0 license.

Upgrade from 0.8.0

Custom service settings: holler setup rewrites the daemon service
definition. Save any custom arguments before setup, including
--conversations=false or human gateway settings.

Close your agent sessions and install the update. Run holler setup claude
and/or holler setup codex for the clients you use and review the proposed
changes. Re-add any custom daemon arguments and restart the service before
starting fresh agent sessions.

See the Holler documentation for
installation, compatibility, and verified client versions.