Skip to content

✨ feature: Dashboard chat: support sending a full !inception interview as one multi-line message #18261

Closed as not planned

Description

@kanrenibm

Use case

An operator pastes the whole inception interview into Dashboard Hive Chat as one message: answer 1 to answer 7, submit, approve, one per line. Only the first line runs. The rest becomes text inside answer 1. The operator gets no warning.

Test on the v6 edge spoke, as owner:

  • The paste is chat seq 81: 709 characters, 8 newlines, 9 !inception tokens.
  • The bot sends one reply: ✅ Recorded answer 1 (1 of 7)….
  • The audit has no inception_answer and no inception_approve after the paste. The phase stays clarify, and answers is {}.
  • After a separate !inception submit, answers.language is 689 characters. It is the paste without the !inception answer 1 prefix. It has 9 lines and 8 !inception tokens.
  • The state has only the key language. Questions 2 to 7 have no answer.
  • The language constitution fact has the same 689-character body.
  • The scaffold is lang=go, while the answer starts with C++ CLI application….
  • A separate !inception approve works: inception_approve is in the audit.

The reply to submit is ✅ Submitted 1 answers. The remaining 6 questions use their defaults. Nothing says that the answer holds other commands.

Affected: operators who run inception through chat and paste several commands.

Proposed solution

When one chat message has several lines that start with !, run each line as its own command, in order. Each command sends its own reply, as if it had been sent alone.

A message with a single command behaves as today.

Alternatives considered

Free-text description. The operator writes a paragraph or multiple paragraphs or a engineered prompt or text ref, not commands. The agent maps it to the questions, shows what it understood for the operator to confirm, and asks only about the gaps. This matches how people describe a project. It is a larger change, because the agent step decides the result. It also changes the fixed 5–7 question flow in brainstorm-advisory.md.

Workaround today. Send one command per message. This works, but it gives no hint to the operator that a paste is stored as one answer.

Scope and compatibility

  • Target branch or version: v6.
  • Operator impact: a pasted block of !inception commands runs as written. Today it stores 9 lines as one answer.
  • Contributor/agent impact: the chat router, src/pkg/chat/router.go, handles one command per message.
  • Migration or backwards-compatibility concerns: a message with one command is unchanged. Behaviour for lines that do not start with ! is not specified here. Unprefixed replies were not tested.

Additional context

By the code at 15a6de7fc:

  • routeMessage (src/pkg/chat/router.go:118-125) strips the first ! and splits once on the first space. cmd is inception. args is the rest of the message, newlines included.
  • cmdInception (src/pkg/chat/inception.go:69-75) takes the next word as the subcommand. rest is everything after it.
  • cmdInceptionAnswer (src/pkg/chat/inception.go:206-233) splits rest once on a space. The first part is the number. The second part is the whole remainder of the message. It is stored as the answer.
  • No inbound code splits a message into several commands. The Split("\n") calls in src/pkg/chat/ are for SSE parsing, outbound message splitting and error summaries.
  • docs/inception.md:122-136 describes one command per message. It does not mention a multi-line paste.

Environment: Hive Hub spoke on Kubernetes, https://availableslotlke648397260827-9hmc-k3sw.lke.hive.hivecommons.dev, branch v6, channel edge, commit 15a6de7fc (release 6.30.1). Operator kanrenibm, role owner. Date 2026-11-15.

Timeline (UTC):

12:28:34  inception_start
12:32:28  chat.dashboard.message seq=81    (the paste)
12:33:52  chat.dashboard.message seq=84    (!inception state: only question 1 has a check mark)
12:34:20  chat.dashboard.message seq=86    (!inception submit)
12:34:20  inception_answer count=1
12:37:46  chat.dashboard.message seq=91    (!inception approve)
12:37:47  inception_approve

Related: the scaffold language in this run is not C++. That is a separate bug.

Not determined:

  • Whether the brainstorm agent used the other six answers from inside the stored text. The facts mention those topics, but the kick text is not logged in full.
  • Other chat backends were not tested. Only Dashboard Hive Chat.

Full logs: logs/step0_* to logs/step5_*.

logs.zip

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 15, 2026
  2. added
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Nov 15, 2026
  3. hivecommons-hive commented on Nov 15, 2026

    @hivecommons-hive
    Contributor

    Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label triage/accepted (configured in issue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.

  4. added
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    stage/stalledIn its current stage longer than expected
    on Nov 15, 2026
  5. clubanderson commented on Nov 17, 2026

    @clubanderson
    Member

    Closing as obsolete in its current form. #18419 (merged 2026-11-16) retired the inception API, and the v6 chat !inception command still calls those removed routes, so the whole command is currently broken, not just multi-line pastes. Tracked as #18565, which moves chat inception onto Inception (Spek) sessions or removes it, and carries forward your multi-line requirement: each line runs in order, or the message is refused clearly, and later lines are never folded into the first answer. Thanks for the thorough report.

  6. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor

    @kanrenibm this issue was closed by @clubanderson as not planned.

    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. removed
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    stage/stalledIn its current stage longer than expected
    on Nov 17, 2026
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

    enhancementNew feature or requesthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions