Install

Let your agent do it

Paste this into Claude Code, Cursor, Codex, or any agent that runs shell commands:

Use curl to read gardenscm.ai/agents.md and perform the setup to install garden

It installs the CLI, authenticates you, installs the garden skill so it uses garden instead of git, and offers to push your first repository. That is the whole setup — the rest of this page is the same thing by hand.

Or do it yourself

curl -fsSL https://get.gardenscm.ai/install.sh | sh
garden auth login
garden skill install

The install script also runs garden setup for you: it downloads the engine and grants it permission to mount your checkouts, which is the one point it prompts for sudo — mounting a filesystem requires it. If that step is skipped or interrupted, the script tells you, and garden setup finishes the job. It is also the first thing to try if checkouts ever stop mounting.

garden auth login opens a browser for OAuth. It stores a refresh token and a per-user mTLS certificate for talking to the repository server. Check with garden auth status.

garden skill install writes the “use garden, not git” guide into the agent configs on your machine — Claude Code, Cursor, Codex. Add --repo <path> to also drop it into a repository’s AGENTS.md so it travels with the project. garden skill status shows where it landed.

Confirm the install with garden version. Already have garden? garden update moves you to the latest release; the CLI also self-updates in the background once a day, and garden update --rollback undoes a bad one.

Running auth login from an agent

It blocks until the browser step finishes. Stream the command’s stdout rather than waiting for it to exit, or the agent looks hung while the browser is open.

Next: make your first push.