Activity

1. coderabbitai commented on Apr 15, 2026

   

   coderabbitaiBot

   on Apr 15, 2026 – with coderabbitai

   More actions

   🔗 Related PRs

   #48 - feat: interactive setup wizard with file mode onboarding [merged]
   #49 - Add first-run detection and install-time setup wizard [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
2. jonathanpopham commented on Apr 15, 2026

   

   jonathanpopham

   on Apr 15, 2026

   ContributorAuthor

   More actions

   Trace results — corrected diagnosis

   Traced the install/run path. The original hypothesis (wizard short-circuits when env key present) is wrong. The actual cause is more fundamental:

   The setup wizard is never auto-invoked on first run. It's only available as an explicit supermodel setup command.

   Code path

   cmd/root.go:45-60 (PersistentPreRunE):

   cfg, err := config.Load()
   // ...
   if cfg.APIKey == "" {
       fmt.Fprintln(os.Stderr, "Run 'supermodel setup' to get started.")
       os.Exit(1)
   }
   return nil

   internal/config/config.go:112:

   if key := os.Getenv("SUPERMODEL_API_KEY"); key != "" {
       c.APIKey = key
   }

   So when a user has SUPERMODEL_API_KEY already set in their environment:

   1. config.Load() populates cfg.APIKey from env
   2. The empty-key guard passes silently
   3. RunE falls straight through to shards.Watch(...) — no wizard, no gitignore prompt, no hook prompt, no shard-mode prompt, no awareness any of those steps exist

   What Elm actually saw

   Not "wizard scrolled past too fast" — the wizard never ran at all. He went directly into watch mode on first invocation.

   What the wizard does cover

   Reviewed internal/setup/wizard.go — the wizard itself handles auth, repo detection, agent hook install, and shard mode toggle correctly. It does NOT have a separate .graph.* ignore prompt though — gitignore is added automatically inside the shard-mode flow (line 148-150). That's worth noting in case the customer expected a prompt that was never going to appear regardless.

   Suggested fix direction (revised)

   • Detect first-run-without-setup state and auto-prompt. E.g. check for a marker (config file existence, ~/.supermodel/.setup-complete, etc.) and run the wizard the first time supermodel is invoked, even when env key is present.
   • OR print a one-liner on every run-without-config that says "run `supermodel setup` to enable agent hook + gitignore" — at least surfaces the option.
   • Decide intentionally: should env-key-only users get a fully-silent install (current behavior, friendly to CI/automation) or a one-time interactive nudge (better for new humans like Elm)?
3. drQedwards commented on Apr 20, 2026

   

   drQedwards

   on Apr 20, 2026

   Contributor

   More actions

   I would just be careful where the wizard isn’t constantly reintroducing the intro windows like what is happening over on the beta with the Remix IDE when introducing the windows for using MCP tools.

   A one time interactive nudge is recommended over a silent install regardless, a window suggesting “start the setup wizard? Recommended for first time install.” With options Yes / Skip.

   No need for the app or the server or anything to do so it is a great choice.