nowfound

Alternatives

Products that do what Qarinah does

Your project remembers when your coding agent changes

  1. 1

    Use Codex at 35.6% lower costs

    Apr 2026

  2. 2

    Repo-native memory for coding agents

    Jul 2026 · github.com

  3. 3
    Caveman161

    why use many token when few do trick

    24d ago · caveman.so

  4. 4
    Conduit137

    Fix the tool-list bloat slowing your AI agent

    Jun 2026

  5. 5

    Make Claude Code faster and cheaper without losing context

    Mar 2026

  6. 6

    Persistent memory for AI coding agents

    Apr 2026

  7. 7
    Code Mode144

    Slash MCP token usage by 68%

    Nov 2025

  8. 8

    The open sparse MoE model for agentic coding

    Apr 2026

  9. 9

    Spotify Wrapped for Claude, Codex & a Public leaderboard.

    Jun 2026

  10. 10LC

    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

  11. 11

    Track AI CLI spending across Claude, Codex & Gemini in 40ms

    Feb 2026

  12. 12PC

    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

  13. 13MS

    As a consultant I foot my own Cursor bills, and last month was $1,263. Opus is too good not to use, but there's no way to cap spending per session. After blowing through my Ultra limit, I realized how token-hungry Cursor + Opus really is. It spins up sub-agents, balloons the context window, and suddenly, a task I expected to cost $2 comes back at $8. My bill kept going up, but was I really going to switch to a worse model? No. So I built l6e: an MCP server that gives your agent the ability to budget. It works with Cursor, Claude Code, Windsurf, Openclaw, and every MCP-compatible application.…

    Apr 2026 · l6e.ai

  14. 14PR

    Hi HN, While building RAG agents, I noticed a lot of token budget was wasted on formatting overhead (HTML tags, JSON structure, whitespace). Existing solutions felt too heavy (often requiring torch&#x2F;transformers), so I wrote this lightweight, zero-dependency library to solve it. It includes strategies for context packing, PII redaction, and tool output compression. Benchmarks show it can save ~15% of tokens with negligible latency overhead (<0.5ms). Happy to answer any questions!

    Dec 2025 · github.com

  15. 15HN

    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

  16. 16PM

    I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~&#x2F;.claude&#x2F;.credentials.json, detects token type (OAT vs…

    Feb 2026 · github.com

  17. 17TT

    I use Claude Code, Codex and Cursor (and sometimes Antigravity) basically every day, and could never tell how much I was actually consuming across all of them. So I built TokenMaxxer. A small CLI reads the files these tools already write locally and puts it all in one dashboard, broken out by tool, model, provider and day. It covers 18 tools now, and you get a profile page with your daily activity, cost estimates, and your top models and tools. There's also a global leaderboard if you want to compete against other TokenMaxxers! I'd love to see if anyone can beat the first place (currently…

    Aug 2026 · tokenmaxxer.xyz

  18. 18CS

    Hi HN! Token cost has started to become a high topic of concern to all of us. I tried a few (awesome) tools such as rtk, caveman, and the recent (hillarious but effective) ponytail. What they usually do, is in-line token reduction, e.g. try to compress requests &#x2F; responses as much as possible. But then it hit me (and I’m sure others had similar ideas) - just like we have routers that pick the right model, why not have something that will also narrow down the amount of available tools, skills and mcps based on repo&#x2F;context? People usually accumulate skills, agents, MCP servers,…

    Jun 2026 · github.com

  19. 19MA

    Hello there HN I experimented with agentic coding recently and I felt the need to track more contextual data by project. Also I felt the need to be able to go beyond the 1D chat to communicate with agents. So I created a local document memory, that is discoverable by agents themselves. The CLI is designed to be easy to pick up by agents. It allows humans to collaborate too by reading &#x2F; searching &#x2F; editing documents in the store. I have a Mac native GUI in the review process, I hope it will show up in the App Store soon. You can try it easily, instructions here:…

    Jun 2026 · metabrain.eu

  20. 20TC
  21. 21ES

    Are you spending hundreds of dollars a month on AI coding costs? I built European Swallow AI, an API that uses reasoning models (Claude, Deepseek) for thinking and cheaper specialized coding models (Qwen, Grok) to write code, so you can save token costs while still getting high quality code. With an OpenAI formatted endpoint you can try European Swallow in Cursor, Typing Mind, Xibe AI and your own custom apps. During testing, European Swallow scored 80.5% on Big Code Bench and over 90% on the HumanEval+. It averaged $2.60 per million tokens compared with the $15 per million output tokens of…

    Oct 2025 · europeanswallowai.com

  22. 22PM

    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

  23. 23RC

    Claude Code &#x2F; 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

  24. 24SO

    hello everyone, my first post! AA here, founder of ⌘ Langbase.com — we are a developer platform for building and scaling serverless AI memory agents. I know surveys can be boring, but this one’s different—it’s interactive! That's very much intentional. My team and I have been up for the last 21 hours putting together this report. This was a looot of work, so I hope y'all like it. Introducing … State of AI Agents 2024 report On Langbase, we processed 184 billion tokens and handled 786 million AI agent runs from 36K developers. From all that data plus insights from 3.4K builders who filled out…

    2024 · langbase.com

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