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…
Show HN: Ctx – a /resume that works across Claude Code and Codex
11–20 of 32 posts
Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#12Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#13Tooling 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
#14Earlier 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...
Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#15Tooling 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…
Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#16Tooling 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…
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
#17Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#18How 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
#19Re: Show HN: Ctx – a /resume that works across Claude Code and Codex
#20Since prompt caching won't work across different models, how is this approach better than dropping a PR for the other harnesses to review?
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.