Alternatives
Products that do what Frame – Managing projects, tasks, and context for Claude Code does
I built Frame to better manage the projects I develop with Claude Code, to bring a standard to my Claude Code projects, to improve project and task planning, and to reduce context and memory loss. In its current state, Frame works entirely locally. You don’t need to enter any API keys or anything like that. You can run Claude Code directly using the terminal inside Frame. Why am I not using existing IDEs? Simply because, for me, I no longer need them. What I need is an interface centered around the terminal, not a code editor. I initially built something that allowed me to place terminals in…
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15IL
VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less. So I built my own IDE around that workflow. Terminals are a first-class citizen, every project stays alive in the background with visual statuses. Close the workspace and come back weeks later, everything is still in its place. I've been using it for weeks and it's a big productivity boost. The…
Jul 2026 · github.com
- 16EC
I participated in the Nvidia + Vercel 2 hour hackathon in SF tonight, and built something I've wanted, but hadn't tried building. I implemented an MCP Server and VS Code extension to allow Claude Desktop to place breakpoints, step through code, and execute expressions (assuming language support). So you can ask it a question that requires actually stepping through the code and now it can actually do that - check values for you, etc. It's _definitely_ not perfect. Have improvements? Please make a PR!
2025 · github.com
- 17DC
After a year of producing all my code through Claude Code, I was growing frustrated with losing Terminal tabs and not noticing when sessions are ready to continue. I looked around at all the terminal managers people have been building for this type of workflow and couldn't find anything that worked for me. Cmux came close but was too buggy in the area I cared the most about: knowing when my sessions are ready for input. I also felt like the sidebar was too cluttered and hard to parse visually. So, I made my own Claude-first terminal manager and optimized it for the habits I've developed over…
Apr 2026 · github.com
- 18D2
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
- 19CC
I built Claude‑CMD, an open-source command-line interface for working with Claude Code commands, configurations, and AI-driven workflows. It’s designed to help developers and PMs streamline how they interact with Claude Code in coding tasks, automation, and prompt management. Website: claudecmd.com Happy to answer questions or hear suggestions. You can also contribute your own commands to help improve the project. Contributions welcome!
2025 · github.com
- 20PT
I vibe-coded a terminal tool called Pluqqy (I had a dormant domain on hand) to help me keep LLM context organized while coding with AI. It’s my first time writing Go and my first terminal app, built almost entirely with Claude Code. • What it does: Pluqqy lets you manage prompts, rules, and context as small building blocks, then stitch them together into a single file (like AGENT.md or CLAUDE.md) that your coding agent can consume. It’s meant to reduce context drift and make iteration easier. • Why I built it: I was losing track of my agent context between sessions and wanted something…
Oct 2025 · github.com
- 21IB
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
- 22CR
Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…
Mar 2026 · github.com
- 23
- 24PC
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →