pulse-agent 2.0.3

Self-hosted personal intelligence agent

The self-hosted personal intelligence agent.

pulseagent.dev · Documentation · Contributing

Ingest your digital life, discover patterns, write an Obsidian-style vault, get push insights — all self-hosted.

---

Install

curl -fsSL https://pulseagent.dev/install.sh | bash

pipx install pulse-agent   # or: uv tool install pulse-agent

Defaults: config under ~/.config/pulse, data under ~/.local/share/pulse (override with PULSE_CONFIG_DIR). Next: pulse configure → pulse init → pulse run — see Quickstart.

Documentation

Documentation lives under docs/ in this repository. The deployed site serves the same guides at pulseagent.dev/docs (site base path (/docs/)). Browse on the web: Quickstart, Configuration, Operations runbook, and Connectors. Canonical repo sources (edit these in PRs): docs/index.md, Quickstart, Configuration, Operations runbook, and Connectors.

Paths and environment: Standalone app, CLI commands, and the MCP server use PULSE_DATABASE_PATH. That variable selects the SQLite event store; use PULSE_VAULT_PATH for vault markdown. Override the config directory with PULSE_CONFIG_DIR (default finds .config/pulse.toml under ~/.config/pulse). pulse and pulse-mcp read the same variables; discovery day boundaries and related scheduling semantics are documented in the Operations runbook (PULSE_TIMEZONE).

MCP

Use pulse-mcp with Claude Code, Cursor, OpenClaw, etc. Setup, client JSON, tools, and resources: MCP agent setup.

Send this to your agent:

Read https://raw.githubusercontent.com/JEFF7712/pulse/main/docs/self-hosting/mcp-agent-setup.md and follow every step to install Pulse (pulse-agent), ensure pulse.toml exists, and register pulse-mcp in my MCP settings for this machine.

Develop

uv sync --group dev && uv run pytest

Layout and companion app: Contributing.

---

pulseagent.dev | PyPI | GitHub