Quickstart
This guide takes you from nothing to an agent that remembers you across sessions. It takes about five minutes.
You need macOS, Linux, or Windows x64, and an agent harness such as Claude Code, Codex, or OpenCode.
1. Install
Section titled “1. Install”curl -fsSL https://signetai.sh/install.sh | bashThe installer downloads a native binary for your platform, checks its SHA-256, and places it at ~/.local/bin/signet. It does not need Node or Bun.
iwr -useb https://signetai.sh/install.ps1 | iexThe installer places signet.exe in %LOCALAPPDATA%\Programs\Signet and adds it to your user PATH. Open a new PowerShell window afterward.
npm install -g signetaiThe package is a small launcher that runs the native binary for your platform.
Nightly builds
Section titled “Nightly builds”Nightly builds come from main automatically. They get fixes and features first and can break. Install one instead of stable with:
curl -fsSL https://signetai.sh/install.sh | SIGNET_CHANNEL=nightly bash$env:SIGNET_CHANNEL = "nightly"; iwr -useb https://signetai.sh/install.ps1 | iexnpm install -g signetai@nextThe installer does not change where updates come from. After step 2, keep updates on nightly with:
signet update channel nightlyRun signet update channel stable to go back.
Check the install
Section titled “Check the install”Check that your shell can find it:
signet --versionIf you see signet: command not found, add ~/.local/bin to your PATH. When the installer runs through a pipe, it cannot edit your shell profile for you, so it prints the commands for your shell instead. They look like this:
# zsh; use ~/.bash_profile for bashecho 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zprofileexport PATH="$HOME/.local/bin:$PATH"Your agent’s hooks call signet from PATH too, so fix this now rather than later.
2. Create a workspace
Section titled “2. Create a workspace”signet setup Workspace: /Users/you/.agents Continue setup: http://127.0.0.1:3850/#setup Connect your provider, select a memory model, and test the connection.Setup creates a workspace at ~/.agents, starts the Signet daemon on 127.0.0.1:3850, and opens onboarding. If you installed the desktop app, onboarding opens there; otherwise it opens in your browser. If nothing opens, paste the URL yourself.
3. Finish onboarding
Section titled “3. Finish onboarding”Onboarding is nine short screens. Three of them decide how Signet works for you.
| Screen | What to do |
|---|---|
| Identity | Name your agent. This is required. |
| Harnesses | Select the agents you use, such as Claude Code. Signet installs their hooks. |
| Connection | Sign in to a model provider, or point at a local model, then Test and enable memory. |
The other screens are optional. Sources imports an Obsidian vault, transcripts, or files. Search keeps keyword search by default; pick an embedding provider for semantic recall. First memory saves one memory to prove the loop works.
No provider yet? Choose Set up later. Saving and recalling memories still works. Memory processing pauses until you connect a provider under Settings → Inference, and Dreaming starts on its own once you do.
4. Check that it is running
Section titled “4. Check that it is running”signet status Status ● Daemon running v0.237.1 Dashboard: http://127.0.0.1:3850 ✓ agent.yaml ✓ database Memories: 1 Path: /Users/you/.agentsA ○ Daemon stopped line means the daemon is not running; start it with signet daemon start.
5. Save and recall a memory
Section titled “5. Save and recall a memory”signet remember "Use Bun for this project" --tags project,tooling✔ Saved memory: 3f9c1e0a-6b2d-4c8e-9f71-2a5d8b0e4c13 (no embedding) Tags: project,tooling(no embedding) is expected with keyword search. Add --critical to pin a memory.
signet recall "which package manager should this project use"Found 1 memory (keyword).
Primary matches:- [64%] id: 3f9c1e0a-6b2d-4c8e-9f71-2a5d8b0e4c13; Use Bun for this project (fact, keyword, 2026-10-08, by user)6. See it in your agent
Section titled “6. See it in your agent”Start a new session in the agent you connected and ask what it knows about the project. Sessions that were already open do not have the hooks.
Skipped the Harnesses screen? Connect one from the terminal:
signet connect claude-codeHere is what the connector does on each session:
- Agent to signet hook: SessionStart
- signet hook to Daemon: session-start
- Daemon to signet hook: working memory
- signet hook to Agent: inject context
- each prompt:
- Agent to signet hook: UserPromptSubmit
- signet hook to Daemon: user-prompt-submit
- Daemon to signet hook: related context
- signet hook to Agent: inject context
- Agent to signet hook: SessionEnd
- signet hook to Daemon: session-end
- Note: store transcript · queue summary
If something goes wrong
Section titled “If something goes wrong”| Symptom | Fix |
|---|---|
signet: command not found |
Add ~/.local/bin to PATH, as in step 1. |
| Onboarding did not open | Open http://127.0.0.1:3850/#setup. |
Daemon is not running |
Run signet daemon start. |
Memory is paused until you connect a provider |
Connect a provider under Settings → Inference in the dashboard. |
Another workspace is running at this address |
Stop the other daemon, or run setup against its workspace. |
Could not start Signet |
Run signet doctor. |
| The agent remembers nothing | Start a new session, confirm signet status shows the daemon running, and check that signet is on PATH. |
Next steps
Section titled “Next steps”- Set up Signet: scripted setup, identity presets, and remote daemons.
- Your first session: memory, secrets, and skills in daily use.
- Connect a harness: every supported agent and what its connector installs.
- Memory and recall: how recall ranks and what it returns.
- CLI reference: every command and flag.

