Skip to content

UX-11: Quick Setup Wizard (Phase 2)#138

Merged
Gambitnl merged 1 commit intomainfrom
ux-11-setup-wizard-phase-2
Nov 24, 2025
Merged

UX-11: Quick Setup Wizard (Phase 2)#138
Gambitnl merged 1 commit intomainfrom
ux-11-setup-wizard-phase-2

Conversation

@google-labs-jules
Copy link
Copy Markdown
Contributor

Implemented Phase 2 of the Quick Setup Wizard (UX-11).

  • Multi-step Wizard: Guides new users through AI backend selection (OpenAI, Groq, Ollama), model configuration, and connectivity testing.
  • Persistence: Automatically saves API keys and configuration settings using existing ConfigManager.
  • UI Enhancements: Added a visual stepper to track progress.
  • Compatibility: Ensures the wizard returns the expected components for app.py integration.

PR created automatically by Jules for task 6072121347826826537 started by @Gambitnl

- Replaced basic setup wizard with multi-step flow:
  1. AI Backend Selection (OpenAI, Groq, Ollama)
  2. Model Configuration (Whisper, LLM, Diarization)
  3. Campaign Creation & Connectivity Test
- Added visual stepper component via `src/ui/theme.py` CSS.
- Integrated with `ConfigManager` and `save_api_keys` for persistence.
- Maintained compatibility with `app.py` wiring.
@google-labs-jules
Copy link
Copy Markdown
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!


For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more at jules.google/docs.

@Gambitnl Gambitnl marked this pull request as ready for review November 24, 2025 20:18
@Gambitnl Gambitnl merged commit d2576cf into main Nov 24, 2025
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/ui/setup_wizard.py
Comment on lines +246 to +250
if groq: keys_to_save["GROQ_API_KEY"] = groq
if hf: keys_to_save["HUGGING_FACE_API_KEY"] = hf

if keys_to_save:
save_api_keys(**{k.lower(): v for k, v in keys_to_save.items()})
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Saving OpenAI key blocks wizard progress

Providing an OpenAI API key in Step 1 causes _save_step1_and_advance to call save_api_keys with an openai_api_key argument, but save_api_keys only accepts Groq and Hugging Face parameters (src/ui/api_key_manager.py:25-29). The call raises a TypeError, so the handler returns an error status instead of advancing to Step 2, effectively preventing the default “OpenAI (Recommended)” path from working whenever a key is entered.

Useful? React with 👍 / 👎.

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.

1 participant