Skip to content

docs: clarify permission context for raw input #2138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kocaemre wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

docs: clarify permission context for raw input #2138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/protocol/v1/tool-calls.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ The Client responds with the user's decision:
}
```

Clients **MAY** automatically allow or reject permission requests according to the user settings.
Clients **MAY** automatically allow or reject permission requests according to the user settings. When making a permission decision, Clients **SHOULD** treat the supplied `toolCall` details as the context being approved, not just the tool identity. If a permission policy or UI depends on `rawInput` and that field is absent or unavailable, the Client should avoid presenting the request as if argument details were known; it should either show that the arguments are unavailable or apply a stricter policy such as requiring explicit user confirmation.

If the current prompt turn gets [cancelled](/protocol/v1/prompt-turn#cancellation), the Client **MUST** respond with the `"cancelled"` outcome:

Expand Down