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

Install from npm and have Meridian running and drafting worklogs in under 10 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

   Install the Meridian CLI from npm and run the one-time setup. The bundle ships a prebuilt binary — no clone, no compiler — and meridian setup installs any missing prerequisites (Homebrew packages, Python, screenpipe, ffmpeg) and registers the background services.

   npm install -g @meridiona/meridian
   meridian setup
   
2. Configure

   Open the config in your $EDITOR and add credentials for the tracker you use (Jira, Linear, or GitHub):

   meridian config edit
   
3. Start

   The setup command registers launchd agents that start automatically. Confirm everything is up and open the dashboard:

   meridian status
   # Dashboard → http://localhost:3939
   

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.