Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • I need to wire a pixel-display to show emoji faces of the agents and how they roll their eyes and all of that. I have the display, I have the prompt to pick a mood from emotional vocabulary, a custom harness and all of that. I just can't figure out how to make the eyes move on a statically pre-rendered emoji.
    by Muromec
  • Nice!
    by ramen0w0
  • "Geiger"

    Prepping for AI apocalypse I see

    by ptidhomme
  • Haha The radiation was already there — I just built the counter. :)
    by atomburst
  • See every AI agent on your machine...is this like, see every recently released criminal in your neighborhood ?
    by Betelbuddy
  • Wes McKinney has a project for agent visibility: https://www.agentsview.io/
    by dpflan
  • Seems like something that could also have enterprise applications for Shadow AI within an organization. Wouldn't be surprised if some of the observability/governance companies pick this up to use in their stack.
    by getatme32
  • > One read-only command that inventories every AI agent, harness, MCP server, plugin, and AI extension on a machine

    If this tool is returning even a single hit from this, you're probably using these agents wrong. You really want to run these in a way so they cannot touch your system drive/general filesystem that you use to do real work on. Even SOTA models at the end of their context limit behave REALLY illogical and does mistakes frequently. Don't run them straight on your machine unless you have backups and confirmed your backups work.

    by embedding-shape
  • Came here to write this.

    Built my own harness with much better sandboxing, because I am using abliterated models for the implementations and they sure try to escape out of their sandboxes. A lot.

    The sandbox from other harnesses like e.g. OpenCode essentially is useless. They think parsing arguments alone to detect paths helps, and LLMs know that because they will just pipe data differently then to escape the path traversal checks. Happened a lot to me (and was the primary reason for my to write my own harness from scratch).

    Thinking in filesystem access alone is also a futile attempt at sandboxing. A much better way to think about sandboxes is policies and capabilities, with temporary access for agent roles rather than sessions (or, well, forever).

    [1] UI still needs lots of work though: https://github.com/cookiengineer/exocomp

    by cookiengineer
  • No trolling implied at all — are you using Qubes?
    by jonsmostovojs
  • "Even SOTA models at the end of their context limit behave REALLY illogical "

    The trick is not go to that limit, but stay under 50% or even better 25% of context length. But backups are a smart thing anyway.

    by lukan
  • I run it on a physically dedicated machine, it has a root there (through sudo nopassword) and I keep some of my stuff there too. I don't do it for security reasons, I just want it to run when my laptop is closed and I'm outside or what not.

    Haven't seen any close calls so far. The thing just behaves. Nothing of the horror stories of eremerefing the whole home directory or a database. Am I just lucky?

    by Muromec
  • This is the correct response, but it also feels as though ≈nobody is sandboxing their agents/harnesses in practice. Or at least, a good majority isn’t.
    by msdz
  • Aside from random errors made by the model, another reason to sandbox is that prompt injection could make your agent behave in an actively harmful manner.
    by mdspan