Skip to content

🐛 [v6] Dashboard chat !inception calls the retired /api/inception routes; move it to Inception (Spek) sessions or remove it #18565

Closed

Description

@clubanderson

Problem

On v6, the Dashboard chat command !inception (src/pkg/chat/inception.go) still calls /api/inception/start, /scan, /answer, /approve and /reset. #18419 retired those routes on 2026-11-16, and they now return "gone". So every !inception subcommand in v6 chat fails. Inception now runs as Spek sessions.

Proposal

  • Point !inception in chat at Inception (Spek) sessions: start a session, show its questions, record answers, submit, show state. Otherwise, remove the command and have chat reply with how to start an Inception session from the dashboard. Owner-only, as today.
  • Multi-line input. Carried over from ✨ feature: Dashboard chat: support sending a full !inception interview as one multi-line message #18261. When one message holds several !inception ... lines, either run each line as its own command in order, or refuse the whole message with a clear error. Never fold the later lines into the first answer. Report which lines ran.
  • Remove the dead route calls and the response types they used.

Done when

  • !inception in v6 chat either drives a Spek session end to end or is gone with a clear pointer.
  • A pasted multi-line interview behaves as described above.
  • Tests and docs are updated.

Supersedes #18261.

Activity

  1. self-assigned this
    on Nov 17, 2026
  2. added
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    kind/bugCategorizes issue or PR as related to a bug.
    on Nov 17, 2026
  3. hivecommons-hive commented on Nov 17, 2026

    @hivecommons-hive
    Contributor

    Thanks for filing this issue! To help us reproduce and investigate, could you please include the commit SHA of the build you're running?

    You can find it by running:

    git rev-parse --short HEAD
    

    Or check the bottom of the console UI for the version string.

    This issue will be on hold until a SHA is provided. Simply add a comment with the SHA and the label will be automatically removed.

  4. hivecommons-hive commented on Nov 17, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @Karibhou released (lease revoked).

    Claim history
    • 2026-11-17 01:18 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-17 01:18 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-17 01:21 UTC — released by Karibhou (contributor; lease revoked)
    • 2026-11-17 01:55 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-17 01:55 UTC — released by Karibhou (contributor; lease revoked)
  5. 11 remaining items

  6. added
    stage/020-claimedClaimed by the scanner or a relay contributor
    stage/stalledIn its current stage longer than expected
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    on Nov 17, 2026
  7. removed their assignment
    on Nov 18, 2026
  8. clubanderson commented on Nov 18, 2026

    @clubanderson
    MemberAuthor

    Owner go-ahead: option B. Remove the !inception chat command and keep a stub that answers any subcommand with a pointer to the dashboard Sessions section (owner-only; refuse multi-line input with a clear error). The routes were retired in #18419 and the interactive flow now lives in /api/sessions, so wiring chat to Sessions (option A) is out of scope. Hive agents may open the PR; the assignee and human claim have been cleared.

  9. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 18, 2026
  10. hivecommons-hive commented on Nov 18, 2026

    @hivecommons-hive
    Contributor

    Fixed by #18878 (merged 14b3d78). Closing. Reply /reopen if the problem persists.

  11. clubanderson commented on Nov 18, 2026

    @clubanderson
    MemberAuthor

    Delivered by #18878 (merged to v6, 14b3d78): the !inception chat command is now a stub that points to the dashboard Sessions section (owner-gated subcommands unchanged, multi-line input refused). Option B per the owner's go-ahead.

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

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.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