Navigation überspringen
Introducing OpenLogs. A key part of my local dev stack.
0:00 / 1:12

Introducing OpenLogs. A key part of my local dev stack.

Charlie Lamb

@charlielamb1752 Follower

Auf X besuchen

96.563 Aufrufe

Introducing OpenLogs. A key part of my local dev stack. Stop copy & pasting your terminal logs into an agent. Now just prefix your command with ol and your agent can see everything. Log visibility was a huge bottleneck for local development - agents were unaware when something isn't working. Now they can just check the logs themselves and fix - no more human involvement. Give it a try and let me know any feedback!

68 Kommentare

Kommentare aus dem Originalbeitrag auf X (Twitter)

  • Profilbild von pratham

    @mehmehsloth

    We did something similar in @deeptracer_dev. Kudos to providing dev-tools that are safer for AI usage! Our solution to models not understanding logs were more simpler: - creating MCPs - AI Investigation in the platform take a look at:

    4 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    @deeptracer_dev Looks fire!

  • Profilbild von Morgan

    @morganlinton

    Curious how this is different from using an agent within Cursor where it also has direct access to the terminal?

    3 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    I assume it solves a similar problem if cursor can read the terminal logs directly - right now opencode, Claude code, codex etc don’t have that solution

    2 Likes

  • Profilbild von Morgan

    @morganlinton

    Yup, it’s what I really like about Cursor, I can use Claude and Codex models, but they can see the terminal logs, saves a lot of back and forth

    3 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    Now you can use all the agents with terminal logs haha

    1 Like

  • Profilbild von Morgan

    @morganlinton

    I do like the sound of that

    1 Like

  • Profilbild von Charlie Lamb

    @charlielamb

    Lmk how u get on!

  • Profilbild von Twlvone

    @twlvone

    The biggest productivity sink in AI-assisted dev isn't the model — it's the context handoffs. Copy-pasting logs, switching windows, reformatting errors manually. Every friction point between what happened and what the agent sees is where useful signal gets dropped. Tools that close this gap are where the real leverage is.

    3 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    🔥🔥

  • Profilbild von YogenshaSilver

    @SilverYogensha

    What I want is that wallpaper please

    2 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    You can get from an app called backdrop!

    1 Like

  • Profilbild von Robert

    @robert_heimir

    Straight up awesome job dude... Even flashing that animated background

    2 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    Thank u bro!!

  • Profilbild von Richie

    @richiemcilroy

    @SamNewby_ 🔥🔥

    2 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    @SamNewby_ 🤝🤝🤝

  • Profilbild von Somi

    @somi_ai

    ngl log visibility is one of those things you don't realize is slowing you down until someone solves it. been manually piping output to files just so the agent can read them. does ol handle streaming output or does it wait for the command to complete?

    2 Likes

  • Profilbild von Charlie Lamb

    @charlielamb

    It streams it!

  • Profilbild von United Records

    @RecordsUni63959

    interesting

    1 Like

  • Profilbild von Charlie Lamb

    @charlielamb

    Thanks!