If I fork a session, the context will reach over 100%

[amat27]

Short description

If I fork a session, the context will reach over 100%

What happened?

• In opencode, choose fork a session
• magic context will report 200% or 400% context usage, sometimes directly trigger a opencode compaction.

Diagnostics

Plugin version

0.21.1

OpenCode version

1.15.0

Platform

Windows 11

Client

OpenCode TUI

Log output (optional)

[ualtinok]

Yes forking is not supported currently for magic-context sessions. Supporting this requires brittle change which can take longer than the /fork command itself. When you fork a session, all the internal ids for that session, including session id, reasonably, get re-IDed. Due to this, magic-context now doesn't recognize this new session and cannot reduce the context sent to LLMs.

Could you tell me the use case for your /fork usage? We might try to support a form of forking but I want to know more first about the use cases.

[amat27]

Thanks for the explanation.
I was working on a feature branch of a large repo for a couple days. Magic context works perfectly (Sometime the model got some amnesia... but that's another topic). Then I need to experiment 2 possible designs in parallel, that's why I forked the session, since I don't know which branch to keep until I see the result.