Playground

The Graft Playground runs the real Graft v0.8.0 CLI compiled to WebAssembly. It stores the worktree, SQLite databases, and .graft/ repository in the browser’s Origin Private File System (OPFS), so you can learn the model without installing Graft or changing local files.

Local browser state

Playground data stays in this browser and origin. It survives reloads until you use Reset data or clear the site’s storage.

Follow The Guided Tour

1. Open the Playground and wait for the GRAFT v0.8.0 · WASM runtime indicator.
2. Open Guide. Start with Basics to initialize a repository, create data.sqlite, add files, stage changes, and commit them.
3. Continue with Branches and Merge to see the same worktree materialize different app states.
4. Finish with Conflicts to inspect a structured SQLite conflict and choose a resolution.

Each guide step runs a real command in the terminal. The OPFS file tree, SQLite editor, Version panel, history, and diff views update from the resulting repository state.

What You Can Explore

Area	What it demonstrates
Files	Text, image, and SQLite paths in one app-state worktree.
Terminal	The v0.8.0 CLI plus a small OPFS shell.
Version	Status, staging, commits, branches, reset, and history.
Diffs	Text changes, image versions, and SQLite row diffs.
Conflicts	Three-way merge state and row-aware resolution.

Browser Boundaries

• Remote synchronization is intentionally unavailable in the browser build.
• OPFS is origin-private; ordinary filesystem tools cannot open its paths.
• Reset data permanently deletes the Playground’s OPFS worktree and history.
• The Playground is for learning and evaluation, not production persistence.

Continue On Your Machine

After the guided tour, run the CLI Quickstart to repeat the same repository flow in a local directory. If your application deliberately needs the optional Graft VFS, see the SQLite Extension Quickstart.