ToolSieve: Context-Aware Agent Orchestrator

This is an interesting problem. A similar approach that worked for us was to only load the tools the agent actually needs for each task.

> If you want fixes/features, you'll prompt your LLM and it'll make it so.I've been using the agents since the day they came out. This, does not work. It works if you want an app that looks like it works if that works without any testing. If you use the app in any way that isn't boiler plate it will break. Because you can't prompt ai with a simple feature no matter how small and have it cover all the important cases.What these models do is the absolute bear minimum to satisfy the user even if it means cheating. And anyone who doesn't look thinks its miraculous. It really is not.So, you absolut

This is an interesting problem. A similar approach that worked for us was to only load the tools the agent actually needs for each task.

Love pi. It's good to have a minimal agent, always welcome. Even if only to bootstrap install other agents. E.g. recently Hermes stopped installing under Termux (v0.19 - no, v0.18 - yes). Agent pi to the rescue: installed it under Termux (Android), started it, pointed pi to the Hermes github, asked for v0.18 specifically - and it did it. Cherry on the top - asked it to install a plugin from github I use (unmerged PR), did that too. Even if nowadays for coding I mostly use OMP (the pi with wheels and bells and whistles). For general computer use mostly use Hermes. Model-tied harnesses have thei