mosaicstack/stack
1
0
Fork 0
Code Issues 13 Pull Requests Actions Packages Projects Releases 11 Wiki Activity

IUV-M03: Install UX v2 — provider-first intelligent flow + drill-down main menu #438

New Issue
Closed
opened 2026-04-05 21:23:16 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-04-05 21:23:16 +00:00
Owner
Copy Link

Mission: install-ux-v2-20260405
Milestone: IUV-M03 (provider-first intelligent flow)
Tier: opus
Depends on: IUV-M02
Target release: mosaic-v0.0.27

The current wizard is a linear interrogation. User feedback: Quick Start asks far too many questions to be meaningfully "quick", there's no drill-down navigation, and provider setup happens late without any intelligence.

Scope

1. Drill-down main menu

Replace the linear flow with a top-level menu:

  • Plugins — Recommended / Custom
  • Providers — list, add, configure
  • (Other top-level groups as needed; design doc defines the final shape)

2. Real Quick Start

Define a minimum curated question set and delete everything else from the fast path. Target: under 90 seconds for a returning user. Document the exact baseline in the design doc.

3. Provider-first natural-language intake

OpenClaw-style flow:

  1. User describes what they want in natural language
  2. Agent expounds on the intent (confirms understanding)
  3. Agent proposes its own name based on the intent
  4. User confirms / overrides

Naming should persist to ~/.config/mosaic/agent.json (or similar — worker decides) so all future mosaic invocations use it.

4. Offline fallback

LLM call assumes a provider is available. Chicken-and-egg: provider setup is what we're configuring. Design doc must resolve one of:

  • (a) Require a provider key before intake
  • (b) Bundle a deterministic "advisor" for common intents
  • (c) Skip intake in offline mode and fall through to defaults

5. Backward compatibility

  • MOSAIC_ASSUME_YES=1 + env-var headless path must still complete end-to-end
  • tools/install.sh --yes must still complete without a TTY

Acceptance

  • Design doc in scratchpad (state machine, menu shape, Quick Start baseline, intent intake, offline fallback, naming persistence)
  • Drill-down main menu implemented
  • Quick Start path trimmed to curated minimum
  • Provider-first intent intake with agent self-naming implemented
  • Offline fallback works (deterministic default name + path)
  • Headless path regression tests pass
  • PR merged, CI green, this issue closed
  • Tag mosaic-v0.0.27 pushed + Gitea release published
**Mission:** install-ux-v2-20260405 **Milestone:** IUV-M03 (provider-first intelligent flow) **Tier:** opus **Depends on:** IUV-M02 **Target release:** `mosaic-v0.0.27` The current wizard is a linear interrogation. User feedback: Quick Start asks far too many questions to be meaningfully "quick", there's no drill-down navigation, and provider setup happens late without any intelligence. ## Scope ### 1. Drill-down main menu Replace the linear flow with a top-level menu: - **Plugins** — Recommended / Custom - **Providers** — list, add, configure - (Other top-level groups as needed; design doc defines the final shape) ### 2. Real Quick Start Define a minimum curated question set and delete everything else from the fast path. Target: under 90 seconds for a returning user. Document the exact baseline in the design doc. ### 3. Provider-first natural-language intake OpenClaw-style flow: 1. User describes what they want in natural language 2. Agent expounds on the intent (confirms understanding) 3. Agent proposes its own name based on the intent 4. User confirms / overrides Naming should persist to `~/.config/mosaic/agent.json` (or similar — worker decides) so all future `mosaic` invocations use it. ### 4. Offline fallback LLM call assumes a provider is available. Chicken-and-egg: provider setup is what we're configuring. Design doc must resolve one of: - (a) Require a provider key before intake - (b) Bundle a deterministic "advisor" for common intents - (c) Skip intake in offline mode and fall through to defaults ### 5. Backward compatibility - `MOSAIC_ASSUME_YES=1` + env-var headless path must still complete end-to-end - `tools/install.sh --yes` must still complete without a TTY ## Acceptance - [ ] Design doc in scratchpad (state machine, menu shape, Quick Start baseline, intent intake, offline fallback, naming persistence) - [ ] Drill-down main menu implemented - [ ] Quick Start path trimmed to curated minimum - [ ] Provider-first intent intake with agent self-naming implemented - [ ] Offline fallback works (deterministic default name + path) - [ ] Headless path regression tests pass - [ ] PR merged, CI green, this issue closed - [ ] Tag `mosaic-v0.0.27` pushed + Gitea release published
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#438
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?