// momentum

tracking since W47

// why it's here

  • Active: last commit today
  • Health 90/100 with only 14 stars
  • 12 forks for 14 stars: people build on it

// how to help

// readme

intentd

intentd is a local-first, headless Rust daemon that owns the Intent domain model — workspaces, notes, tasks, comments, agents, git, pull requests, scripts, terminals, files, and events — and exposes it over a JSON-RPC 2.0 API. Clients (a desktop UI, a CLI, or an agent acting as an MCP client) are thin: all business logic lives in the daemon.

This repo is consumed as a git submodule by intent-hq/intent.

What it is

  • Local-first. The default transport is a Unix-domain socket (mode 0600, newline-delimited JSON-RPC frames). A secure WSS/TLS LAN transport (bearer auth, origin allow-list, TLS fingerprint pinning) runs alongside it; there is no plaintext TCP product transport.
  • Single source of truth. The daemon owns all durable state in SQLite (via sqlx with embedded migrations); clients hold only ephemeral UI state.
  • One service layer, many transports. Transports are thin; the shared WorkspaceApi service surface is the single code path every listener — and the agent-facing MCP server — calls.
Read the full README on GitHub ↗

Health score

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

How it's calculated

Undervalued score

Activity relative to attention (stars + watchers). Above 50 means a lot of activity for a project its size. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

How it's calculated

Tags

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

How it's calculated