Skip to content

Quickstart

This tutorial takes a local installation from zero to a working memory command. It uses the interactive setup route; use the reference pages when you need a managed or remote deployment.

On macOS or Linux, install the native binary:

Terminal window
curl -fsSL https://signetai.sh/install.sh | bash
signet --help

Windows users should install the package wrapper instead:

Terminal window
npm install -g signetai

See Install for package-manager alternatives and non-interactive setup.

Terminal window
signet setup

For a new workspace, setup asks how Signet should manage identity, then asks for an identity preset when managed identity is enabled. It asks for an agent name, harnesses, optional core plugins, how the daemon should run (local, Tailscale, or remote), embeddings, background inference, and optional advanced settings before showing the plan for confirmation.

The default Minimal identity preset keeps normal startup context small. Setup creates AGENTS.md for that startup context and DREAMING.md for Dreaming sessions. Other presets create a different set of identity files; do not assume that every workspace has SOUL.md, USER.md, MEMORY.md, or a hooks directory. See Set up Signet for the preset and workspace details.

Setup initializes the database and starts a local daemon unless you selected a remote daemon. It can then open the dashboard.

Terminal window
signet status
signet dashboard

signet dashboard opens the local dashboard and starts the local daemon when necessary. If setup points the workspace at a remote daemon, the CLI uses that configured daemon URL instead.

Terminal window
signet remember "Use Bun for this project" --tags project,tooling
signet recall "Which package manager should this project use?"

Use --critical with signet remember to pin a memory. Recall combines the available keyword and embedding search paths; setup can run without embeddings if you prefer.