Alternatives
Products that do what Pull Claude Code transcripts into your Codex session, and vice versa does
Hi HN, I'm Rob. Contextify indexes every Claude Code and Codex session on your machine into one local, searchable database. The current session, in either tool, can search all of it: /total-recall in Claude Code, $total-recall in Codex. Demo: https://www.youtube.com/watch?v=FvrvRGp4C9M | Mac app: https://contextify.sh (App Store or DMG) | Linux: CLI with a one-line installer, same search. No signup. I split my work between Claude Code and Codex. When I burn through rate limits on one, I switch to the other, and new models keep leapfrogging each other, so the…
- 1
- 2
- 3
Get your trading card based on your CC & codex usage
May 2026
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18SS
Hola HN! Long time lurker, sometimes commentor, first time poster here. I’ve been working alongside my two co-founders and a few colleagues on a project I’m excited (and a little nervous) to share with you all! Like many of us, I’ve lived a tortured existence with AI coding (is it vibes?) over the past few months - I think November was a big moment with this. But, one thing I’ve noticed after building orchestration layer after orchestration layer is that the thing I always came back to was “what the hell is Claude Code actually doing?” Perhaps it’s because of the time Claude Code got…
Jun 2026 · backplanes.com
- 19OA
I spend a lot of time in Claude Code and Codex with my friend. We kept losing the context behind changes because every agent session lived on one person's laptop, and by the time code made it into a PR, all the reasoning was gone. We tried commits, PRs, and docs, but they only really capture the end result, so we built a tool to keep all of our agent sessions in one searchable place. Now we (and our agents) can check out anyone's session and ask things like "what was Alex working on yesterday?" It's also quite helpful in recovering the context behind a change days or weeks later. Ocean works…
Aug 2026 · ocean.mosaic.inc
- 20CC
*Claude Code History Viewer – A macOS Desktop App for Reviewing Claude Code History at a Glance* Hello everyone, I have a habit of reviewing my coding history when working with AI. It's important to trace back and understand "how did I get to this result?" Recently, while using Claude Code, I found it quite inconvenient to check the history in separate terminal tabs or editor windows. So I built a desktop app called *Claude Code History Viewer* using *Tauri + React + Rust*. ## Key Features & Highlights * *Claude Code Conversation History Visualization* When you install Claude Code,…
2025 · github.com
- 21RC
Claude Code / Codex session metadata can actually tell a story about how you work with AI coding agents. 50 days ago we posted about analyzing 1.6k Claude Code sessions from our own team. Skills were used in 4% of sessions, 26% were abandoned early, and we had no real benchmark for what good looked like. Now across 20k+ sessions, we started looking at behavior patterns from derived session metadata: consistency, intensity, session shape, repo breadth, output, cost intensity, and model range. Nine archetypes fell out, which we turned into playful cards. We built a Spotify Wrapped meets…
May 2026 · app.rudel.ai
- 22IB
I wanted to share a project I have been working on over the past week. It is a simple local memory system that saves your sessions into Markdown files, which can be viewed later. I developed this after using Claude Mem. I really enjoyed working with it, but it was consuming a lot of RAM, and each Claude session was becoming a major resource hog. I also tried other plugins and MCP solutions, but ran into similar issues, either slow performance or concerns about data being sent elsewhere. Because privacy was a big thing for me, I decided to build my own solution that keeps all data local.
Feb 2026 · github.com
- 23PM
This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks!
Jan 2026 · github.com
- 24DE
I wanted a very simple way to dump prompts, links, and todo lists into my claude code and codex agents. And to work outside of the context window. This works particularly well for sharing "Projects" between Claude/ChatGPT etc. It's open source here; https://github.com/Vochsel/dump.page Anything you dump on the board becomes an llms.txt - spatially sorted implicitly and explicity sorted via connection edges. Would love HN's thoughts!
Mar 2026 · dump.page
Ranked by how close each launch is in meaning, then by votes. Refine with a description →