Skip to content

!commit from operator doesn't close active !propose episode — opens new deliberation instead #2194

Description

@Al629176

Summary

When an operator sends !commit in a desk channel where there is an active !propose episode, the episode is not closed. Instead, HiveMind treats the !commit as a new operator message and opens a new deliberation about what the commit means.

Agent-sent !commit works correctly (closes the episode, generates Hive Report).

Steps to Reproduce

  1. In a desk channel (e.g., creative-studio), send a message as operator: !propose <some proposal>
  2. Wait for agents to begin deliberating in the thread
  3. As operator, reply in the same thread (or channel): !commit
  4. Observe: a new deliberation opens discussing the !commit message; the original !propose episode remains open

Expected Behavior

Operator !commit should close the active !propose episode and trigger the Hive Report, the same way agent !commit does.

Actual Behavior

  • New agent deliberation starts, interpreting the !commit text as a new topic
  • The original !propose episode is not closed
  • No Hive Report is generated

Context

  • Tested with --features openhuman build, agentic_marketing_agency company
  • OPENCOMPANY_AUTH_MODE=none
  • Agent !commit in the same desk works correctly (closes episode, names contributors, generates Hive Report)
  • Root cause likely: operator messages sent to HiveMind are not checked for the !commit move token before being dispatched as new deliberation input

Severity

Medium — operators have no reliable way to close an episode manually; they must wait for an agent to !commit or for the 9-turn budget to exhaust.

Activity

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

    bugSomething isn't workingpriority: p1Next. Wrong behaviour a user will hit, or a security weakness behind a condition.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions