Show HN: Ratel, give agents unlimited tools and skills without context bloat

github.com

19 points by jack1689 8 hours ago

Hi HN! We're Giacomo and Roberto, authors of Ratel (https://github.com/ratel-ai/ratel)

We used to help SaaS companies build agents on top of their products. Whenever we wanted to expand the agents’ complexity/scope, by adding more and more tools and instructions, we always run in the same issue: context bloat, with frequent hallucinations and sky high token bills. So we started constantly engineering the agents, dynamically loading tools, splitting them into subagents, inventing our own way to support skills

And that's exactly when we started building Ratel: a library to let your agent keep its full catalog of tools and skills, but progressively disclosing only the few that actually matter for each turn. Now you can grow your agent's capabilities without breaking it or taking out a loan for it

People are already using it in production, with a user cutting their token cost up to 81% in the first month without compromising the accuracy

We support both keyword and semantic retrieval, all in-process and without any additional infra. Open source, framework-agnostic, exposes OpenTelemetry metrics, available for Typescript and Python

Benchmarks: https://benchmark.ratel.sh

Some cool things we did with this:

• One team's agent had up to 300+ tools dynamically loaded into context. Ratel cut their token cost 81% in month one. • Another team split into several subagents instead, one agent per task. It worked, until the swarm got slow and expensive. We fixed this with our skills.

We're both here all day. Tear it apart, especially if you're an AI or SWE running agents in production

vinci00 6 hours ago

Isn't this just RAG for tools? Also, MCP already has tool search, how is this useful in that case?

  • jack1689 6 hours ago

    Hey, yes it's on the same family for sure! The difference is that it works with anything, not just MCPs, and it runs in-process without any additional infra (which usually isn't the case for other RAG solutions). Happy to hear your feedback if you try it out :)

tomhow 6 hours ago

[stub for offtopicness]

  • iustinai 8 hours ago

    man this could save me so much money lol

    • jack1689 8 hours ago

      Would love to hear your feedback if you can try it. We initially rolled out BM25 for tool search as it worked best for us internally. Recently rolled out also embeddings and an hybrid option that is being tested in production as we speak

  • KristianLentino 8 hours ago

    Benchmarks looks very promising! I’ll try to test this new tool in the next few days thanks for sharing!

    • rstagi 8 hours ago

      Thank you mate! Please share your feedback :)

  • atenareply 7 hours ago

    This looks so nice!

    • atenareply 7 hours ago

      I see you built the core in Rust with bindings to TS/Python. y?

      • jack1689 7 hours ago

        Yes! I should have mentioned in the original post. It was actually built in Typescript at first, but then the performance were not good enough for production use cases. With Rust the footprint was way lower, and we managed tear the latency down from 200ms to 20ms for a single search

  • missmoss 7 hours ago

    This is neat! It tackles a boring but real problem with agents. When you have too many tools, the model gets confused. This is a good search box for its tools instead of dumping everything into the prompt. Benchmarks is amazing!

    • jack1689 7 hours ago

      Thank you! Let us know how it works if you try it out :) of course real world is another story, but we agree benchmarks are amazing indeed!

  • flaviobernoni 7 hours ago

    really cool, first time I've seen anyone treat "which tools does my agent even get to see" as its own problem. Is the roadmap more about pushing deeper on the retrieval side over time, or mostly about covering more frameworks/languages?

    • jack1689 7 hours ago

      Thank you! Right now we're adding some frameworks adapters to lower the adoption friction, and pushing deeper on new algorithms on the retrieval side. More languages support is not on the radar yet, but we accept contributions! :)

  • bbg2401 7 hours ago

    Anyone else suspect this is an entirely astroturfed comment section?

    • tortilla 6 hours ago

      Yes. The comments read like positive ai vibes and their profiles seem empty and low karma.

      • jack1689 6 hours ago

        Hey guys, fair callout, but no AI involved, promise! You're right that some comments look off and someone's farming karma for sure. We see genuine traffic to the repo anyway, so people is checking it out!

        Critical feedback is what we're here for, so fire away if you have anything :)

        • tomhow 3 hours ago

          This comment was detected by our software as AI generated. It could always be a false positive, but if you're using AI at all to write your comments, please stop. It's against the guidelines and only harms your reputation in the eyes of the community.