Session-Scoped Tool Permission Caching (Autonomous Execution Flow)

Overview

In autonomous agent environments (Antigravity IDE, Claude Code, Cursor, MCP Servers), asking the user for interactive permission on every basic action ("Allow agent to read src/utils.ts?", "Allow agent to run git status?") causes catastrophic workflow degradation.

Per-action confirmation prompts cause:

1. Long Idle Stalls: The agent freezes mid-task for 30 minutes while waiting for the human to click "Approve".
2. Permission Retry Loops: Models get confused when a command is rejected or timed out, generating apologetic retry loops that burn tokens.
3. Context Transcript Pollution: Permission metadata and grant/deny logs inflate the conversation context.

The Session-Scoped Permission Caching Protocol establishes a 3-Tier Risk Hierarchy and persists granted permissions across the entire workspace session.

Interactive Per-Action Approval vs. Session-Scoped Caching