[GH-ISSUE #399] Agent integration capability selection is unclear and can silently drop the bundled skill #245

Closed
opened 2026-10-15 18:22:56 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Jul 21, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/399

Problem

The "Agent integration (MCP + guided workflow)" capability bundles MCP client configuration and the REA reverse-engineering skill. However, the UI flow for selecting which agents to configure is unclear, and selecting the capability without selecting any agents can silently omit the skill installation.

Observed behavior

  1. The capability label says "MCP + guided workflow" but the second prompt "Which agents should use REA?" appears only after the capability is selected, with no explanation that the skill install depends on selecting agents.
  2. In selectSetupActions (src/cliSetup.ts, lines 150-166), when agentIntegrationCapabilityId is selected but no clients are selected (selectedClients.length === 0), the function returns selectedActionIds without including bundledSkillAction. So a user who selects "Agent integration" but toggles off every detected agent gets neither client configs nor the guided-workflow skill.
  3. The agent option hints show implementation details (create · /Users/.../.codex/config.toml) rather than something helpful about what each agent is.

Expected behavior

  • If "Agent integration" is selected, the skill should always be included, because the guided workflow is part of the bundle. The only exception should be an explicit opt-out such as --skill=false.
  • The agent picker should make clear that at least one agent must be selected for the integration to be useful, or default to selecting all detected agents.
  • The agent option hints should describe the agent, not the file operation.

Suggested changes

  • Always include bundledSkillAction when agentIntegrationCapabilityId is selected, regardless of client selection, unless the user explicitly disabled the skill.
  • Pre-select detected agents by default and consider using required: true on the agent multiselect when agent integration is chosen.
  • Improve option labels/hints in selectClients to explain what each agent is.
  • Consider whether the second prompt is needed at all: if only one agent is detected, a single confirm ("Set up REA for Codex?") would be clearer than an empty multiselect.
  • Update tests/cliSetup.test.ts to cover the skill-retention behavior.
  • src/cliSetup.ts lines 125-167, 233-251
  • docs/installation.md lines 53-63
  • tests/cliSetup.test.ts lines 126-180
Originally created by @morluto on GitHub (Jul 21, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/399 ## Problem The **"Agent integration (MCP + guided workflow)"** capability bundles MCP client configuration and the REA reverse-engineering skill. However, the UI flow for selecting which agents to configure is unclear, and selecting the capability without selecting any agents can silently omit the skill installation. ## Observed behavior 1. The capability label says **"MCP + guided workflow"** but the second prompt **"Which agents should use REA?"** appears only after the capability is selected, with no explanation that the skill install depends on selecting agents. 2. In `selectSetupActions` (`src/cliSetup.ts`, lines 150-166), when `agentIntegrationCapabilityId` is selected but no clients are selected (`selectedClients.length === 0`), the function returns `selectedActionIds` without including `bundledSkillAction`. So a user who selects "Agent integration" but toggles off every detected agent gets neither client configs nor the guided-workflow skill. 3. The agent option hints show implementation details (`create · /Users/.../.codex/config.toml`) rather than something helpful about what each agent is. ## Expected behavior - If **"Agent integration"** is selected, the skill should always be included, because the guided workflow is part of the bundle. The only exception should be an explicit opt-out such as `--skill=false`. - The agent picker should make clear that at least one agent must be selected for the integration to be useful, or default to selecting all detected agents. - The agent option hints should describe the agent, not the file operation. ## Suggested changes - Always include `bundledSkillAction` when `agentIntegrationCapabilityId` is selected, regardless of client selection, unless the user explicitly disabled the skill. - Pre-select detected agents by default and consider using `required: true` on the agent multiselect when agent integration is chosen. - Improve option labels/hints in `selectClients` to explain what each agent is. - Consider whether the second prompt is needed at all: if only one agent is detected, a single confirm ("Set up REA for Codex?") would be clearer than an empty multiselect. - Update `tests/cliSetup.test.ts` to cover the skill-retention behavior. ## Related code - `src/cliSetup.ts` lines 125-167, 233-251 - `docs/installation.md` lines 53-63 - `tests/cliSetup.test.ts` lines 126-180
bsakaguchi 2026-10-15 18:22:56 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#245
No description provided.