Back to projects

Projects

Infra Sentinel

macOSobservabilityai-usagenetworklocal-system

Infra Sentinel is a macOS desktop monitor for network traffic, local AI-client usage, host resources, remote hosts, and service status. Each source keeps its own units and accounting method.

Infra Sentinel overview
The screenshot uses anonymous demonstration data and contains no real hosts, addresses, accounts, paths, or project content.

Supported sources

NetworkConnections, domains, and proxy routes from a Mihomo or Clash Meta-compatible core, plus optional Linux interface counters through an SSH Host alias.
AI usageCodex, OpenCode, Antigravity, and connected Infer Runtime instances. Each source retains its own accounting boundary.
Host resourcesCPU, memory pressure, swap, disk throughput, IOPS, capacity, thermal pressure, and best-effort per-app disk I/O attribution.
Service statusPublic status feeds for selected AI services and local PCP, Infer Runtime, Dev Mesh Observer, and other compatible services discovered through Infra Protocol.

AI usage accounting

Codex usage comes from per-request increments in local rollout JSONL, with fork replay and duplicate records removed. The persistent ledger stores aggregate usage, parser state, and deduplication markers, but no task content.

Charts show raw Tokens observed on this machine, not Codex account quota or billing. API reference value is calculated from model-specific input, cached-input, cache-write, and output prices.

Infra Sentinel AI usage view
Hourly Token buckets and local API reference value using anonymous demonstration data.

Data and boundaries

Collection is read-only. Infra Sentinel does not capture packets or retain prompts, responses, project files, or credentials, and it does not change proxy or remote-service configuration. Remote hosts are identified by existing SSH aliases; keys, passwords, and HostName values are not copied.

The current desktop package supports macOS 13+, uses ad-hoc signing, and is not notarized by Apple. Collection, storage, and analysis stay local by default. Stored state may include aggregate domains, model names, Xray client labels, and user-defined display names.

On this page