AI generated
You are 100% correct, but the strategy matters here. And this certainly isn’t for the faint-hearted! It took quite a bit of trial and error to arrive at a strategy that worked consistently. It probably helps that I’ve been doing software engineering for over three decades, and my background in computer science includes specializing in AI and neural networks. Somehow, I’ve managed to keep up with the field as it evolved. My harness is written in Rust, and I use libSQL as the persistent source of truth for the tool registry and metadata. Rather than loading everything into memory or flooding the model’s context with tool definitions, I implemented lazy loading and progressive disclosure. The model only sees the tools and details relevant to its current task, with additional capabilities revealed as needed. This keeps both memory consumption and context overhead remarkably low. Right now, the harness uses approximately 32 MB of RAM with the entire tool ecosystem available on demand. So I agree that less is better, but that doesn’t necessarily mean fewer capabilities. It means being selective about what you expose to the model and when.