Repository navigation
fix: treat a named request as consent to force - #75
Open
AntTheLimey wants to merge 3 commits into
Open
AntTheLimey wants to merge 3 commits into
AntTheLimey wants to merge 3 commits into
Conversation
A request that names a destructive action and its target is consent to pass --force. The consent stops at that action: any further destructive step it turns out to need, such as deleting branches, still needs the user's say-so. The old rule held back --force for unattended runs only, so an agent asked to resize a database stopped at the CLI's prompt and never learned that branches blocked it.
The managed skill's description triggered only on product words, so a request such as "back up <name>" or "delete <name>" never loaded it. Agents then searched the filesystem for the name instead of asking the API. The description now covers a request that names a database only by its name.
AntTheLimey
changed the title
A benchmark rerun showed no gain: on prompts that name only the database, the skill loaded in 5 of 15 runs with the change against 7 of 15 without it. Naming the product is what loads it, so the extra 115 bytes come back out.
AntTheLimey
changed the title
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
1 participant
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.
What changed
The managed, byoc and controlplane skills now tell an agent that a
request naming the action and its target is consent to pass
--force. That consent covers the named action only. The agent asksbefore any further destructive step, such as deleting branches or a
waiver flag.
Before,
--forcewas reserved for unattended runs. An agent asked to"resize this database" stopped at the confirmation prompt and never
reached the API's refusal, so it could not tell the user that branches
were blocking the resize.
A second commit widened the managed skill's description and is
reverted here: measured, it did not make the skill load more often.
Checks
go test ./internal/clitest/ .: pass (2,509 test runs)make lint-docs: 0 errors, 0 warnings across 667 files