Operate your installation

Install as a System Service

To have Signet start automatically on boot:

cd platform/daemon
bun run install:service

macOS (launchd):

launchctl load ~/Library/LaunchAgents/ai.signet.daemon.plist

Linux (systemd):

systemctl --user enable signet.service
systemctl --user start signet.service

Editing Your Agent

If you enabled Signet-managed identity, your agent identity lives in four self-managed files:

$SIGNET_WORKSPACE/AGENTS.md — How the agent operates, including rules, workflow, and constraints. This is the main file that syncs to harnesses.

$SIGNET_WORKSPACE/SOUL.md — Personality, voice, values, and temperament.

$SIGNET_WORKSPACE/IDENTITY.md — Who the agent is.

$SIGNET_WORKSPACE/USER.md — Who you are to the agent, plus preferences and relationship context.

These files are meant to be maintained over time as durable context.

$SIGNET_WORKSPACE/MEMORY.md is different. It is auto-generated by Signet as episodic and operational memory. Do not edit it manually.

Edit the four identity files directly in your editor or via the dashboard’s config editor. Changes sync to harnesses automatically within 2 seconds.

If you want Signet only for memory, recall, sources, and secrets, run setup with --identity-mode off or choose the identity-off option in the wizard. In that mode Signet does not create, inject, or sync AGENTS.md, SOUL.md, IDENTITY.md, or USER.md; your harness-native instruction files remain the source of truth.

Auth and Team Deployments

By default, Signet runs in local mode with no auth required on requests. In the default local setup, the daemon also binds to localhost only, which keeps that unauthenticated mode local by default. For team deployments or self-hosted remote access, Signet supports token-based auth with roles and scopes. See Auth and Self-Hosting for setup details.

Troubleshooting

Daemon won’t start

Check if port 3850 is in use:

lsof -i :3850

Remove a stale PID file if needed:

rm $SIGNET_WORKSPACE/.daemon/pid
signet daemon start

Embeddings not working

Make sure Ollama is running:

ollama serve &
ollama pull nomic-embed-text

Or check that OPENAI_API_KEY is set in your environment (or stored as a secret and referenced in agent.yaml).

Changes not syncing to Claude Code

Make sure ~/.claude/ exists and you have the harness configured:

ls ~/.claude/CLAUDE.md
signet status

Dashboard not loading

curl http://localhost:3850/health
signet daemon logs

Next Steps

Configuration Reference — all agent.yaml options
Memory System — how remember/recall works
Pipeline — how Pipeline V2 extracts and processes memories
Connectors — document-source connector details
Remote Harness Connectors — connect harnesses on other machines to one Signet daemon
Hooks — lifecycle hooks for harness integration
Analytics — session and memory analytics
Diagnostics — health checks and pipeline status
Documents — ingest files and URLs into memory
SDK — embed Signet in your own apps
Auth — token-based auth and team deployment modes
Harnesses — detailed integration docs
API Reference — HTTP API for scripting and tooling