Interactive demo

Explore brewscope commands with synthetic output

Terminal

$ brewscope doctor

{ "schema": "brewscope.doctor/1", "ok": true, "generated_at": "2026-10-11T12:34:56Z", "source": { "brew": "7.0.7", "capabilities": { "brew": true, "fda": true, "fda_via": "com.apple.Terminal", "zsh_history": true } }, "data": [ { "check": "brew", "ok": true, "detail": "/opt/homebrew/bin/brew 7.0.7", "remediation": null }, { "check": "zsh_history", "ok": true, "detail": "/Users/demo/.zsh_history", "remediation": null }, { "check": "knowledgec", "ok": true, "detail": "/Users/demo/Library/Application Support/Knowledge/knowledgeC.db", "remediation": null }, { "check": "biome", "ok": true, "detail": "127 entries", "remediation": null }, { "check": "automation", "ok": false, "detail": "not probed: checking would raise a consent dialog", "remediation": "login items are read from LaunchAgents instead; opt in later with --allow-automation" } ], "truncated": false, "next": null, "warnings": [] }

What it shows

brewHomebrew version and location
zsh_historyShell history file availability
knowledgecmacOS app usage database access
biomemacOS activity streams access

Each check reports what brewscope can read on your machine. Full Disk Access is needed for app usage tracking.

Output envelope

Every brewscope command returns JSON with the same envelope structure, whether invoked by a human or an AI agent.

schema: versioned schema identifier

ok: true on success, false on error

generated_at: ISO 8601 timestamp

source: brew version and capabilities

data: command-specific payload

warnings: non-fatal notices

Roadmap

M0

Output contract, describe, doctor

Done

M1

Snapshot creation, inventory with filesystem attribution, orphan detection

M2

Capability taxonomy, conflict detection (PATH shadowing, functional overlap)

M3

Usage analysis: shell history, agent transcripts, app launches

M4+

Recommendations, migration planning, optional MCP server mode