Show HN: Stroq – a local audit of what your coding agent did and why(github.com)
30 pointsby agybay_074 hours ago3 comments
  • maven2921 minutes ago
    You could cover a lot more adversarial scenarios with an ebpf backend. It needs linux, but with all the patches going around, you should be doing all your dev in a VM anyway. https://eunomia.dev/agentsight/
  • agybay_073 hours ago
    I've built project that helps to protect your computer from dangerous commands that your ai agent might execute. Have you noticed how often dont even check what our agents are actually running? Thats why I created Stroq. Try it locally npx @stroq/cli
    • embedding-shapean hour ago
      > helps to protect your computer from dangerous commands that your ai agent might execute

      How does "a local audit of what your coding agent did and why" help prevent dangerous commands? Sounds like your solution comes too late, innit? Sure, I can see that at 16:48 the agent ran "rm -rf --no-preserve-root" but if it already executed it on my personal computer, isn't it too late then?

      Personally, I think this solves the wrong problem. If you're one stray "rm" away from letting the agent delete stuff on your personal computer, you're running the agent harness the wrong way. At least give it its own user, ideally limit what paths/network it can use, but don't rely on "auditing" to prevent dangerous commands, it'll bite you in the future.

      • arnarbian hour ago
        You are correct, but it's generally very hard to come up with good access control policies up front. Also, as you grant more access the system tends to become over-permissioned over time, and often you don't really find out until so wrong that it hurts. The ability to audit is necessary to maintain good policies. It allows you to discover gaps in your policy even when things didn't break terribly.
      • agybay_07an hour ago
        You’re right the command from my comment only generates a report and doesn’t actually prevent anything. stroq init sets up hooks that prompt for confirmation before a dangerous command is executed—but that’s a filter, not a sandbox
      • agybay_07an hour ago
        [flagged]
  • hmokiguess3 hours ago
    feature suggestion:

    background daemon that continuously scans and alerts in a menubar app when a positive match is found

    clicking the menubar app shows the offending entry, clicking the entry lets you redact, delete, repair, mark as false positive, etc.