Repository navigation
docs(kit): a new CLI's README says that over MCP ask does not ask - #191
Merged
Merged
Conversation
NEED-2731 B keeps ask as the default for the api group's deletes. Over MCP nobody answers it, so the agent runs them. A CLI with an api group now says so beside the MCP setup, says each write is kept in runs list, and gives the two commands that stop it for a profile: config set permissions.api readonly, or permissions.api.<operation> deny. Both were run on a CLI made with new --spec openapi. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
The owner ruled NEED-2731 B:
askstays the default for the api group's deletes. Over MCP nobody is there to answer it, so it runs (cli-core'sserviceApiPermissionssays so in its own comment). A user who connects the CLI to an agent should read that where they set it up.What
cliReadmeinkit/src/new.ts: a CLI with an api group gets one paragraph under "Use it with your agent". The agent runs the API's writes and deletes without asking, each one is kept inruns list, andconfig set permissions.api readonlyorconfig set permissions.api.<operation> denystops it for a profile. A CLI without an api group gets nothing, sincepermissions.apinames no command there.kit/test/preset.test.tsfor both cases.changes/docs-mcp-ask-runs.md.Testing
new --preset generic --spec openapi, in a throwaway HOME with the keyring cut off: afterpermissions.api readonly,api comments-delete --dry-runandapi comments-create --dry-runare refused andcomments-liststill reads. Afterpermissions.api.comments-delete deny, only the delete is refused.pnpm vitest run kit,pnpm lint,tsc -p kit,pnpm docs:check: passed.🤖 Generated with Claude Code