Skip to content

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.

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

The 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.

Nightly builds come from main automatically. They get fixes and features first and can break. Install one instead of stable with:

Terminal window
curl -fsSL https://signetai.sh/install.sh | SIGNET_CHANNEL=nightly bash

The installer does not change where updates come from. After step 2, keep updates on nightly with:

Terminal window
signet update channel nightly

Run signet update channel stable to go back.

Check that your shell can find it:

Terminal window
signet --version

If 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:

Terminal window
# zsh; use ~/.bash_profile for bash
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zprofile
export PATH="$HOME/.local/bin:$PATH"

Your agent’s hooks call signet from PATH too, so fix this now rather than later.

Terminal window
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.

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.

Terminal window
signet status
Status
● Daemon running v0.237.1
Dashboard: http://127.0.0.1:3850
✓ agent.yaml
✓ database
Memories: 1
Path: /Users/you/.agents

A ○ Daemon stopped line means the daemon is not running; start it with signet daemon start.

Terminal window
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.

Terminal window
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)

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:

Terminal window
signet connect claude-code

Here is what the connector does on each session:

An agent session with Signet connected. The hooks run the signet CLI, which asks the daemon.each promptAgentClaude Codesignet hookfrom PATHDaemon127.0.0.1:3850SessionStart1session-start2working memory3inject context4UserPromptSubmit5user-prompt-submit6related context7inject context8SessionEnd9session-end10store transcript · queue summary
An agent session with Signet connected. The hooks run the signet CLI, which asks the daemon.
  1. Agent to signet hook: SessionStart
  2. signet hook to Daemon: session-start
  3. Daemon to signet hook: working memory
  4. signet hook to Agent: inject context
  5. each prompt:
  6. Agent to signet hook: UserPromptSubmit
  7. signet hook to Daemon: user-prompt-submit
  8. Daemon to signet hook: related context
  9. signet hook to Agent: inject context
  10. Agent to signet hook: SessionEnd
  11. signet hook to Daemon: session-end
  12. Note: store transcript · queue summary
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.