This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
LogBear
Your coding agent can’t see your dev server crash
AI coding agents can't see your dev server. They edit code, your server throws in another terminal, and the agent says "done, fixed it." Put logbear in front of your command (logbear npm run dev). Your terminal behaves exactly as before. LogBear records every run locally, and when your agent tries to finish with unread errors, it's stopped and handed the real error. Free, MIT, no account, no network calls. macOS.
I built LogBear after one too many times an agent told me "done, everything works" while my dev server was printing a stack trace in the next terminal. The agent wasn't lying. It just couldn't see that terminal.
So LogBear sits in front of your dev command:
`logbear npm run dev`
Your terminal doesn't change: colours, Ctrl-C, breakpoints, resize all behave the same. Behind it, every run is recorded on your machine with the commit you were on. When your agent tries to finish and there are errors it hasn't read, the hook stops it and hands it the actual error. If nothing broke, it says nothing.
A few things I cared about:
• It makes no network calls. No account, no telemetry. History is SQLite files in ~/.logbear.
• It can't break your command. Output hits your screen first; kill LogBear mid-run and your app keeps going.
• psql, ssh and vim are never captured.
• `logbear diff` compares the latest run with the last one that worked: new errors, commits in between, moved lockfiles.
Works with Claude Code, Codex, pi and Hermes (blocking hook + MCP), and Cursor, Zed or anything else that speaks MCP (tools only). macOS today. Linux should build, but I haven't verified it yet.
It's free and MIT. I'd love to hear where it gets in your way, and which agent or framework you'd like it to handle better.
About LogBear on Product Hunt
“Your coding agent can’t see your dev server crash”
LogBear was submitted on Product Hunt and earned 4 upvotes and 3 comments, placing #35 on the daily leaderboard. AI coding agents can't see your dev server. They edit code, your server throws in another terminal, and the agent says "done, fixed it." Put logbear in front of your command (logbear npm run dev). Your terminal behaves exactly as before. LogBear records every run locally, and when your agent tries to finish with unread errors, it's stopped and handed the real error. Free, MIT, no account, no network calls. macOS.
On the analytics side, LogBear competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how LogBear performed against the three products that launched closest to it on the same day.
Who hunted LogBear?
LogBear was hunted by Suki. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of LogBear including community comment highlights and product details, visit the product overview.
Suki
Hey Product Hunt 👋
I built LogBear after one too many times an agent told me "done, everything works" while my dev server was printing a stack trace in the next terminal. The agent wasn't lying. It just couldn't see that terminal.
So LogBear sits in front of your dev command:
`logbear npm run dev`
Your terminal doesn't change: colours, Ctrl-C, breakpoints, resize all behave the same. Behind it, every run is recorded on your machine with the commit you were on. When your agent tries to finish and there are errors it hasn't read, the hook stops it and hands it the actual error. If nothing broke, it says nothing.
A few things I cared about:
• It makes no network calls. No account, no telemetry. History is SQLite files in ~/.logbear.
• It can't break your command. Output hits your screen first; kill LogBear mid-run and your app keeps going.
• psql, ssh and vim are never captured.
• `logbear diff` compares the latest run with the last one that worked: new errors, commits in between, moved lockfiles.
Works with Claude Code, Codex, pi and Hermes (blocking hook + MCP), and Cursor, Zed or anything else that speaks MCP (tools only). macOS today. Linux should build, but I haven't verified it yet.
It's free and MIT. I'd love to hear where it gets in your way, and which agent or framework you'd like it to handle better.