nowfound

Alternatives

Products that do what Context Gateway does

Make Claude Code faster and cheaper without losing context

  1. 1

    Persistent memory for AI coding agents

    Apr 2026

  2. 2
    Sipcode148

    Keep Claude Code's context clean for sharper answers

    Jun 2026

  3. 3
    WOZCODE194

    Cut Claude Code costs by up to 50%

    May 2026

  4. 4

    Turn your work activity into structured AI context.

    Feb 2026

  5. 5
    Termexo98

    A local Windows workbench for Claude Code and Codex

    Aug 2026

  6. 6

    Connect Claude Code to your internal systems w/o credentials

    Mar 2026

  7. 7IC

    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

  8. 8PC

    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

  9. 9LC

    Hi HN, I'm building Librarian (https://uselibrarian.dev/), an open-source (MIT) context management tool that stops AI agents from burning tokens by blindly re-reading their entire conversation history on every turn. The Problem: If you're building agentic loops in frameworks like LangGraph or OpenClaw, you hit two walls fast: Financial Cost: Token usage scales quadratically over long conversations. Passing the whole history every time gets incredibly expensive. Context Rot: As the context window fills up, the LLM suffers from the "Lost in the Middle" effect. Response latency…

    Feb 2026 · uselibrarian.dev

  10. 10OO

    One coding agent orchestrator UI for Claude and Codex, but actually feels nice. Free, open-source, MIT licensed. Why I built it: - I wanted a lightweight UI as nice as the Codex app, but without the complexity and the custom diffs on the side - I want files and diffs open straight in my editor! - And I wanted both agents - Anthropic + OpenAI — in one place How it works: - No API keys, no OAuth, no separate billing — it just uses whatever you're already logged into. So your Claude Max and ChatGPT/Codex subscriptions both work out of the box. - Talks to Claude Code via the Claude Agent…

    Apr 2026 · github.com

  11. 11DG

    I got frustrated watching Claude Code fail at using modern APIs (ask it about GPT-5 and it says it doesn't exist). Existing solutions like Context7 dump thousands of tokens of irrelevant docs into context. So I built DeepCon. How it works: - Crawled 10,000+ official docs using agentic browser automation and structured them hierarchically - Query decomposer breaks down requests, searches in parallel, then merges only relevant context - Returns just what's needed: 2.4x fewer tokens than Context7 Results on our benchmark: DeepCon achieved 90% accuracy vs Context7's 65% on real-world tasks with…

    Nov 2025 · deepcon.ai

  12. 12DE

    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

  13. 13HN

    I built Hydra because I kept losing my flow when Claude Code hit usage limits mid-task. I would copy context, open another tool, and then re-explain everything. This would be super annoying for me. Hydra wraps your AI coding CLIs (Claude Code, Codex, OpenCode, Pi, or any terminal-based tool) in a single command. It monitors terminal output for rate limit patterns, and when one provider runs out, you switch to another with one keypress. Your conversation history, git diff, and recent commits are automatically copied to your clipboard so you can paste and keep going. The fallback chain is…

    Apr 2026 · github.com

  14. 14PT

    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

  15. 15D2

    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

  16. 16
    ctxopt1

    One context config for Claude Code, Codex, Cursor & more

    5d ago · projectone2020.github.io

  17. 17OA

    I've been running Claude Code and Codex together every day. At some point I figured out you can use tmux to let them talk to each other, so I started doing that. Once they could coordinate, I kept adding more agents. Before long I had a whole team working together. But any time I rebooted my machine, the whole thing was gone. Not just the tabs. The way they were wired up, what each one was doing, all of it. Nothing I'd found treats your agent setup as a topology, as something with a shape you can save and bring back. So I built OpenRig, a multi-agent harness. A harness wraps a model. A "rig"…

    Apr 2026 · github.com

  18. 18MA

    2024 · repo-distillery.vercel.app

  19. 19FM

    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…

    Jan 2026

  20. 20CC

    Uses agent and Git Hooks to automatically create Git Notes on commit, containing the agent conversation that led to that commit. Works if either you or the agent commit. It's basically the same thing as entire.io just announced that they got $60m investment for. Except I got Claude Code to write it last week, in my spare time, without really paying attention. I certainly didn't read or write any of the code, except for one rubbish joke in the README. I've got a Claude Code instance working on Gemini CLI support and OpenCode support currently.

    Feb 2026 · github.com

  21. 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

  22. 22IM

    heylo! open sourcing a plugin that I've been daily driving for a month. And I promise, I can't go back to vanilla Claude Code. I'm a heavy Claude Code user, and a couple of things kept bugging me. Claude really likes to jump into code. And its responses are too long. I'd skim past walls of text just to find the recommendation. Plan mode helps, but it didn't go deep enough. The questions it asked were still implementation questions, when what I actually needed was alignment on the problem. So I made it stop. Relay is a different output style and two Python hooks. When you describe what you…

    Apr 2026 · github.com

  23. 23PA

    Claude Code is amazing at writing code, but it will happily build from under-specified requirements, implement the same thing different ways, and fail to write great tests unless you specifically ask it to. Prawduct is a set of prompts, skills, hooks, and artifact templates that help focus Claude Code on product development rather than code development. You can start from something a simple as "make a website with a scientific calculator" or as complex as "create a MMO with clients for iOS, Android, and web". You can specify as much or as little arch standards or implementation details as…

    Mar 2026 · github.com

  24. 24

    He doesn't waste shots

    22d ago · deepaksinghcs14.github.io

Ranked by how close each launch is in meaning, then by votes. Refine with a description →