soft-fig

A garden is a folder of small, plain-text notes about your machine — how it’s configured, why a choice was made, what broke and how it got fixed. soft-fig keeps it encrypted at rest, version-controls it for you, and hands it to Claude as memory it can read and write by typed, convention-stamping tools. You open Claude from the garden’s root, and every session starts knowing your machine instead of re-learning it.

The promise is trustworthy, not easy: history is signed and content-addressed, secrets stay sealed even from the model, and the store on disk is ciphertext only — plaintext exists through a FUSE view that is there only while the garden is unlocked. soft-fig also ships a dotfile deploy command, cross-device sync, and Growlight, an autonomous work loop that runs on the garden — but the garden is the product.

1.0.0-alpha.1

This is the first public alpha. soft-fig is built and used daily on one device by one author, so expect rough edges. It installs by building from source only (Linux, systemd, FUSE) — no prebuilt packages yet. Read what ships and what doesn’t before you rely on it, and don’t store anything you can’t afford to lose: the cryptography has not been independently audited.

Where to go

What a garden isThe core idea and where the product stands today.

Install & grow your first gardenBuild from source, then onboard a garden end to end.

Working with ClaudeThe root-open practice, the alias, and a starter-prompt cookbook.

GrowlightThe autonomous work loop the garden ships as a tool.

CLI referenceThe full softfig command surface, plus MCP verbs and schema.

The codebaseCrates, the daemon, the FUSE view, the ciphertext VCS, the vault.

Curious how this started? The story — the reasoning and how the idea grew — is being written in the author’s own voice.

soft-fig is open source under the AGPL-3.0-or-later.