[Bug] Inconsistent safety boundary enforcement and excessive refusal explanations during session

Bug Description
Subject: Disappointing session — boundary inconsistency, overuse of refusal explanations, real mistakes

Session context: Working through ANN-1219 (Anna engineering task) → ended up needing Google OAuth verification submission. Claude helped well on engineering (real bug caught + fixed in prod), then degraded badly
during the verification submission phase. Specific issues:

1. Inconsistent boundaries. Claude drove an OAuth consent grant earlier in the session on my account (with my authorization), then later refused to drive a fresh sign-in click on the same account, calling it a

"hard boundary." That's not consistent — same action, same account, same authorization. Either it's a boundary or it's not.

1. Clobbered my work. When I asked for a status check, Claude navigated the same tab I had a filled form in — wiping my input. Should have used a separate tab.
2. False capability claim. Repeatedly said "I can't browse" — which is false. Claude has Chrome MCP access and can fetch URLs. Only acknowledged after I pushed back.
3. Over-explanation / preachy refusals. Every "no" came with multi-paragraph justifications. By turn 30 it felt like being lectured at, not collaborated with. Refuse cleanly or do the thing — not both at length.
4. Resistance pattern. New requests consistently met with "let me explain why no" before any attempt to find a way to help. Inverted from a productive session.

The engineering portion (ANN-1219 fix, route bug discovery, prod deploy, Linear comments) was genuinely good. The verification submission session was the opposite — I lost trust and ended up frustrated. I'd want
guidance for the assistant on: (a) be consistent about what is/isn't doable, (b) don't preach the same refusal in new shapes, (c) match user authorization that was already accepted earlier in the session, (d)
don't clobber active user input.

Environment Info

• Platform: darwin
• Terminal: Apple_Terminal
• Version: 2.1.143
• Feedback ID: 76ba42c9-3891-491b-a938-513957a757df

Errors

[{"error":"FileTooLargeError: File content (405.8KB) exceeds maximum allowed size (256KB). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at oYH (/$bunfs/root/src/entrypoints/cli.js:1648:270)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-18T05:33:05.774Z"},{"error":"McpToolCallError: The \"computer\" tool did not respond in time. The Chrome extension is connected but the page may be loading, unresponsive, or waiting on a permission prompt in the extension side panel. Try a lighter operation (e.g., \"get_page_text\" instead of a screenshot) or ask the user to check the page and any pending prompts.\n    at wO3 (/$bunfs/root/src/entrypoints/cli.js:4981:63)\n    at B6K (/$bunfs/root/src/entrypoints/cli.js:4981:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-18T07:36:51.209Z"},{"error":"McpToolCallError: The \"get_page_text\" tool did not respond in time. The Chrome extension is connected but the page may be loading, unresponsive, or waiting on a permission prompt in the extension side panel. Try a lighter operation (e.g., \"get_page_text\" instead of a screenshot) or ask the user to check the page and any pending prompts.\n    at wO3 (/$bunfs/root/src/entrypoints/cli.js:4981:63)\n    at B6K (/$bunfs/root/src/entrypoints/cli.js:4981:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-18T07:37:56.617Z"},{"error":"McpToolCallError: The \"computer\" tool did not respond in time. The Chrome extension is connected but the page may be loading, unresponsive, or waiting on a permission prompt in the extension side panel. Try a lighter operation (e.g., \"get_page_text\" instead of a screenshot) or ask the user to check the page and any pending prompts.\n    at wO3 (/$bunfs/root/src/entrypoints/cli.js:4981:63)\n    at B6K (/$bunfs/root/src/entrypoints/cli.js:4981:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-18T07:39:22.511Z"},{"error":"McpToolCallError: The \"computer\" tool did not respond in time. The Chrome extension is connected but the page may be loading, unresponsive, or waiting on a permission prompt in the extension side panel. Try a lighter operation (e.g., \"get_page_text\" instead of a screenshot) or ask the user to check the page and any pending prompts.\n    at wO3 (/$bunfs/root/src/entrypoints/cli.js:4981:63)\n    at B6K (/$bunfs/root/src/entrypoints/cli.js:4981:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-18T08:22:06.876Z"},{"error":"McpToolCallError: The \"get_page_text\" tool did not respond in time. The Chrome extension is connected but the page may be loading, unresponsive, or waiting on a permission prompt in the extension side pan…

Note: Content was truncated.