feat(init): onboard subagents across MCP and local harnesses - #215
feat(init): onboard subagents across MCP and local harnesses#215Waishnav wants to merge 3 commits into
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
41b5c7e to
b0b640b
Compare
Greptile SummaryThe PR expands
Confidence Score: 5/5The PR appears safe to merge with no concrete blocking or independently actionable non-blocking defects identified. The new onboarding choices map consistently to existing configuration semantics, preserve provider-specific settings, and retain MCP skill discovery through the bundled-skill fallback.
|
| Filename | Overview |
|---|---|
| src/cli.ts | Extends initialization with remote-host, local-harness, subagent, and provider onboarding while conditionally presenting credentials and next steps. |
| src/onboarding.ts | Adds a focused helper that updates provider enabled states without discarding existing model and effort settings. |
| src/user-config.ts | Removes automatic installation of the bundled delegation skill and obsolete boolean subagent resolution helpers. |
| src/onboarding.test.ts | Covers provider selection, preservation of provider-specific settings, disabling subagents, and the printed installation command. |
| skills/subagent-delegation/SKILL.md | Documents the targets command as the catalog-discovery path for directly installed local-harness skills. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[devspace init] --> B{Remote MCP host?}
B -->|Yes| C[Collect public HTTPS base URL]
B -->|No| D[Store no public base URL]
C --> E{Enable subagents?}
D --> E
E -->|Yes| F[Detect and select providers]
E -->|No| G[Persist subagents disabled]
F --> H[Persist provider configuration]
H --> I{Local coding harness?}
I -->|Yes| J[Print Skills CLI install command]
I -->|No| K[Use bundled skill through MCP]
J --> L[Complete setup]
K --> L
G --> L
Reviews (1): Last reviewed commit: 41b5c7e | Re-trigger Greptile
b0b640b to
0e6e211
Compare
0e6e211 to
b058a3d
Compare
b058a3d to
edffb73
Compare
edffb73 to
2732acf
Compare
Setup previously assumed every user needed a public MCP URL and copied a bundled skill into DevSpace state. This layer separates remote MCP access from local-harness use, allows a local-only configuration without a tunnel, detects providers, and persists the selected provider objects while preserving existing defaults.
For local harnesses, setup prints npx skills add Waishnav/devspace --skill subagent-delegation --global and leaves harness discovery and installation to the Skills CLI. DevSpace does not execute that command or write into Codex, Claude Code, OpenCode, Pi, or other harness skill directories. Remote MCP hosts continue receiving the bundled skill through workspace context.
This is layer 4 of 4, based on #214. The local-only TTY flow was exercised with isolated config and state directories, and the stack also passes the full test suite, TypeScript typecheck, and packaged build.