Open-source tools

The phrase covers a wide surface. Crafting Interpreters is a book whose full source, including two working Lox interpreter implementations in Java and C, lives in a public repository. The repo itself is the artifact: readers can build the interpreters, inspect every line, and submit corrections. That transparency is what makes it more than documentation.

LostWarrior/knowledge-base takes a different angle, releasing a zero-dependency bash CLI for organizing project context as tiered markdown files. The zero-dependency constraint is a deliberate design choice common in open-source tooling aimed at wide portability: nothing to install beyond bash.

Not all open-source tools are code utilities. The Micrographics Templates Figma library extends the concept into design assets: 50 customizable layouts and 40-plus vector symbols released for public use via the Figma Community.

Vet is an open-source local code review tool from Imbue that reads an AI agent’s conversation history alongside the diff to surface mistakes standard review misses. Its openness matters because the trust problem it addresses, verifying what an autonomous agent actually did, benefits from auditable tooling.

Strands Agents is an open-source Python and TypeScript SDK derived from Amazon production systems, providing built-in observability, guardrails, and multi-agent orchestration. Publishing production-grade infrastructure as open source lowers the bar for teams building on top of it.

The Jujutsu review workflow is less a tool than a technique built on one: it depends on jj, an open-source version control system, to make large-change review tractable by using commits as review-progress bookmarks.