Skip to main content
The meridian CLI is a bash script that wraps macOS launchd, letting you manage all Meridian daemons without touching launchctl directly. After installation, the script is symlinked into /usr/local/bin/meridian (or ~/.local/bin/meridian) so you can call it from any directory.

​
Commands

Enables and bootstraps every Meridian LaunchAgent, then prints a live status summary. The daemons started are, in order:If any .plist file is missing, meridian start prints an error for that service and exits with a non-zero code. Run ./install.sh to reinstall missing plists.
The PM worklog (Jira / GitHub / Linear) pipeline and the coding-agent indexer used to ship as their own LaunchAgents (com.meridiona.jira-updater, com.meridiona.coding-agent-indexer). They now run inside com.meridiona.daemon, so meridian status only reports the four labels above.
The Rust daemon TCP-connects to the MLX server at startup to verify it is reachable. If the MLX server is not running, the daemon exits immediately. Start all services together with meridian start rather than launching them individually.
Disables and boots out every LaunchAgent, then kills any orphaned mlx_lm.server processes that launchd does not track. The .plist files in ~/Library/LaunchAgents/ are left in place so meridian start can bring everything back up.Use this command before editing ~/.meridian/.env so the daemon picks up the new values on the next meridian start.
Runs meridian stop, waits one second, then runs meridian start. Use this after changing environment variables or rebuilding the daemon binary.
Queries launchd for the running state of every registered service and prints a colour-coded summary:
  • ✓ running (pid N) — service is up and has a PID
  • ⊘ loaded but not running — launchd has the plist but the process is not active
  • ✗ not installed — plist is missing; run ./install.sh
Run meridian status any time you are unsure whether the stack is up.
Tails a log file from ~/.meridian/logs/. All arguments are optional.Valid targetsEach component has a normal log (everything) and a paired -error log (WARN/ERROR only) so you can grep for problems without scrolling past routine output.FlagsExamples
The Rust daemon also writes structured JSON logs to ~/.meridian/logs/meridian-rust.jsonl.<date> for jq-friendly grepping outside the CLI.
Runs a comprehensive, read-only system-health sweep across every Meridian daemon and prints a colourised (when stdout is a TTY) by-daemon table, a root-cause Diagnosis section, and an escalation footer when anything needs attention. The CLI wrapper delegates to the daemon binary’s health engine — if the binary is missing or stale, a minimal bash fallback runs so meridian doctor always produces something useful.Run meridian doctor as the first diagnostic step whenever something seems wrong: a missed Jira sync, a blank dashboard, a misclassified session, or a daemon that looks alive but isn’t producing output. Every check is content-free — counts, timestamps, status codes, reachability — never screen content or ticket text.Check groupsEach row is ✓ ok, ⊘ warn, · info, or ✗ critical. Failing rows show a → remedy line with the exact command to fix them. The exit code is 0 on a clean run and 1 when any check is critical.Flags--fix repair tiersAnything still failing after --fix is escalated: a content-free diagnostic bundle is written to ~/.meridian/ so you can share it with the team or hand it off to claude.Examples
The daemon also runs a subset of these checks (capture-layer / L1 only) as a startup preflight, logging warn/error to daemon.log. The preflight is non-fatal — the daemon still runs — so always confirm with meridian doctor if you suspect a fault.
Prints a read-only, human-readable report of the day’s PM worklogs: the hour ledger (done / pending / stuck), worklogs grouped by state (drafted, approved, posted, rejected, failed), and a per-ticket table with the synthesised Jira comment for each row. Useful for a quick “what is the daemon about to post?” check before approving worklogs in the dashboard.This command is read-only — it never writes to the DB and never calls Jira / GitHub / Linear. It also skips daemon initialisation, so it’s safe to run while the daemon is up.FlagsExamples
One-shot run of the Stage 4 PM worklog pipeline: walks the day’s hour ledger and drafts one worklog per task per ready hour. Worklogs land in the drafted state — they are never auto-posted. Approve them in the dashboard (or run meridian worklog-post-approved) to send them to Jira / GitHub / Linear.Use this when you want to regenerate drafts for a past day, recover from a failed run, or kick the pipeline manually without waiting for the next daemon cycle. The daemon runs the same pipeline on a schedule, so under normal operation you do not need to call this command.FlagsExamples
Running meridian pm-worklog while the in-daemon worklog pipeline is also active can have both processes hit the LLM at the same time. The global LLM gate prevents corruption, but for predictable behaviour run this against a stopped daemon (meridian stop) when backfilling.
Posts every worklog you have approved in the dashboard to its provider (Jira / GitHub / Linear) immediately. This is a one-shot run of the same approved-poster sweep the daemon performs every ~60 seconds, so use it when you want a result now — for example, right after approving a batch of worklogs in the dashboard and not wanting to wait for the next cycle.This is the only CLI command that writes to a real ticketing system. Worklogs in any state other than approved are skipped.Example
Writes the session-summary Claude Code slash-command file to ~/.claude/commands/session-summary.md so claude -p /session-summary resolves to the prompt Meridian uses to summarise coding-agent transcripts for the Jira worklog.Without this file, claude -p /session-summary returns Unknown command and the summariser silently falls back to the local MLX model for every Claude Code session — you lose subscription-claude quality on the transcript summaries that feed the worklog. Run this once per machine where Claude Code is installed.The command is idempotent (safe to re-run) and writes nothing if the file already exists. meridian doctor warns when the skill is missing, and meridian doctor --fix runs this command for you, so most users never need to invoke it directly.Example
Opens ~/.meridian/.env in your $EDITOR (falls back to nano if $EDITOR is not set). This is the canonical way to update API keys, change the poll interval, or toggle classification without hunting for the file path.After saving, run meridian restart so the daemon picks up the new values.
You can also set $EDITOR to any editor you prefer before calling this command:
Walks you interactively through the three macOS privacy panes that screenpipe requires:
  1. Screen Recording — opens the System Settings pane; click +, navigate to the screenpipe binary, add it, and toggle it on.
  2. Accessibility — same steps.
  3. Microphone — screenpipe appears here only after it first requests mic access. Grant Screen Recording first if screenpipe is not listed yet.
