FAQs

Spruce is in beta and free to use. Licensing and pricing for the generally-available release will be announced on buildwithspruce.com.

Spruce project data lives on your local machine in your OS application-data directory, and in any git remote you configure for the project. Nothing is uploaded to a Spruce-operated server. See The .spruce Directory.

Yes. If you don't link any code repos, Spruce is fully usable as a planning tool: the Code page and worktree features stay hidden, but artifacts, comments, views, templates, and agents all work. Skip the Code Repositories step in the project wizard to start plan-only.

Not today. Spruce assumes git for the branch-artifact link, worktrees, the Activity feed, and sync. Other VCS backends are on the roadmap.

The Spruce project holds your plan: artifacts, templates, views, actions. A code repo holds your code. They're separate git repos with separate remotes. See Open Your First Project.

Not concurrently. Spruce's sync model is pull-merge-push, like ordinary git. When two people edit the same artifact, the second one to sync gets a conflict; Spruce's sync flow shows a built-in conflict-resolution UI for picking sides per-block. For non-overlapping changes, Spruce auto-resolves where it safely can.

No. Agents run as local processes; Spruce launches them via terminal actions. The agent's inference may go to the cloud (Claude Code talks to Anthropic's API), but Spruce itself doesn't run any agent code on a server.

macOS is the most battle-tested. Windows and Linux builds are available, and both are getting active work, with platform-specific quirks called out in Platform Notes.

Parts of Spruce (the docs-core library, the spruce-cli crate) are open source. The desktop app itself is closed-source during the beta.

Use the in-app feedback form under Help → Send feedback, open an issue on our issue tracker (link in the app's About dialog), or join our Discord for live discussion.

Changelog and upcoming features are published under Changelog.