fix: correct harness path and next steps in create summary#1099
fix: correct harness path and next steps in create summary#1099
Conversation
…mmary Two bugs in the create flow completion screen: 1. The "Created:" tree showed harness path as harness/<name>/ but harnesses are actually created under app/<name>/. Fixed in both buildExitMessage (CLI output) and CreatedSummary (TUI component). 2. The non-interactive (CLI) completion screen showed "Next: Run agentcore deploy" without telling the user to cd into the project directory first, causing "No agentcore project found" errors. Replaced with explicit "cd <project>" + "agentcore" instructions, matching the buildExitMessage output.
|
Reviewed the changes — LGTM. The → display fix is consistent with where harnesses are actually created (verified in One very minor nit (non-blocking): |
Remove unnecessary Box nesting from the cd instructions. Both interactive and non-interactive paths now share the success message.
Coverage Report
|
Summary
Two bugs in the create flow completion screen for harnesses:
Wrong path in "Created:" tree: Showed
harness/<name>/but harnesses are created underapp/<name>/. Fixed in bothbuildExitMessage(CLI text output) andCreatedSummary(TUI component).Missing
cdinstruction: The non-interactive (CLI) completion showed "Next: Runagentcore deploy" without telling the user tocdinto the project first, causing "No agentcore project found" when they follow the instruction. Replaced with explicitcd <project>+agentcoreinstructions, matching thebuildExitMessageformat.Changes
src/cli/tui/screens/create/CreateScreen.tsx— 1 file, +19/-41 linesharness/→app/in bothbuildExitMessageandCreatedSummaryNextStepscomponent in the non-interactive branch withcd+agentcoreinstructionsNextSteps/NextStepimports,getCreateNextStepsfunction, andpath.joinimportTest plan
npm run typecheckpassesnpx eslinton changed file passes (0 errors, 0 warnings)agentcore create, pick harness, verify "Created:" showsapp/<name>/and completion sayscd <project>thenagentcore