Repository navigation
Description
Use case
An operator who runs Inception only through chat is never told that a scaffold exists or how to get it.
Run on a spoke (greenfield, !inception start → 7 answers → !inception approve):
- After
✅ Submitted 7 answers., chat shows only agent status lines ([brainstorm] Completed,[supervisor] Completed). It does not say the scaffold is ready or that!inception approveis the next step. - The engine reached phase
scaffoldat 04:30:40 (-05:00, hive log:inception watcher: facts extracted, advancing to scaffold).GET /api/inception/scaffoldthen returned 13 files. !inception approvereplied with one line:✅ Inception approved and brainstorm re-paused.No file count. No download path.!inception statein phasescaffoldorcompletehas no scaffold line. By the code it prints the idea,Moving on with N of M answers.andFacts recorded: N(inception.go:176-185). Not run during this test.
Environment:
- Hive URL: https://availableslotlke648397260827-9hmc-k3sw.lke.hive.hivecommons.dev
- Surface: Dashboard Hive Chat panel, as
owner. - Hive: hub-managed spoke, branch
v6, channeledge, buildfd020b3.src/pkg/chatis unchanged in15a6de7(v6.30.1). - Date: 2026-11-15.
Code:
src/pkg/chat/inception.go:123-131returns the fixed approve line.cmdInceptionState(inception.go:154-190) never reads the scaffold.- No code under
src/pkg/chatcalls/api/inception/scaffoldor/api/inception/download.
Affected: operators using the chat-only Inception flow (#7563 "dashboard-optional operation", #9735 row "Inception via chat").
Logs Taken during the test :
Proposed solution
Chat should report what was produced and where to get it.
-
After
!inception approvesucceeds and a scaffold exists, the reply adds the file count and the download path, for example:📦 Scaffold ready: 13 files generated. ⬇️ Download: /api/inception/downloadIf no scaffold can be read, the reply stays as it is today.
-
!inception statein phasescaffoldorcompleteadds a scaffold line with the file count and the download path. -
When the phase changes to
scaffold, chat posts one line: the scaffold is ready, review it, then send!inception approve.
Alternatives considered
- Docs only.
docs/inception.md:102-103and:169-173already describe review and download. An operator in chat does not read them at that point. - List the file paths in chat. About 13 lines per call. The count and the download path are enough.
- New command such as
!inception download. Larger surface than a reply line. The operator still has to know the command exists.
Scope and compatibility
- Target branch or version:
v6only. Tested onfd020b3;src/pkg/chatunchanged at15a6de7. The default branchv5has nosrc/pkg/chat/inception.go. - Operator impact: extra lines on
!inception approve,!inception stateand one phase-change message. No new command, flag or config. - Contributor/agent impact: reply text in
src/pkg/chat.GET /api/inception/scaffolddoes not change the phase (docs/inception.md:169). - Migration or backwards-compatibility concerns:
- The first line of the approve reply is unchanged.
docs/v6-readiness-runbook.md:514still holds. - Only
inception.go:131and that runbook line contain the approve text. - The dashboard shows Sessions instead of the Inception panel when sessions are enabled (
agent-detail.js:242). Thesessions.jsfile has no reference to/api/inception/download. The message should name the API path and not a tab.
- The first line of the approve reply is unchanged.
Additional context
-
Related: 📝 v6 epic + readiness bar: dashboard-optional operation — meet humans where they are #7563, [scanner] v6 readiness live exercise: dashboard chat, inception via chat, standby S5-S6 #9735 (both closed). [runs] Host the L1 inception interview in the chat spine #8305 (issue) hosted the interview in the chat spine. PRs 🐛 fix: report defaults and plain errors when inception leaves clarify early #15753 and 🌱 chat: share the inception answer record/submit path; fix fragment grammar #15811 changed
src/pkg/chat/inception.go. -
Duplicate search on
hivecommons/hive: 11 queries, none failed, 10 s apart. No open issue matches. No closed issue proposes a scaffold or download pointer in chat. Comments on 📝 v6 epic + readiness bar: dashboard-optional operation — meet humans where they are #7563 (40) and [scanner] v6 readiness live exercise: dashboard chat, inception via chat, standby S5-S6 #9735 (32) were scanned for the same terms: no match. Queries:inception approve scaffold chatinception download archive chatinception state scaffold files chat!inception approve replyinception scaffold ready hint"Scaffold ready" inception"13 files generated"is:open inception chatis:open inception scaffold"inception approve" UXinception "download" zip chat operator
-
In the dashboard, "Download Project" appears only in phase
complete(inception.js:486-497). In phasescaffoldthe panel shows Approve and Start Over./api/inception/downloadworks in any phase (inception_handlers.go:508-565has no phase check). -
Chat transcript after approve:
!inception approve ✅ Inception approved and brainstorm re-paused. 💡 [brainstorm] Paused
Activity
[-]✨ feature: Dashboard Chat: report scaffold file count and download path on inception approve[/-][+]✨ feature[v6]: Dashboard Chat: report scaffold file count and download path on inception approve[/+]hivecommons-hive commentedon Nov 15, 2026
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label
triage/accepted(configured inissue_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.clubanderson commentedon Nov 17, 2026
Closing as obsolete. #18419 (merged 2026-11-16) retired the inception API, watcher and scaffold generator that this report exercised;
/api/inception/approveand/api/inception/scaffoldnow return "gone", and inception runs as Spek sessions. Thanks for the careful, detailed report, it was useful while the old flow existed. If the Spek session flow has a similar gap in reporting what it produced, please open a new issue against it.github-actions commentedon Nov 17, 2026
@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
/reopenand 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.