garden holds the knowledge.
Your agent judges it.
garden gives any coding agent maintained engineering knowledge: guidance published as immutable, addressable snapshots with their provenance, served from a hosted store under a key.
The garden command remains unpublished, with no public download. Its hosted endpoint is active under a valid access key, with no public sign-up.
garden holds; the agent judges.
garden stores, filters, delivers, validates and records. It never ranks by engineering merit, recommends, synthesizes, classifies or calls a model on the server. Every judgement of what applies, from retrieval to application, belongs to the agent reasoning inside its harness.
What garden is
One curated corpus
garden's knowledge is engineering guidance by language, purpose, technology and concern, authored from acquired sources under recorded treatment. There is one authored corpus. What an agent receives is an immutable published snapshot of it, and no customer repository holds a copy of the library.
Three doors, one client
An agent reaches garden through the documented HTTP API, the standalone
garden command, or the local MCP server that comes with the command. People
read the guides here.
Codex first
The MCP objective passed in Codex against the saved package and a fixture service; hosted current and historical reads were verified separately. Claude Code has no fresh proof against the current package and service. Every other client remains unverified until it is proven, and the guides say so.
Keyed, and free in beta.
Every read of the guidance needs an access key, which Fernworks issues. garden is free during its beta, and any later price is announced before it applies; guidance a customer has already received is never withdrawn from that customer.
garden and greenline
Each works without the other. When a greenline user enables garden, the only bridge between them is a consultation and its receipt: greenline records what it received and never what it applied, and garden never reads greenline's records.
For a greenline personA greenline install now needs no account, no key and no service; it works entirely offline and keeps every method, artifact and receipt it had. The built-in guidance was the premium part; it moves to garden, which the owner can enable when they want it. A fresh install has no maintained knowledge until its owner enables garden.
Start with the guides.
One guide for what is available now, and one for each door.