[notgitika]

Description

Resolve bare Windows commands against absolute PATH entries before launching them, while preserving PATHEXT and command-shim support. Explicit relative and absolute paths keep their existing behavior.

Route browser launch and Windows process cleanup through the shared process launcher. Apply the Windows lookup setting at CLI startup so child processes use consistent command lookup.

Related Issue

Not applicable.

Documentation PR

Not applicable; this changes internal process-launch behavior without changing the command interface.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

• I ran bun test — 4,709 passed, 6 Windows-only tests skipped on Linux, 0 failed
• Relevant end-to-end tests are not applicable because this change does not modify deployment or AWS interactions
• I ran bun run typecheck
• I ran bun run lint:check
• I ran bun run format:check
• I ran bun run build
• I ran bun run secrets:check
• src/assets/ was not modified

Checklist

• I have read the CONTRIBUTING document
• I added focused command-resolution tests and a Windows process-launch regression test
• No documentation changes are needed for this internal behavior change
• No new example is needed because the command interface is unchanged
• My changes generate no new warnings
• No dependent changes are required

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-1.0.0.tgz

How to install

gh release download pr-2704-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-1.0.0.tgz

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[notgitika]

CI status note:

• verify / Linux reaches the dependency-audit step and fails on the repository’s current dependency state. This branch does not modify dependency manifests, lockfiles, or audit configuration; the build and test portions of the job completed successfully.
• harness-review / review stopped because the automated reviewer reached its maximum generation limit before producing a result. It did not report a code finding.

The relevant platform validation is green: Windows, macOS, CodeQL, and the external end-to-end build all passed.