Interaction of Session-Scoped Permissions with Cross-Session State

Ascertain how session-scoped permissions should interact with any cross-session durable state substrate without reintroducing implicit restoration of permissions on resume or fork.

Background

Claude Code deliberately avoids restoring session-scoped permissions on resume or fork to maintain safety. Introducing a durable, cross-session state layer raises the question of how permission state should be represented or excluded to avoid undermining this safety invariant.

Resolving this issue is critical for balancing productivity (reduced friction across sessions) with safety (ensuring trust decisions remain current and explicit).

References

How session-scoped permissions interact with such a substrate, without reintroducing the resume-restoration concern that \Cref{sec:persist} closes as a deliberate safety choice, is a further open question.

— Dive into Claude Code: The Design Space of Today's and Future AI Agent Systems  (2604.14228 - Liu et al., 14 Apr 2026) in Section 12.2 (Persistence: Memory and Longitudinal Colleague Relationships)