fix(cli): clarify subagent setup language

[Waishnav]

Selecting ChatGPT during setup still leads to a local agent picker because those agents are workers DevSpace can delegate to, not another place the user must run DevSpace from. The old wording made that intended flow look contradictory.\n\nClarify the destination prompt, explain the delegation step before the agent picker, and use Subagents consistently in the setup summary and docs. Fixes #333.

Summary by CodeRabbit

• Documentation

  • Clarified the distinction between where DevSpace is invoked and which agents it may use as subagents.
  • Added setup guidance explaining subagent selection and configuration storage.
  • Updated terminology throughout setup documentation for greater clarity.

• User Experience

  • Improved devspace init prompts and setup summary to clearly describe DevSpace and subagent selection.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: be85e5d3-ca0d-4869-92f8-c7b29658df9d

📥 Commits

Reviewing files that changed from the base of the PR and between 1694fbb and 142f84b.

📒 Files selected for processing (3)

• README.md
• docs/setup.md
• src/cli.ts

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The setup flow now distinguishes where DevSpace is invoked from which agents it may use as subagents. CLI prompts, setup output, the README, and setup documentation use the updated terminology.

Changes

Setup terminology

Layer / File(s)	Summary
Interactive setup prompts src/cli.ts	CLI prompts and the final setup summary distinguish DevSpace invocation locations from subagents.
Documentation clarification README.md, docs/setup.md	Documentation explains delegated work, supported subagents, and their configuration under subagents.

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

Severity of issue fixed: Medium

Merge Risk: ⚪ Minimal · up to 142f8

ChatGPT-only setup now clearly prompts users to choose delegated subagents, with consistent terminology across the CLI and documentation. No material merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (2 skipped: 2 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the primary change: clarifying subagent setup language in the CLI.
Linked Issues check	✅ Passed	The CLI continues to prompt for agent selection after the DevSpace usage selection, including when ChatGPT is selected. The updated wording and delegation message clarify this flow and address issue […
Out of Scope Changes check	✅ Passed	The README, setup documentation, and CLI prompt changes directly support the objective of clarifying DevSpace subagent setup. No unrelated changes are identified.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/onboarding-subagent-language

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit reads the prompts anew
DevSpace names each path in view
Subagents wait for delegated play
Clear words guide the setup way
Config hops neatly into place
Binky approves the cleaner interface}

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

[greptile-apps]

Greptile Summary

This change clarifies that setup destinations identify where DevSpace is invoked, while separately selected subagents are available for delegated work. The interactive setup flow, persisted selection, and focused onboarding coverage confirm the revised wording behaves as intended.

Confidence Score: 5/5

Safe to merge; no verified issues affect the changed setup flow.

The reviewed change is limited to onboarding terminology and documentation, and the exercised setup path completed with all assertions passing.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• Executed the onboarding wording-check verifier script and confirmed it passed, validating the changed prompt, delegation explanation, persisted subagent choice, and ready-summary label.
• Inspected the onboarding wording-check output and focused-test logs, confirming both reported ASSERTIONS: PASS.
• Performed a second validation run to check for defects; the check again passed with ASSERTIONS: PASS and reported no changed file/line, severity, or securityIssue.
• Uploaded and linked the artifact bundle to support review, including the script, logs, videos, and before/after visuals.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "fix(cli): clarify subagent setup languag..." | Re-trigger Greptile}