About include.tools
An open-source toolbox for AI agents, built by a small team. We believe agents are limited by the quality of their tools — and that most tools in the AI ecosystem today are too shallow, too leaky, or too expensive to be trusted with real work. We're building the version we wanted.
What we're building
include.tools is a local-first toolbox that gives AI agents one super tool — a typed TypeScript API to real-world services like email, calendar, and drive, running in an isolated sandbox on your own machine.
Credentials stay encrypted outside the runtime and are injected at the network layer, so tool code never sees raw secrets. Network access is deny-by-default per tool — every tool declares an allowlist of hosts it can reach, and anything off-list is blocked. Every tool's trust properties (untrusted input exposure, private data access, exfiltration capacity) are declared in its manifest so you see the risk before you install.
The toolbox runs on your machine, with your LLM API key, against your real accounts. We never see your data.
The team
Include Tools Team — a small group of engineers building an open-source tools layer for AI agents. Reach us at [email protected].
License
The toolbox is licensed under GNU AGPL v3. We chose AGPL because it protects the project from being forked into a closed-source hosted product by a third party while the open-source version is still maturing. Most individual users, teams, and companies can use the toolbox exactly as they would under an MIT-style license — AGPL's network-copyleft clause only triggers obligations if you modify include.tools and then serve your modified version to others over a network.
We commit to relicensing to MIT once the project reaches 10,000 GitHub stars. At that point, the ecosystem is large enough that AGPL's protective purpose has been served, and a permissive license better supports the long-term health of the project.
Commercial licenses are available for organizations that need terms different from AGPL — for example, teams at companies with blanket AGPL policies. Email [email protected].
Contributing
We welcome contributions. Because we intend to relicense the project to MIT in the future (see above), every contribution must be made under a Contributor License Agreement that assigns copyright to [email protected]. The CLA is a standard copyright-assignment document and is required before any pull request can be merged.
This is the same pattern used by many dual-licensed open-source projects and is necessary to give us the flexibility to eventually relicense the entire codebase at once, without needing to track down every contributor individually.
Commercial roadmap
We intend to add paid hosted services on top of the open-source toolbox over time. We're staying deliberately vague on specifics — the open-source core needs to land first, and we'd rather keep our options open than commit to a particular shape before we know what users actually need.
Our commitment: the toolbox is open source under AGPL v3 and will always be free to install. Paid hosted services will be additive — never a replacement for the free toolbox.
Contact
- General: [email protected]
- Commercial licensing & sales: [email protected]
- Contributions: [email protected]