Review console
The health CLI is the deterministic core for reads, writes, agreement status, imports, reviews, gaps, batteries, and consults.
local-first · alias-only · own-risk
LLM Health helps you review labs, wearables, records, and self-reported context over time: timelines, quick reviews, diagnostic gaps, test candidates, category consults, and research queues. Local-first, alias-only, and explicit about risk.
required before use
No medical advice: LLM Health does not diagnose, prescribe, order tests, treat disease or create a clinician relationship. It organizes records, calculations, questions and research notes. You are responsible for all decisions, delays, experiments, purchases, interventions and omissions.
Do not use it for emergencies or urgent symptoms. Do not start, stop, combine or change medications, supplements, procedures, devices or preventive protocols solely because an agent suggested or questioned something.
Every private HUB must explicitly accept the agreement once. The CLI stores only the agreement version and timestamp in agreement.json.
get running
The default path is ~/health. Use any private local or synced directory. Keep raw PDFs, Apple Health exports and clinical dumps out of Git.
brew tap nvk/tap
brew install llm-health
health agreement show
health config hub-path ~/health --init --accept-risk
health doctor
health welcome
interfaces
The health CLI is the deterministic core for reads, writes, agreement status, imports, reviews, gaps, batteries, and consults.
The repackaged health-v2 stack provides timelines, chart exports, wearable context, categories, and local analytics.
Claude Code, Codex, OpenCode, Pi, and portable AGENTS files are supported as interfaces — not the point of the product.
what it does
health-v2 analytics/dashboard stack.what it refuses to pretend
TEST_CANDIDATE cards, not orders.common commands
health enroll --alias alex --birth-year 1983 --role adult
health data-wishlist
health dr-visit --profile alex --cadence onboarding
health ingest-note --profile alex --marker ALT --value 76 --unit U/L --category liver --flag high
health result --profile alex --marker mercury
health review --profile alex
health close-gaps --profile alex
health test-battery --profile alex --scope expanded --sources
health consult --profile alex --specialist auto
health plugin-paths
In your local HUB. The website has no backend, accounts, analytics or health-data upload.
Yes, but use aliases, keep raw dumps out of Git, and be mindful of every app/agent with filesystem access.
Because health outputs can affect real decisions. LLM Health forces an explicit own-risk checkpoint before profile-specific HUB work.