Repository navigation
Conversation
Before this change, setup created an agent space if no space had the name from --agent-space-name. With --yes, a wrong name made a new agent space without a question. Now setup stops before it changes AWS and lists the spaces in the region. To create a space, pass --new-agent-space with the name. The space list in a terminal no longer offers a space with that name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 0470ba2. Configure here.
davidbrackbill
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the behavior of
--agent-space-nameto pick only an existing agent space, not create a new space with that name.If no space in the region has the name,
setupstops. The error lists the agent spaces in the region, and tells you to add--new-agent-spaceto provision a space with that name. This applies with and without a terminal.These items also changed:
--agent-space-namedescribes the new behavior.--new-agent-space.--new-agent-space, if a space already has the name, the error tells you to remove--new-agent-spaceand runsetupagain. To pick the space by its ID, you also replace--agent-space-namewith--agent-space-id <id>.Scripts that use
--agent-space-nameto create a space on the first run must also pass--new-agent-space.To test the change, run
go test ./cmd/aws_devops_agent/.🤖 Generated with Claude Code
Note
Overview
--agent-space-namenow selects only an existing agent space; it no longer implicitly creates one when no space matches. If the name is missing in the region, setup fails (interactive or not) with a message that lists spaces and says to add--new-agent-spaceto provision with that name.The interactive space list drops the “provision a new agent space named …” shortcut; users still get a single “provision a new agent space” path that prompts for a name. Unattended errors when spaces exist but none are chosen now mention
--new-agent-space. With--new-agent-space, if the name is already taken, planning errors tell users to drop that flag to reuse the space or switch to--agent-space-id.Breaking change for automation: scripts that relied on
--agent-space-namealone to create on first run must also pass--new-agent-space.Reviewed by Cursor Bugbot for commit 0470ba2. Bugbot is set up for automated code reviews on this repo. Configure here.