dev --logs on harness-only project exits 0 instead of failing

Open Beginner friendly
#1,406 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start with the agentcore dev command handling for --logs on harness-only projects and reproduce the documented command sequence with --skip-deploy. Make the command return exit code 1 with a clear validation error directing users to agentcore invoke --harness, then verify both the message and exit status.

Written by the indexing model from the issue text.

Description

bug

agentcore dev --logs on a harness-only project prints guidance text and exits 0. It should exit 1 with a
validation error since no dev server can be started, harness projects don't support local dev.

Reproduction:

 agentcore create --name MyHarness
 cd MyHarness
 agentcore dev --logs --skip-deploy
 # Prints "Harness dev runs against the deployed service..." and exits 0

Expected: Exit code 1 with a clear error (e.g. "Harness projects do not support local dev. Use agentcore
invoke --harness instead.")

Actual: Exit code 0 with informational text.

Dominant language
TypeScript
Stars
291
Forks
96
Avg merge
1d 1h
Merged PRs (30d)
192

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/agentcore-cli

All issues in aws/agentcore-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.