Welcome to Meridian — Ambient Dev Automation Docs

Everything you need to install, configure, and run Meridian — the local-first daemon that turns screenpipe recordings into automatic PM ticket updates.

Meridian is a local-first ambient automation daemon that reads your screen activity, structures it into labelled work sessions, and automatically updates your Jira, GitHub, or Linear tickets — with zero manual input and no data leaving your machine. This documentation covers everything from installation to advanced configuration.

Introduction

Learn what Meridian does, how it works, and what you need before you install.

Quickstart

Clone, install, and have Meridian running and syncing tickets in under 15 minutes.

MCP Server Setup

Connect Meridian’s session data to Claude, Cursor, or any MCP-compatible AI tool.

CLI Reference

Every meridian command — start, stop, logs, doctor, config, and more.

Get up and running in three steps

1. Install

   Clone the repository and run the installer. It handles every dependency — Homebrew, Rust, Node, Python, screenpipe — and registers Meridian’s background daemons automatically.

   git clone https://github.com/meridiona/meridian
   cd meridian
   ./install.sh
   
2. Configure

   The installer walks you through an interactive credential prompt. Enter your OpenRouter API key plus credentials for any PM tools you use (Jira, GitHub, Linear). Skip any service you don’t need by pressing Enter.

3. Start

   Bring all daemons up with a single command, then open the dashboard to see your first sessions appear.

   meridian start
   # Dashboard → http://localhost:3000
   

All your data stays on your machine. Meridian never phones home, sends telemetry, or forwards screen recordings to any remote server. Your activity database lives at ~/.meridian/meridian.db and is yours alone.