Skip to content

buzz: a hosted harness loses every channel's conversation and sandbox on each deploy (buzz-acp session/new after restart) #774

Closed

Description

@jhgaylor

What happens

A hosted Buzz agent's harness (Fountain.Buzz.Harness, buzz-acp in the pod) restarts on every deploy — Horde moves it to the new pod. buzz-acp keeps its channel→ACP-session map in memory only (crates/buzz-acp/src/pool.rs, SessionState.sessions: HashMap<Uuid, String>) and never calls session/load/session/resume; after a restart the next mention in a channel gets a fresh session/new. Through fountain acp that is a new conversation and a new sandbox. Observed 2026-08-16 with FizzTheShark: after the harness restart (#773), a DM continued in a new conversation f313b4e4 instead of 1d239529; the old sandbox is suspended with the workspace on it, unreachable from Buzz.

With ~24 deploys/day, a hosted agent's per-channel context and workspace last hours. Buzz's own base prompt assumes the opposite ("after a session restart, resume silently — rebuild state from your todos, memory…" — a persistent cwd).

Why the gateway cannot fix it alone today

session/new from buzz-acp carries cwd, mcpServers, _meta.sessionTitle (agent + channel name, DMs get no name), and _meta.systemPrompt. No channel id — the only channel-id carrier is BUZZ_GIT_ORIGIN_CHANNEL_ID, and only for stream channels with MCP servers configured. The id does appear in the first prompt's [Context] Channel: DM (#…) text, which is not a key to build on.

Proposed

  1. Upstream (block/buzz), the real fix — drafted alongside this issue: (a) _meta.channelId / _meta.channelType on session/new; (b) buzz-acp persists channel→session per identity and calls session/load on restart when the agent advertises loadSession (Fountain does), falling back to session/new.
  2. Gateway sticky resume (once 1a lands, or as _meta becomes available): fountain acp maps (identity, channelId) → conversation and treats session/new for a known channel as a resume of that conversation, so continuity does not depend on buzz-acp's memory.
  3. Fountain-side, independent of upstream: a Buzz identity's new conversations reuse the identity's previous sandbox/workspace (or a per-identity persistent volume), so memory/todos survive even when the ACP session does not. Matches Buzz's "rebuild from your workspace" contract and is worth doing regardless of 1/2.

Related: #773 (harness spec replay), ADR 0020.

Activity

  1. jhgaylor commented on Aug 17, 2026

    @jhgaylor
    CollaboratorAuthor

    Gateway half shipped in #775 (channel-bound conversations, hosted buzz-acp built from the fork). Remaining: #776 (repin to upstream when block/buzz#6088 ships), #778/#779 (24 h-ceiling cliff, deferred — not worried about 24 h agents for now).

  2. jhgaylor commented on Aug 22, 2026

    @jhgaylor
    CollaboratorAuthor

    Closing — the reported break is fixed on the build we ship; the one remaining idea is better tracked elsewhere.

    Conversation continuity across a deploy works today. #775 added the gateway sticky resume: session/new carrying _meta.channelId maps (identity, channel) to a conversation and resumes it rather than creating one (cli/internal/acp/session.go:126,186 → Conversations.start_or_resume_conversation/2). A hosted harness runs our pinned buzz-acp, which sends that member, so a Horde move on deploy no longer strands the channel. The suspended sandbox comes back with the conversation (ADR 0017), so the workspace returns too.

    Where each proposal landed:

    Nothing here is lost: #776 for the pin, #805 for the persistent workspace, #936 for the ceiling that still costs an agent its memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions