Reopening: "Continue" leads to massive context carry-over into new 5h limit, thus when implementation stops half-way and you are asked to wait, the next session quota is reduced massively.

Hey all, we have root caused and fixed this. Detailed technical post-mortem here: https://www.anthropic.com/engineering/april-23-postmortem. If you see any more issues/weirdness, please don't hesitate to run /feedback + open an issue. Not entirely convinced that the issue is completely resolved. Version: v2.1.119 From what it looks like there is still a big carry-over of history into the session on a 'continue' : Initial very rapid increase to about 39% usage, then subsequently settling down (increase to action ratio diminished massively). I can share you the logs in confidential matter which the actual work efforts being produced, and even it being Opus 4.7 (low setting) this is just a massive jump for essentially moving But came down to this: ``bash continue ● source .venv/bin/activate.fish; python -c "import jsonschema, referencing; print…) Read 1 file (ctrl+o to expand) ● source .venv/bin/activate.fish; python -c "from jsonschema import Draft202012Val…) ⎿  OK both available Searched for 2 patterns, read 1 file (ctrl+o to expand) ● Good — Feature.is_core_feature exists. Now let me look at yaml_load to find where validation is invoked, then build the Python validator. First, let me check yaml_utils.py: Read 1 file (ctrl+o to expand) ● Now I have what I need. Implementing #36. Replacing ys subprocess with Python jsonschema + a URI retriever that handles core://, semantics://, and relative refs: Read 1 file (ctrl+o to expand) ● Now replace the ys subprocess body with Python jsonschema+referencing: ● Update (..........) ⎿  Added 104 lines, removed 29 lines ● Now check if _resolve_ys_executable, _summarize_output, the shutil and SubprocessExecutor imports are still used. If not, Searched for 1 pattern, read 1 file (ctrl+o to expand) ⎿  Found 1 new diagnostic issue in 1 file (ctrl+o to expand) ● Update ⎿  Added 16 lines, removed 17 lines ● Now make X FATAL, and split core vs non-core feature failure: ● Update() ⎿  Added 16 lines, removed 17 lines ● Update( ⎿  Added 11 lines Then some docker restart with very conservative greps/ tails … +12 lines (ctrl+o to expand) … +16 lines (ctrl+o to expand) ....+ 11 lines │ … +62 lines (ctrl+o to expand) … +14 lines (ctrl+o to expand) + a grep returning 4 lines + another bash command to restart the container with sleep,wait, tail-3 very selective sed | grep. `` And all for about : When I noticed and checked, slightly less than 40% <img width="1646" height="393" alt="Image" src="https://github.com/user-attachments/assets/46d14d13-0460-476e-9a2c-a155df81ec03" /> This basically makes a plus plan useless afaic. there is no point with the 5h window to even try a $20 plan, because there is just no point in waiting only to get screwed over again on the next session.

_Originally posted by @milankubin in #44197_