Compare commits

...

2 Commits

Author SHA1 Message Date
Claude
a7c291aca7 Show input_preview only for Bash permission prompts
Bash commands are the security decision — the user needs to see the
actual command. Other tools (Write, Edit, etc.) have bulky payloads
that flood a phone screen; the description line is enough.
2026-03-24 06:01:58 +00:00
Claude
d369b8cb8b Drop input_preview from iMessage permission prompt
Brings the prompt closer to the compact format telegram/discord use.
The description field already summarizes what the tool will do; the
raw input dump made the text wall-of-texty on a phone screen.
2026-03-24 06:01:13 +00:00

View File

@@ -536,11 +536,12 @@ mcp.setNotificationHandler(
async ({ params }) => {
const { request_id, tool_name, description, input_preview } = params
const access = loadAccess()
const preview = tool_name === 'Bash' ? `\n${input_preview}` : ''
const text =
`🔐 Permission request [${request_id}]\n` +
`${tool_name}: ${description}\n` +
`${input_preview}\n\n` +
`Reply "yes ${request_id}" to allow or "no ${request_id}" to deny.`
`${tool_name}: ${description}` +
preview +
`\n\nReply "yes ${request_id}" to allow or "no ${request_id}" to deny.`
// allowFrom holds handle IDs, not chat GUIDs — resolve via qChatsForHandle.
// Include SELF addresses so the owner's self-chat gets the prompt even
// when allowFrom is empty (default config).