Show HN: Geiger – See every AI agent on your machine and what it can touch
1–10 of 28 posts
Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#2Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#3If 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.
Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#4Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#5> 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…
Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#6Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#7> 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…
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?
Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#8> 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…
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?
Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#9Re: Show HN: Geiger – See every AI agent on your machine and what it can touch
#10Earlier quoted context omitted.
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?
I don't think you're just lucky, depends heavily on the model + reasoning effort. I've never had any of the GPT models do anything of the sorts when using the higher reasoning efforts, but sometimes when I play around with local models, even "big" ones (as big as you can fit with 96GB VRAM) sometimes forgets/misses to define $ID then do "rm -rf data/$ID" for example, deleting more than they intended.
Right, that's kinda the same failure mode as delete from table something and hitting enter before you write the condition or writing the wrong one. If you reach the point where you opened the terminal to do it this way you already lost.