After each step the script waits for you to press Enter. Run meridian restart afterwards so screenpipe picks up the newly granted permissions.
Without Screen Recording permission, screenpipe cannot capture frames and Meridian will have no data to process.
Updates a source checkout to the latest main in one step: git pull --ff-only, rebuilds the Rust daemon (cargo build --release), rebuilds the Next.js UI (npm run build), then restarts every daemon via meridian restart. Use it after a release announcement, or any time you want to pull upstream fixes without running each step by hand.This command only works in a source checkout (the directory contains a Cargo.toml). For production installs from npm, upgrade with:
If git pull --ff-only fails (local commits that haven’t been pushed, or a non-fast-forward), meridian update exits without rebuilding so you can resolve the conflict yourself; rerun meridian dev build and meridian restart afterwards.Example
The command prints the new version on success — either the contents of the VERSION file or the short Git SHA if VERSION is missing.
Prompts for confirmation, then stops all daemons, runs each service’s uninstall script, kills orphaned mlx_lm.server processes, and removes the meridian and meridian-daemon symlinks from /usr/local/bin/ and ~/.local/bin/.Your data at ~/.meridian/ is not removed. Delete it manually if you want to wipe everything:

​
install.sh Flags

The installer (./install.sh) accepts flags that let you customise or automate the setup process.

--no-ui

Skip the Next.js dashboard build. Useful on headless machines or when you only need the daemon and MCP server.

--dry-run

Preview every action the installer would take without executing any of them. Helpful for auditing the setup on a new machine.

--no-daemon

Build all binaries but do not register any launchd agents. Use this if you want to manage service startup yourself.

--skip-permissions

Skip the interactive macOS permissions walkthrough. Useful when re-running the installer after permissions are already granted, or in scripted environments.

--skip-env

Skip all credential prompts entirely. Existing values in the .env files are preserved. Use alongside --skip-permissions for fully non-interactive re-installs.

--mlx

Install and register the persistent MLX inference server as a launchd daemon. Requires Apple Silicon. Enables faster, on-device session classification with no external API calls.
Example — build only, no prompts, no daemon registration: