Original Reddit post

So I googled “claude code auto compact” because I was losing my shit over it, and the first thing that shows up is this top 1% commenter saying never compact at any context size, that it’s a guessing game, and that the cleanest solution is to just start a new session with a standardised handoff document and session handshake protocols. And I’m sitting here going ok but is this actually how top vibe coders do it? Because like, the guy’s got the badge and the rep, but I need to know if that’s actually what works in practice and how do you guys get into deep multi-hour agentic run while can’t afford to stop and write a handoff doc every time the context gets heavy. So I’m coming in with Codex where auto-compact at 275k just happens and you don’t even think about it, and trying to translate that to Claude Code where it feels like that safety net just isn’t there. Now with Haiku 5.5 I feel like there’s a real play to build plans with Opus and hand off execution to Haiku, but I have no idea how people are actually structuring that without the smaller model losing the plot halfway through. So if you’re running long agentic sessions on Claude Code, how are you handling context? Are you doing the handoff doc thing and actually making it work, are you breaking sessions manually, letting it compact and eating the hit, or something completely different? And if anyone’s doing the Opus to Haiku pipeline already, how do you calibrate the switch so it doesn’t go sideways? I want the real stuff. What’s actually working for you, need that juicy advice. Help a noobie out here. submitted by /u/One-Luck7149

Originally posted by u/One-Luck7149 on r/ClaudeCode