LOBELobe is a local HTTP profiler. Route your dev traffic through its proxy and see exactly where each request spends its time — get answers, not guesswork.
brew install kpwithcode/lobe/lobelobe capture <url>Features
Lobe is for finding the slow query before you ship — not monitoring production after. No APM agent, no SaaS onboarding: a proxy on your machine and answers in your terminal.
Local proxy captures DNS, TCP, TLS, TTFB, and download for every request. Emit the standard Server-Timing header and the TTFB bar splits into your app's own segments — db, render, cache. No agent, any language.
Route-scoped percentiles and a latency heatmap surface bimodal patterns — cache hit vs. miss, fast path vs. slow path.
Built-in loopback / LAN / remote baselines from Systems Performance. Cold and warm connections judged separately, so pooled requests aren't mistaken for impossibly fast ones.
lobe explain walks your session resource by resource and returns a ranked triage — top hypotheses about where time is going and why. Pair it with the shipped skill for hands-off use in Claude Code or Cursor.
How it works
$ lobe capture http://localhost:3000Spins up a local proxy on 127.0.0.1:7878 by default (configurable via --listen). Route your app or mobile client through it — every request gets its DNS, TCP, TLS, TTFB, and download phase recorded.
$ open http://127.0.0.1:7878 # the proxy (or your --listen port)Use your app through the proxy and every request streams into the TUI live — phase breakdown and baseline anomalies, nothing leaving your machine. Press e to export the session, or sync it to the dashboard for percentiles, the heatmap, and bimodal detection.
$ lobe explain session.jsonWalks your session resource by resource — CPU, DB pool, network, upstream — and returns a ranked markdown report of what's likely slowing you down. Bring your own Anthropic key, or use the bundled Claude Code / Cursor skill.
The mental model
Every request flows through the same subsystems — each named after a region of the brain that does the equivalent job. You’ll see them in your terminal as things happen.
The observation layer
Local proxy on 127.0.0.1:7878 by default (configurable via --listen). Every request in, every phase timed, nothing lost. No agents to install.
The threshold guard
Grounded baselines fire the moment a request breaks what should be possible. Flagged in real time, not after the fact.
The exporter
Sessions become portable JSON. Reports become portable markdown. Everything you diagnose is something you can share.
The analyzer
lobe explain walks each anomalous request through a systematic triage. Ranked by impact.
The memory
Sessions sync to your dashboard. Route trends chart every route across days and flag the session where it started drifting.
Install
The Lobe CLI is a single Rust binary. Install it via Homebrew on macOS or Linux, or with Cargo on any platform with a Rust toolchain. No runtimes, no daemons, no config file.
lobe login syncs sessions to your dashboard on Probrew install kpwithcode/lobe/lobelobe capture <url>Grounded baselines
Rule-of-thumb budgets for a healthy service on each network class — loopback, LAN, and remote. Anything slower has a findable reason, and Lobe helps you find it.
Pricing
The full CLI and local web app are free, no account required. Bring your own Anthropic key on Free and Pro — no managed AI cost to you. Pro adds cloud persistence; Team adds the PR bot and CI checks.
Full CLI + web app, no account required.
Your sessions, kept — synced across devices, compared across days.
One flat price. Up to 15 members.
Teams past 15 — SSO, audit, private region.
FAQ
HTTPS without a certificate, whether it works with your stack, how it splits TTFB, its own proxy overhead, and what lobe explain sends — answered plainly.
Talk to us
Lobe is early — tell us what’s breaking, what’s missing, and what you’d pay for next. We read every note.
getlobedev@gmail.com