Alternatives
Products that do what ctxbudgeter does
Control what AI agents know before they act
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13CS
AI agents accumulate stale tool results — file reads, web fetches, bash outputs — in their context window. Every one sits there for the entire conversation, consuming tokens and degrading quality. The standard fix is auto-compaction: wait until full, then drop content indiscriminately. Context Surgeon gives the agent three operations — evict, replace, and restore — so it can manage its own context. It works as a transparent local proxy that intercepts API requests, assigns IDs to content blocks, and applies eviction directives before forwarding. The agent calls the tools via bash. The proxy…
Apr 2026 · github.com
- 14OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 15
- 16FA
LLM agents rely on tool calls — but tool responses are huge. Gmail, CRMs, and APIs return bloated JSON LLMs choke on large responses You only need 2–3 fields, but frameworks give you zero control Toolflow is an AI-native framework to fix this: * Filter tool responses before they hit the LLM * Context modes: `minimal`, `full`, `custom`, or `ai` * Composable TypeScript tool registry GitHub: [https://github.com/dksingh1997/toolflow](https://github.com/dksingh1997/toolflow) Would love feedback — especially from those building with LLMs in production.
2025 · github.com
- 17IM
Every time I wanted to use LLMs in my existing pipelines the integration was very bloated, complex, and too slow. This is why I created a lightweight library that works just like scikit-learn, the flow generally follows a pipeline-like structure where you “fit” (learn) a skill from sample data or an instruction set, then “predict” (apply the skill) to new data, returning structured results. High-Level Concept Flow Your Data --> Load Skill / Learn Skill --> Create Tasks --> Run Tasks --> Structured Results --> Downstream Steps And the bast part: Every step can be saved and reused as…
2025 · github.com
- 18MM
I built MCPlexor to solve a token waste problem I kept running into with MCP-based agents. The Problem: MCP (Model Context Protocol) is great for giving LLMs access to external tools. But if you connect multiple servers (GitHub, Linear, Postgres, Slack), you end up with 40-50k tokens of tool definitions injected into every request – before the agent even does anything. On a 200k context model, that's 25% gone. On smaller models, it's worse. And most runs only use 1-2 tools. The Solution: MCPlexor sits between your agent and your MCP servers. Instead of loading all tool definitions upfront:…
Feb 2026 · mcplexor.com
- 19CP
Hi, we're Sohaib and Hannan from APIMatic. We built Context Plugins: given an OpenAPI spec, we generate SDKs and an MCP server that exposes structured API context to AI coding assistants. This gives tools like Cursor access to comprehensive, up-to-date API context (including SDK documentation and API integration patterns), instead of relying on outdated training data or code scraped from GitHub. We've just launched a pilot with PayPal, it's live on the PayPal Developer Portal https://developer.paypal.com/serversdk/java/getting-started/.... In our benchmarks for…
Mar 2026 · apimatic.io
- 20CP
CoreMem lets you build collections of context, called a mem, and share it with any AI agent via URL, a Chrome extension, MCP, Cursor/VS Code plugins, a skill, and more. Instead of re-explaining your project or goal when you switch agents or start new sessions, CoreMem keeps your context centrally organized so that any AI tool can read it. This originally started as a CLI I built that kept pieces of context (Project A/B/C details, my writing style, preferred tech stacks, coding style, etc) in a SQLite database. I could instruct various agents to “use my `coremem` CLI to…
May 2026 · coremem.app
- 21IB
TLDR; I built a tool that turns any API into a CLI designed for ai agents --- Got tired of dealing with bloated context windows from MCP servers and skills that stuff entire API docs into the agent's context CLIs fix this, agents run a single command to self-discover everything an API has to offer So, built a tool to generate them for any api. All CLIs are written in Go, fast and lightweight, no dependencies Help text (via the --help flag) is the killer feature: all context for each command/endpoint/parameter is extracted directly from the user-facing API docs and enhanced with…
Mar 2026 · instantcli.com
- 22CC
agents. Not a custom truncation strategy, not a sliding window, not dropping old messages and hoping for the best. The failure mode is well-understood: your context window fills up, you truncate from the top, and the agent loses the thread. It forgets the task it was working on, the file path it just wrote to, the UUID it needs to reference. The conversation breaks. The problem is everyone keeps solving it by throwing away information instead. Truncation is fast to implement and quietly wrong. The agent appears to work until it doesn't, and debugging context loss in a long-running session is…
Mar 2026 · github.com
- 23MF
Hello HN, I created Decispher (decispher.com) to enable human developers and AI agents working alongside each other to share their context. It has some pretty cool features, like Branch Story (explains why a branch's code looks the way it does) and Session Context Transfer (an MCP tool that can copy context from one chat, agent, or machine to another). You can also capture context from engineering platforms like Slack, JIRA, and Git(hub/lab) just by tagging @Decispher.
Jul 2026
- 24LC
Prompt instructions like 'never do X' don't hold up in production. LLMs ignore them when context gets long or users push hard. Limits sits between your agent and the real world. Every action — database writes, API calls, refunds — gets intercepted and checked against your rules before it executes. Deterministically. No LLM involved in enforcement. Three modes: Conditions: hard rules on structured data Guideance: validate LLM output before it reaches the user and give the agent chance to reason and retry Guardrails: scan for PII, toxicity, prompt injection etc One line to integrate: npm…
Feb 2026 · limits.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →