Better Logger

Better Logger

Modern MacOS Log viewer for iOS developers with MCP support

58 followers

Better Logger is a powerful, modern macOS log viewer built for iOS developers. Stream logs in real time from iOS Simulators, organize them into visual lanes, and integrate with AI-powered tools like Cursor through MCP.
Better Logger gallery image
Better Logger gallery image
Better Logger gallery image
Better Logger gallery image
Better Logger gallery image
Better Logger gallery image
Free Options
Launch Team / Built With
Anima - Vibe Coding for Product Teams
Build websites and apps with AI that understands design.
Promoted

What do you think? …

Nedim
I’ve had this idea in my head for a while. Every time I ran into a difficult memory issue, I wished I had a tool like this. Something that would let me visually inspect each log category lane and see what’s happening in real time. I’ve been using it for a while now and thought other iOS developers might enjoy it just as much. Adding MCP capabilities has completely changed the way I debug; asking Cursor to look at specific logs without having to copy and paste has been a game-changer.
Masum Parvej

@nedimf how do you see it scaling for larger teams, maybe with shared log views?

Nedim

@masump yes, there is already export option which allows you to compose a issue like report to share across Github Issues or Slack channel, you can choose which lanes (categories) you want to be affected.

André J
💡 Bright idea

How does it work with streaming? isnt MCP mostly turn by turn? Prompt -> response. Can MCP listen passively?

Nedim

@conduit_design so, idea is that it's a tool, that Cursor or other IDEs can use, to basically query app logs, based on lane (category) or some other filter that LLM in that time calls. I hope this answers your question, I hope you try out tool and let me know your feedback, if you are interested I'll send you 100% off code to try out.

André J

Right. yeah. Okay. Now I understand. yes. I use this as well. Actually. I really need this. But for any log really. What I do today. Is that I store log sessions from tests. Can be iOS or Javascript projects etc. And I store a new log file for every run. So that they dont get too big (to avoid using up context tokens). Then I have a rule set that the AI agent uses to read the logs. So the agent will use terminal with some filtering, based on what its looking for. it works. but leaves so much to be desired. I think the ultimate solution may be to store logs in sqllite and make a api that the agent can then more easily use rather than terminal with filtering strategies which works, but is a hit and miss sometimes. But yeah. Log reading is the key to AI coding. Esp when your implementing features that requires a lot of back and forth testing to get right.

Nedim

@conduit_design yes, send me email at nedim.apps at gmail com, I'll get you key for 100% off, and let me know your feedback about this. One way to fight token consumption is to tell AI to look at last 10 logs, etc, and it really helps when lanes are used, because you can pin point specific problem, without inflating token size.

Nedim

If anyone wants to try this out with hybrid tooling, like Flutter, RN or something similar let me know so I can provided you with 100% off. I really want to learn if tool is accessible enough for this type of tooling system.