Skip to content

fix(minimal): drop the "Next steps" hint printed after init writes the mfile - #785

Merged
norrietaylor merged 1 commit into
mainfrom
fix/init-activate-scaffold-hint
Jul 16, 2026
Merged

norrietaylor merged 1 commit into
mainfrom
fix/init-activate-scaffold-hint

Conversation

@norrietaylor

@norrietaylor norrietaylor commented Jul 16, 2026 •

Copy link
Copy Markdown
Member

Closes #771. Supersedes #781 (closed — wrong root cause).

Problem

minimal activate on a project with no minimal.toml auto-scaffolds one and then printed a "Next steps" block telling the user to run minimal activate . # create a session — while activate is already running and creates the session in the same command:

Created …/minimal.toml

Next steps:
  minimal update      # pin package versions
  minimal activate .  # create a session      ← nonsensical: you just ran activate

The block lives in run_init_flow, which is shared by minimal init and activate's auto-scaffold (offer_mfile_scaffold).

(The bot-generated #781 misread this as an "inside an active session" bug and gated on MINIMAL_SESSION_ID — a channel-routing var never set in this host-side flow; the session UUID in the report was the one activate had just created. See the #781 discussion.)

Change

Just drop the "Next steps" block. init still prints the created path; the next action is clear from context (activate proceeds to create the session; a standalone init leaves the toml ready). No behavior worth keeping is lost, and there's no caller-conditional logic to maintain.

Net diff: 7-line deletion in crates/minimal/src/lib.rs.

Note: the minimal crate doesn't build on macOS (transitive Linux-only procfs), so I relied on the Linux CI lanes to compile.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Bug Fixes
    • Removed the interactive “Next steps” guidance displayed after initialization.
    • Initialization now completes with the existing success output without additional follow-up prompts.

@coderabbitai

coderabbitai Bot commented Jul 16, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

run_init_flow still writes minimal.toml and prints its creation message, but no longer prints the subsequent “Next steps” guidance.

Changes

Initialization output

Layer / File(s) Summary
Remove post-creation hints
crates/minimal/src/lib.rs
Removes the minimal update, minimal activate ., and conditional minimal attach guidance after successful file creation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

  • gominimal/inbox#285 — Directly concerns removal of stale “Next steps” output from run_init_flow.

Suggested reviewers: msample

Poem

A bunny trims the hints away,
No stale commands remain today.
The config blooms, the output’s neat,
No extra steps beneath its feet.
Hop, hop—clean initialization!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Linked Issues check ✅ Passed The change aligns with #771 by eliminating the nonsensical post-scaffold next-steps prompt in the activate path.
Out of Scope Changes check ✅ Passed No unrelated code changes are indicated beyond the next-steps output adjustment for minimal.toml scaffolding.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: removing the post-init "Next steps" hint output.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

Comment @coderabbitai help to get the list of available commands.

…e mfile

`minimal activate` on a project without a `minimal.toml` auto-scaffolds
one via `run_init_flow`, which printed a "Next steps" block suggesting
`minimal activate .  # create a session` — nonsensical there, since
`activate` is already running and creates the session in the same
command. Just drop the block; `init` still reports the created path and
the next action is clear from context.

Supersedes #781, which gated the hint on `MINIMAL_SESSION_ID` — a
channel-routing var never set in this host-side flow.

Closes: #771
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@norrietaylor
norrietaylor force-pushed the fix/init-activate-scaffold-hint branch from ba6a899 to edab516 Compare July 16, 2026 04:31
@norrietaylor norrietaylor changed the title fix(minimal): omit "activate" next-step hint when activate scaffolds the mfile fix(minimal): drop the "Next steps" hint printed after init writes the mfile Jul 16, 2026
@norrietaylor
norrietaylor merged commit ad793fc into main Jul 16, 2026
28 checks passed
@norrietaylor
norrietaylor deleted the fix/init-activate-scaffold-hint branch July 16, 2026 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

activate auto-scaffold prints a nonsensical "minimal activate ." next-step hint

2 participants