Local observability for developers and agents

Catch the process before the evidence disappears.

Monitor turns volatile machine state into grouped local issues, bounded diagnoses, and durable evidence—without an account, a daemon, or a cloud dependency.

Start investigating Connect an agent

brew install --cask abdul-hamid-achik/tap/monitor

Local-firstStudio + JSON + MCPmacOS + Linux

Live machine state collecting · 1s

monitor studio local

OverviewCPUMemoryProcessesTrends

CPU82.3%high

Memory9.8GBof 16 GB

Temperature52°Creal sensor

Disk31%156 GB used

CPU by corerolling 60s

P091.7%

P173.8%

E061.2%

E143.1%

Top processesCPU

PIDCOMMANDCPURSS

8421node82.3%2.1G

9102chrome12.7%1.4G

7788go8.3%890M

6651rust-analyzer3.1%420M

AnomalyCPU spikenode (8421) at 82.3% · baseline median 24.1%

1 overview9 tabscollecting · 1s

01: One collectorEvery interface sees the same facts
02: Local issue modelEvents grouped into durable threads
03: Bounded by defaultStable JSON and intentional limits
04: Agent-safe actionsTyped input plus confirmation gates

A complete local investigation

From a transient spike to evidence you can keep.

Monitor follows one coherent path from live signal to issue, diagnosis, and incident bundle. Select a stage to see the contract exposed to both humans and agents.

01 / Signal

A process leaves its baseline.

Monitor compares current CPU, memory, disk, and process state with bounded local history.

investigationlocal

$ monitor watch --interval 1s

cpu: 82.3%
median: 24.1%
delta: +58.2

One model, three surfaces

Stay visual. Go scriptable. Hand off safely.

Use the interface that matches the moment without changing the underlying process model, safety rules, or evidence format.

01 / Studiohuman

The machine, composed for focus.

Nine keyboard-driven views keep live metrics, trends, processes, settings, and actions close without becoming a wall of dashboards.

Explore Studio

02 / CLIautomation

Signal that pipes cleanly.

One-shot JSON, streaming NDJSON, stable exit codes, and bounded outputs fit scripts and CI without a translation layer.

$ monitor snapshot --compact | jq '.cpu.usage_percent'
18.4

Read the CLI guide

03 / MCPagents

Context with sharp edges.

Ten typed tools advertise read-only, destructive, and idempotent behavior. Mutations require confirmation and still honor process protection.

monitor_analyzeread-only

monitor_issuesread-only

monitor_killconfirm

Configure MCP

Local developer stack

Built to outlive an ephemeral environment.

Monitor observes the run. Chalupa provides the environment. file.cheap retains its artifacts. codemap and vecgrep add code and semantic context when an investigation needs to go deeper.

See integration contracts

observe + groupMonitor

environmentchalupa.run

artifactsfile.cheap

code contextcodemap

semantic searchvecgrep

Agent-safe by construction

Read freely.
Mutate deliberately.

Read-only tools return bounded structured context. Actions such as killing or profiling require confirm: true, then pass the same protected-process checks used by Studio and the CLI.

Review the safety model

MCP requestdestructiveHint: true

monitor_kill

{
  "pid": 8421,
  "force": false,
  "confirm": true
}

typed input accepted · protection checks pending

Install Monitor

One binary. Your machine stays yours.

Start with the maintained Homebrew tap, download a release archive, or build from source. No account or background service required.

Fastest path

Install a verified release with Homebrew

The tap selects the right binary for macOS or Linux and for Apple Silicon, Intel, or ARM64 automatically.

brew install --cask abdul-hamid-achik/tap/monitor

01
Verify the binarymonitor --version
02
Open Studiomonitor studio
03
Check integrationsmonitor doctor

The next incident starts locally

Keep the signal.
Lose the guesswork.

Install Monitor, open Studio, and turn the next unexplained spike into evidence.

Open the guide View source