Local-first · open source · evidence-backed

A steady heartbeat for useful operations.

Run recurring checks, remember what happened, and turn verified signals into reviewable tickets—without requiring a paid service.

Start locally Inspect every tool

01 Heartbeat Run bounded checks

02 Evidence Keep facts and context

03 Ticket Capture actionable work

04 Review Humans close the loop

SQLite memoryLocal and portable

MCP toolsStructured and explainable

No key requiredUseful on first run

Writes are visibleApproval stays explicit

The operating loop

Small checks compound into useful memory.

A pulse checks local repository state, documentation, and selected logs. Every run keeps compact evidence in SQLite. Before creating work, it looks for related tickets—so the next agent or human starts with history instead of a blank prompt.

Deterministic checks come first. Models are optional interpretation layers, not required infrastructure.

Self-describing at launch

Know what a tool does before it runs.

Every tool declares its use case, cost class, data boundary, write behavior, approval rule, and a working example.

ExplainRead only

operations_describe

Returns the complete tool and connection catalog for setup, review, or UI rendering.

“What can this pulse use, and which options cost money?”

MemoryRead only

tickets_list

Search prior and active work before staffing a new ticket.

HeartbeatLocal write

pulse_run

Runs configured checks and stores evidence. Ticket creation is separately opt-in.

TriageExplicit write

ticket_create

Adds one proposal to the local queue with source, tags, and priority.

HistoryRead only

pulse_history

Surfaces recurring noise and changes across recent runs.

SetupNo secrets

connections_list

Explains free, self-hosted, subscription, and bring-your-own paths.

Free first, connected when useful

Use the tools you have. Keep the choice visible.

The host owns the guided connection prompt and secret store. Operations Pulse supplies the standard capability contract.

Capability Path Launch status

Git, files, logs, SQLite Free · local · open source Available

Email IMAP · bring your account Available · read only

GitHub and Linear Connected account or token Available · read only

PostHog and Sentry Self-hosted or cloud Available · read only

Model interpretation Local model, subscription, or API Optional by design

Guided setup

Choose a path; keep credentials outside the browser.

This picker generates a reviewable local setup command. It never asks for, stores, or transmits a credential. OAuth stays in a compatible host's own approval screen; bring-your-own credentials stay in your environment or secret manager.

First local run

Useful before you connect anything.

Node.js 24 or newer is the only runtime requirement. The supported first release is local stdio MCP plus SQLite.

$ npm install
$ npm run build
$ node packages/core/dist/cli.js init
$ node packages/core/dist/cli.js pulse run --root .

Endorsed child identity

Operations Pulse, by Openly Useful.

The pulse-and-ticket motif belongs to this product. The Open Monitor identity remains the unchanged institutional mark.