Live data from Hacker News

Show HN: Ctx – a /resume that works across Claude Code and Codex

github.com

21–30 of 32 posts

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#21

I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.

I'd use it if I hit the 5 hour quota mid-change and then came back later in the day in a new terminal (depending on the input/output ratio of my now un-cached context, of course).

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#22

I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.

I have like 15 concurrent sessions I leave up for weeks, 50% Codex 50% Claude Code, even though I know they work better with fresh context. Then again I also always have least 200 browser tabs up. I probably just have a mental illness.

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#23

I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.

I spin up a lot of agents and don't always get back to them same day, so it helps a lot if my laptop restarts to install updates automatically.

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#24
Claude Code used to have a warning that toggling thinking within a conversation would decrease performance:

> Changing thinking mode mid-conversation will increase latency and may reduce quality. For best results, set this at the start of a session.

Neither OpenAI nor Anthropic exposes raw thinking tokens anymore.

Claude Code redacts thinking by default (you can opt in to get Haiku-produced summaries at best), and OpenAI returns encrypted reasoning items.

Either way, first-party CLIs hold opaque thinking blobs that can't be manipulated or ported between providers without dropping them. So cross-agent resume carries an inherent performance penalty: you keep the (visible) transcript but lose the reasoning.

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#25

I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.

I have like 15 concurrent sessions I leave up for weeks, 50% Codex 50% Claude Code, even though I know they work better with fresh context. Then again I also always have least 200 browser tabs up. I probably just have a mental illness.

lol after reading your first sentence I literally thought to myself "this sounds like the type of person who never closes their browser tabs"

Re: Show HN: Ctx – a /resume that works across Claude Code and Codex

#30

I don't think I've ever /resumed a Claude Code session even once. What do people use that for? The way I use it is to make a change, maybe document the change, and then I'm done. New session.

Most of the time it's when I want to go back and have a skill made for future reuse, but with remote control I've had some sessions open for remote diagnostics and it just works better than starting from scratch - even having lessons learned to create memories and update Claude.md.

I know it's wasteful but often I've got a surplus of tokens and not enough of my time - so it's a trade off I've been fine with.

Post reply on HN