Skip to content

✨ Betty F: action requests in meetings (issue, RFC, Spek session, knowledge item), spoken or typed, approved in the dashboard #18406

Closed

Description

@clubanderson

Part of #18391. Builds on #18392 (Betty engine).

People can ask Betty to do something in hive during a meeting, spoken or typed in the meeting chat: open an issue, open an RFC, start a Spek session, or save a knowledge item. Examples: "Betty, open an issue for the lobby timeout", "make that an RFC", "start a Spek session on calendar sync", "save that as a knowledge note".

Behaviour:

  • Betty detects the request (addressed by name, speech or chat), drafts the item from the request and the recent meeting context (title, short body, target repo when clear, link back to the meeting and transcript excerpt), and confirms in the meeting chat: "Drafted an issue: '<title>'. It's waiting for approval in the hive." If the request is unclear she asks one clarifying question first.
  • Speaker identity in a meeting is only a display name, so nothing is created directly. Every draft lands in an approval queue in the dashboard (Calendar/Inbox approvals) with the meeting context attached. An owner or read-write user approves, edits or rejects it.
  • On approval: issue or RFC through hive's normal issue path on the chosen monitored repo, Spek session through the existing Spek destination (spek_rfc), knowledge item into the vault. Betty posts the result link in the meeting chat if it is still live, otherwise it shows in the meeting notes.
  • Config (Meeting attendee settings tab, ✨ Betty E: Settings tab "Meeting attendee" with persona presets, voice, language, accent and email #18396): enable/disable actions, which action types are allowed, default repo, and an optional per-type auto-approve (off by default for all types; knowledge notes are the only candidate).
  • Her persona never claims an action was done before approval.
  • Tests: transcript and chat replays for each action type, clarification path, approval/reject flows, no creation without approval, prompt-injection text treated as data.

Activity

  1. added
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    kind/featureCategorizes issue or PR as related to a new feature.
    on Nov 16, 2026
  2. self-assigned this
    on Nov 16, 2026
  3. clubanderson commented on Nov 16, 2026

    @clubanderson
    MemberAuthor

    working this in a PR now (starts once #18392 lands)

  4. added a commit that references this issue on Nov 16, 2026
    e4ce816
  5. added 3 commits that reference this issue on Nov 16, 2026
    245007a
    e2c25ff
    56a4a87
  6. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

  7. added a commit that references this issue on Nov 16, 2026
    d9bc333
  8. clubanderson commented on Nov 16, 2026

    @clubanderson
    MemberAuthor

    Shipped in #18424 (merge d9bc333). Every meeting draft waits in Calendar, Drafts from meetings, for owner or read-write approval; only knowledge notes can be auto-approved (meetings.persona.actions).

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

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions