Why we build
Modern agent pipelines depend on fragile, outdated primitives. XML parsers that explode, feed libraries frozen for years, dependency surfaces that are unacceptably large — these are not edge cases. They are systemic.
We build because the stack deserves a reset: minimal dependency surfaces, auditable runtime code, and trust boundaries that are explicit. Every BOSS project is a deliberate step toward that baseline.
The three principles
Minimal by design
Small, intentional dependency surfaces reduce supply-chain risk and keep every line auditable. Zero runtime dependencies when possible. Custom engines when needed.
Agent-native
Every tool is built for agents first — MCP servers, SDK adapters, and explicit trust boundaries included. Agents call tools; tools donâ·¢t call agents by accident.
Open by default
MIT-licensed, publicly developed, welcoming contributions from day one. Open source is not a marketing move; it's a commitment to permanence.
Our commitment
Every BOSS release ships with:
- Permissive open licenses — MIT or equivalent, no hidden restrictions.
- Minimal dependency surfaces — zero runtime dependencies when possible, small, auditable stacks when not.
- Explicit trust boundaries — SSRF protection, XSS mitigation, prompt-injection defense, response size caps.
- MCP-ready tooling — JSON-RPC servers that agents can call as native tools.
- Public development — issues, PRs, discussions open in the public GitHub repos.
How to get involved
BOSS is for anyone who wants agent-native infrastructure that doesn't trade safety for features. Star a project, file an issue, or open a pull request.
If you're building agent pipelines, you don't have to accept the status quo. Start with tools that are minimal by design, agent-native, and open by default.