Alternatives
Products that do what Rudel does
Claude Code & Codex session analytics for dev teams
- 1
Get your trading card based on your CC & codex usage
May 2026
- 2RC
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
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11D2
Mike, cofounder of DevSwarm here. I’ve been using Claude Code heavily for the last few months (multiple Max plans). Running sessions in parallel across git branches or worktrees is fast, but it breaks down quickly in practice because of sprawl. Terminals everywhere, editor windows everywhere, and you lose track of basics like which agent is on which branch and what is ready for review. DevSwarm is what we built to solve that. The core abstraction is simple: workspace equals branch. Each workspace runs its agent session(s) and keeps the state visible. In 2.0 we added a full VS Code IDE…
Feb 2026
- 12SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 13
- 14SI
Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's…
Jan 2026 · github.com
- 15IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 16PC
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…
Jul 2026 · contextify.sh
- 17TA
Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…
Jul 2026 · github.com
- 18
- 19TA
Hi everyone! I built this because I wanted a little bit more organization around my Claude sessions, worktrees and plans while staying in the terminal and not relying on another SaaS tool. Since it's a command line tool, the added bonus is that Claude can use `td` directly. The td calendar was just a fun add-on but the Claude session stats have been pretty interesting! Let me know what you think!
Apr 2026 · github.com
- 20OA
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
- 21TC
I got tired of screenshotting claude code sessions to share with teammates, so I built this. It converts session into beautiful web pages with proper rendering of tool calls. Works by parsing CC's session, extracting steps, then uploading to a simple sharing service. Takes about 2 seconds to generate a shareable link. Live examples: - https://cc.getpochi.com/s/IldMh27j (Research claude-code-share repo) - https://cc.getpochi.com/s/mrqGqgOT (Creating an issue in a GitHub repo)
2025 · github.com
- 22NO
We're open sourcing Nimbalyst, a multi-agent, visual workspace for building with Claude Code, Codex, and Opencode (alpha). It pairs parallel session management with WYSIWYG editors so you and your agents can work on the same files at the same time. The core idea: agents edit files, you edit files, and Nimbalyst makes that collaboration legible. Built-in WYSIWYG editors cover markdown, mockups, Excalidraw diagrams, data models, spreadsheets, and code (Monaco). Every edit is tracked back to the session that made it, with red/green WYSIWYG markdown diffs for review and approval. A session…
Apr 2026 · github.com
- 23IC
Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…
2025 · shadowgit.com
- 24AW
AdaL is the world’s first local coding agent with web UI. Claude Code has proven that coding agents work best when they are local, bringing developers back to the terminal. Terminal UIs are fast and great with shortcuts, shell mode, and developer-friendly workflows. But they are limited in history and image display, and the experience varies by terminal and OS. Many of them flicker (buuuut not AdaL CLI ). Most importantly, they can be quite intimidating for non-technical users. This led us to explore new possibilities for a coding agent interface. What if you could get the best of both…
Jan 2026 · youtube.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →