[FEATURE] Don't block Edit tool for files read in session it was forked from

Resolved 💬 1 comment Opened May 18, 2026 by poof86 Closed Jun 17, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When using --fork-session the Read calls history on the files, doesn't seem to be transferred. So when Claude tries to Edit a file it already read in the session it was forked from, it gets blocked. Claude then needs to re-read lines it already has in context, which is a waste of time and tokens.

Proposed Solution

Have Read() call history be part of the forked data too, so there are no unnecessary re-reads needed to edit files already in context.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

File operations

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