Start with Garden
Garden is in early access. We set it up alongside your team: connect your data, find the first workflow worth automating, and put an agent on it.
Garden is the layer between your company and its agents. It connects to where the work happens, writes down how the work is done, and runs agents that do it.
Connect GitHub, Slack, Linear, QuickBooks, Postgres and the rest once. Garden reads the original records through each Connection, and agents reach them through Garden.
One place to connectRotating a credential does not change the Connection or anything granted on it.
Garden keeps your company’s context as plain documents: what the company does, how the work is done, who does it and where it goes wrong. Each claim cites the evidence behind it.
It says what it does not knowUnknowns are written down next to the rest, not filled in.
Someone in Finance checks QuickBooks for invoices past terms, usually on Monday, and writes each customer from ar@acme.com. The reminder stops when the invoice is paid.
Reminders go out 12 days late on average. Disputed invoices get the same reminder as the rest.
Who decides to stop chasing an invoice. Nothing Garden can read records it.
Discovery agents read what you connected and keep Memory current. From it they find the workflows worth automating and say how often each one happens.
It runs continuouslyNew evidence reopens the documents and proposals that depend on it.
An agent starts as a proposal: the work, the evidence for it and the smallest access it needs. Approve it and the agent runs, on a schedule or when something happens in a Connection.
Nothing exists until you approveA proposal is data. It creates no agent, identity or grant.
Email each customer whose invoice is more than 7 days past terms, and stop when the invoice is paid.
Finance does this by hand about 41 times a month. Cited: 41 QuickBooks invoices and 38 Gmail threads.
Disputed invoices. A person should check the first ten reminders.
Add Garden to Claude Code, Codex or any MCP client. The agents you already run get your company’s context and the same scoped access as agents that run in Garden.
Use one part or all of itOriginal data and Memory are each usable on their own.
https://withgarden.ai/mcpStreamable HTTPGarden-Workspace-Id: your workspace ID
Browser sign-in and consentThe workspace ID is shown in Connections, under MCP setup.
No. Add Garden to the client you already use as a remote MCP server. Agents that run in Garden and agents that run in your own client are governed the same way.
Only the Connections granted to it. It has no access by default, like every other agent.
No. Discovery proposes an agent, and a person with authority over the requested Connections approves it. Discovery never approves its own proposals.
It says so. Coverage and unknowns are kept with the documents, and a proposal states what it does not cover.
Garden is in early access. We set it up alongside your team: connect your data, find the first workflow worth automating, and put an agent on it.
Point Claude Code, Codex or any MCP client at Garden to give it your company’s context and only the access its work needs.