buildwithspruce.com is built with React, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics.
Built with React, hosted on Cloudflare. Domain registered in 2026.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS3 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting1 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
chan.ns.cloudflare.commarvin.ns.cloudflare.comUser-agent: * Allow: / Sitemap: https://buildwithspruce.com/sitemap.xml
# Spruce > Spruce is a native desktop app for planning, code, and review. Each feature, bug, and task lives in your repo as plain markdown, and you can run any CLI agent in parallel across your work. This index covers the product docs plus top-level marketing and policy pages. ## Get started - [Get Started](https://buildwithspruce.com/docs/get-started): Spruce is a native desktop app that combines project planning, a code browser, terminals, and AI agents, all backed by plain-markdown files you can push to git. - [Install Spruce](https://buildwithspruce.com/docs/install): Download Spruce for macOS, Windows, or Linux, install it, and launch it for the first time. - [How Spruce Thinks](https://buildwithspruce.com/docs/how-spruce-thinks): Spruce's mental model in 10 minutes. The two-root model, artifacts, templates, worktrees, and agents. - [Open Your First Project](https://buildwithspruce.com/docs/open-first-project): Create a new Spruce project or import one from a remote. The home screen offers two paths, and a step-by-step wizard for each. - [Your First Artifact](https://buildwithspruce.com/docs/first-artifact): Walk through creating, editing, and saving your first artifact in Spruce. A feature with a description and pinned fields. - [Hand Work to an Agent](https://buildwithspruce.com/docs/first-agent): Start an agent on an artifact. Spruce creates a worktree, launches the agent, and lets you review its work via diffs and comments. ## Your workspace - [The Sidebar](https://buildwithspruce.com/docs/sidebar): Spruce's left-hand navigation, sectioned by Views, By type, Tools, and App, with the project switcher and sync menu in the header. - [The Focus Bar](https://buildwithspruce.com/docs/focus-bar): A persistent strip at the top of every page in Spruce that pins the artifacts most relevant to your current work, including ones assigned to you, linked to your branch, or matching a rule you define. - [Command Palette](https://buildwithspruce.com/docs/command-palette): Open anything in Spruce (artifacts, files, commands) by typing a few characters. ⌘K on macOS, Ctrl+K on Windows and Linux. - [Views](https://buildwithspruce.com/docs/views): A view is a named configuration of filters, group-by, sort, and visible fields applied to your project's artifacts. Spruce ships with several built-in views, you can save your own, and every view exposes the same filter / group / sort toolbar. ## Artifacts - [Artifact Types](https://buildwithspruce.com/docs/artifact-types): The five built-in artifact types in Spruce (feature, task, bug, chore, and memo) plus the option to create your own. - [Fields, Status, and Priority](https://buildwithspruce.com/docs/fields-and-status): The core fields most Spruce artifacts share (status, priority, size, and assignee) plus how they're defined by the artifact's template. - [Artifact Relationships](https://buildwithspruce.com/docs/relationships): Link artifacts together with relationship fields. Parent / child, sibling, cross-type. Relationships render as clickable chips and travel in the frontmatter. - [The Artifact Editor](https://buildwithspruce.com/docs/artifact-editor): Spruce's main editing surface for an artifact, with a header (title, fields, Start / Finish), markdown body, attachments, and the tool tabs that open the tool panel. ## Tools - [Tools Overview](https://buildwithspruce.com/docs/tools): Spruce ships five built-in tools (Code, Activity, Comments, Sessions, Git) each available in two surfaces. The global page for project-wide views, the artifact-scope tab for the open artifact. - [Code](https://buildwithspruce.com/docs/code): Browse files in any linked code repository, globally on the Code page, or scoped to an artifact's worktree from the Code tab in the tool panel. Same tool, two surfaces. - [Activity](https://buildwithspruce.com/docs/activity): A unified feed of code commits, pending Spruce changes, and pending code changes. Globally on the Activity page, or scoped to an artifact in the Activity tab. Same tool, two surfaces. - [Comments](https://buildwithspruce.com/docs/comments): Leave comments on blocks of an artifact, on the artifact itself, or on lines of code. The primary channel for the in-flight loop with an AI agent — comments auto-route to listening sessions or offer a menu to send to a session / start a new action, with activity badges and a Nevermind cancel for in-flight work. - [Sessions](https://buildwithspruce.com/docs/sessions): Spruce's built-in terminal sessions run inside an artifact's worktree, persist across project switches, and live in two surfaces, the global Sessions page and the per-artifact Sessions tab. - [Git](https://buildwithspruce.com/docs/git): The artifact-scope Git tab in the tool panel covers branch info, smart action, view changes, all git actions, commit history, and Finish. The behavior of each operation is documented on Branches and Worktrees. ## Code workflows - [Blame and File History](https://buildwithspruce.com/docs/blame): Git blame inside Spruce. See which commit and author last touched every line of a file, and click through to the commit context. - [Diffs and Commits](https://buildwithspruce.com/docs/diffs-and-commits): View pending changes, branch commits, and individual commit detail with per-file expandable diffs, all inside Spruce. - [Branches and Worktrees](https://buildwithspruce.com/docs/worktrees): Spruce creates a dedicated git branch and worktree for every artifact you start working on, giving you isolated checkouts per piece of work, so parallel progress doesn't conflict. ## Agents & Actions - [Actions](https://buildwithspruce.com/docs/actions): Actions are project-defined commands that run in an artifact's worktree, including agent launchers, dev servers, test runs, anything you can type at a shell. Defined as markdown files in actions/, with the body used as the system prompt. - [Action Recipes](https://buildwithspruce.com/docs/action-recipes): Ready-to-copy action definitions for common developer workflows. Agent launchers, dev servers, builds, unit tests, lint, and more. Real Spruce action format. - [Action Template Variables](https://buildwithspruce.com/docs/action-template-variables): Variables available inside an action's command and prompt body. Artifact ID, session ID, action content, paths, plus inlined templates and context blocks. - [MCP Tools](https://buildwithspruce.com/docs/mcp-tools): Spruce exposes artifact and comment tools via MCP so AI agents can read, write, and comment on your plan. - [Commenting Back on Agent Work](https://buildwithspruce.com/docs/commenting-back): Practical guidance for the human side of the agent-review loop. Writing review comments agents can act on, and recognizing the agent's claim/reply cycle. ## Templates - [Editing Built-in Templates](https://buildwithspruce.com/docs/editing-built-in-templates): Customize the feature, task, bug, chore, and memo templates. Change status options, add fields, tweak colors, without touching code. - [Creating a Template](https://buildwithspruce.com/docs/creating-a-template): Add your own template (incident, RFC, design review, anything) with its own fields, options, color, icon, and pinned hints. Templates are how artifact types get defined. - [Field Types and Options](https://buildwithspruce.com/docs/field-types): The field types available in Spruce templates (text, number, date, boolean, relationship, user) plus how to constrain values, allow multiple selections, mark required, and link artifacts to each other through relationship fields. ## Settings - [Global Preferences](https://buildwithspruce.com/docs/global-preferences): App-wide settings that apply across every Spruce project. Appearance, credentials, and keyboard shortcuts. - [Agents Settings](https://buildwithspruce.com/docs/agents-settings): Pick the default agent CLI Spruce uses when running actions, wire up MCP server config per agent, and see install / configuration status at a glance. - [Terminal Settings](https://buildwithspruce.com/docs/terminal-settings): Configure the integrated terminal's shell, arguments, renderer, and native-launcher app from a dedicated settings page. - [Per-Project Settings](https://buildwithspruce.com/docs/per-project-settings): Settings that belong to a specific Spruce project, including name, base branch, linked code repositories, focus bar filter, and worktree storage. - [Importing and Exporting Bundles](https://buildwithspruce.com/docs/import-export-bundles): A bundle packages a project's templates, views, and actions so you can reuse it across projects or share it with another team. - [Shell Configuration](https://buildwithspruce.com/docs/shell-configuration): Configure which shell Spruce launches for terminal sessions, plus any default arguments, environment tweaks, and platform-specific overrides. - [The .spruce Directory](https://buildwithspruce.com/docs/spruce-directory): What's inside a Spruce project folder on disk. Artifacts, templates, views, actions, and the config files that define how the project behaves. - [Removing a Project](https://buildwithspruce.com/docs/removing-projects): Three levels of project removal in Spruce, from just closing it to deleting all its data and linked code repos. ## Reference - [Keyboard Shortcuts](https://buildwithspruce.com/docs/keyboard-shortcuts): The full list of Spruce's default keyboard shortcuts. Navigation, focus bar, paired tool shortcuts, git operations, terminals, and the dynamic per-template / per-action / per-view shortcuts you can assign yourself. - [Artifact and Template Schema](https://buildwithspruce.com/docs/artifact-schema): The on-disk schema for Spruce artifacts and templates, including frontmatter fields, the body format, and the rules templates enforce. - [MCP Tool Reference](https://buildwithspruce.com/docs/mcp-tool-reference): Full reference for the MCP tools Spruce exposes to agents, including parameters, return values, and usage notes. - [Spruce CLI](https://buildwithspruce.com/docs/spruce-cli): The `spruce-cli` tool for daemon management, scripting hooks, and other command-line operations for power users. - [The .spruce Directory File Layout](https://buildwithspruce.com/docs/spruce-directory-layout): File-by-file reference for what's inside a Spruce project directory. Every folder, every config file, every storage format. - [Glossary](https://buildwithspruce.com/docs/glossary): Definitions of the Spruce-specific terms you'll see throughout the docs and the app. ## Troubleshooting & releases - [FAQs](https://buildwithspruce.com/docs/faqs): Frequently asked questions about Spruce. Licensing, data portability, team use, and platform support. - [Changelog](https://buildwithspruce.com/docs/changelog): Release history for Spruce. New features, bug fixes, and breaking changes per version. Versioned changelog entries start with the first GA release. - [Platform Notes](https://buildwithspruce.com/docs/platform-notes): Platform-specific behaviour, known issues, and workarounds for macOS, Windows, and Linux. ## Optional - [Homepage](https://buildwithspruce.com/): Product overview, features, and beta signup - [Privacy Policy](https://buildwithspruce.com/privacy) - [Terms of Service](https://buildwithspruce.com/terms)
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |