Live data from Hacker News

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

github.com

11–20 of 32 posts

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

#11

Tooling like this is why I really want to build my own harness that can replace Claude Code, because I have been building a few different custom tools that would be nice as part of one single harness so I don't have to tweak configurations across all my different environments, projects and even OS' it gets tiresome, and Claude even has separate "memories" on different devices, making the experience even more inconsis…

Pi is very extensible, and could possibly serve as a good foundation to build on.

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

#12
post #8
post #3

Have you considered making it possible to share a stream/context? As an export/import function.

I wrote a tool for myself to copy (and archive) the claude/codex conversations github.com/rkuska/carn

Thanks

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

#13

Tooling like this is why I really want to build my own harness that can replace Claude Code, because I have been building a few different custom tools that would be nice as part of one single harness so I don't have to tweak configurations across all my different environments, projects and even OS' it gets tiresome, and Claude even has separate "memories" on different devices, making the experience even more inconsis…

Pi is very extensible, and could possibly serve as a good foundation to build on.

Is it Pi LLM you're referring to? I've heard "Pi" referenced twice now, and now I'm curious, I do have unused Pis, though not Raspberry Pi 5s...

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

#14

Earlier quoted context omitted.

Pi is very extensible, and could possibly serve as a good foundation to build on.

Is it Pi LLM you're referring to? I've heard "Pi" referenced twice now, and now I'm curious, I do have unused Pis, though not Raspberry Pi 5s...

https://github.com/badlogic/pi-mono/tree/main/packages/codin...

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

#15

Tooling like this is why I really want to build my own harness that can replace Claude Code, because I have been building a few different custom tools that would be nice as part of one single harness so I don't have to tweak configurations across all my different environments, projects and even OS' it gets tiresome, and Claude even has separate "memories" on different devices, making the experience even more inconsis…

I've actually had the same itch and decided to give it a go ... So far I'm one year into the project, learned a ton and highly recommend to anyone who'd listen - try writing you own harness. It can be fun, it can be intoxicating, it can also be boring and mundane. However you'll learn so much along the way, even if you thought you already were well versed.

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

#16

Tooling like this is why I really want to build my own harness that can replace Claude Code, because I have been building a few different custom tools that would be nice as part of one single harness so I don't have to tweak configurations across all my different environments, projects and even OS' it gets tiresome, and Claude even has separate "memories" on different devices, making the experience even more inconsis…

The problem with this is that you won't get to enjoy the heavy subsidies of Claude subscriptions

But yeah, after the price hikes, it's inevitable that people will run open source harnesses

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

#18
Interesting. What kind of context usage does it have when switching between the two providers? Like is it smart about using the # tokens when you go from claude -> codex or vice versa for a conversation?

How does ctx "normalize" things across providers in the context window ( e.g. tool/mcp calls, sub-agent results)?

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

#20
post #2

Since prompt caching won't work across different models, how is this approach better than dropping a PR for the other harnesses to review?

Great callout about the prompt caching, this switch is going to burn subscription limits on Claude real real fast.

Unless the goal is to move from one provider to another and preserve all context 1:1. And I can’t seem to find a decent reason why you would want everything and not the TLDR + resulting work.

Post reply on HN