feat(cli): add interactive setup wizard and modernize init command#247
feat(cli): add interactive setup wizard and modernize init command#247cameroncooke wants to merge 2 commits intomainfrom
Conversation
Add `xcodebuildmcp setup` — an interactive terminal wizard that walks users through configuring project defaults (project/workspace, scheme, simulator, workflows, debug mode, Sentry opt-out) and persists the result to .xcodebuildmcp/config.yaml. Key changes: - New setup command with clack-based interactive prompts - Shared Prompter abstraction for testable TTY/non-interactive prompts - Promote sentryDisabled from env-var-only to first-class config key - Extract reusable functions from discover_projs, list_schemes, list_sims so both MCP tools and CLI can call them directly - Modernize init command to use clack prompts and interactive selection - Replace Cursor/Codex client targets with generic Agents Skills target - Add persistProjectConfigPatch for atomic config file updates
commit: |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Extract shared isInteractiveTTY() to prompts.ts and add try/catch to withSpinner so the spinner is stopped if the task throws, preventing garbled terminal output on error.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| .filter((workflow) => !WORKFLOW_EXCLUDES.has(workflow.id)) | ||
| .filter((workflow) => isWorkflowEnabledForRuntime(workflow, predicateContext)) | ||
| .sort((left, right) => left.id.localeCompare(right.id)); | ||
| } |
There was a problem hiding this comment.
Setup wizard uses uninitialized config store for workflows
Medium Severity
getWorkflowOptions calls getConfig() to build the predicate context for filtering visible workflows. However, the setup command exits early in cli.ts before bootstrapRuntime / initConfigStore runs, so getConfig() returns only defaults (e.g., experimentalWorkflowDiscovery: false). The existing project config loaded via loadProjectConfig earlier in the wizard is never fed into the workflow-visibility predicates. Workflows gated behind config-file settings (like experimental ones) won't appear in the setup prompt even when the user's existing config enables them.
Additional Locations (1)
1 participant
Add
xcodebuildmcp setup— an interactive terminal wizard that configures project defaults (project/workspace, scheme, simulator, workflows, debug mode, Sentry opt-out) and persists results to.xcodebuildmcp/config.yaml.Previously users had to hand-edit YAML to configure their project. The setup wizard discovers available projects, schemes, and simulators, presents them in a polished terminal UI via
@clack/prompts, and writes a complete config file with a summary of what changed.Supporting changes:
Prompterabstraction (src/cli/interactive/prompts.ts) — wraps@clack/promptswith a testable interface that auto-selects defaults in non-interactive modesentryDisabledpromoted to first-class config key — previously env-var-only (XCODEBUILDMCP_SENTRY_DISABLED), now settable inconfig.yamland resolved through the standard config layering. A newhydrateSentryDisabledEnvFromProjectConfig()bridges the config file to the env var before Sentry init in all three entrypoints (cli, daemon, mcp server)discoverProjects(),listSchemes(), andlistSimulators()functions from the MCP*Logicwrappers so both the MCP layer and CLI can call them directly. No behavior change to MCP tool responsesinitcommand modernized — switched from rawreadlineto@clack/prompts, added interactive skill type and client selection when no flags are provided, replaced Cursor/Codex targets with generic "Agents Skills" target, added~expansion for--destpersistProjectConfigPatch()— new utility for atomic config file updates with support for mutually exclusive key cleanup (projectPath vs workspacePath)