brian_r_hall

6 ms·

1.
by brian_r_hall 4mo ago
I think it's really scary how agents are hallucinating/doing bad actions, then proceeding to gaslight you about how nothing went wrong. Then you tell the agent that it deleted your whole company database, it says something like &q
2.
by brian_r_hall 4mo ago
For teaching beginners, I’d keep it “boring” at first: VSCode or terminal + Claude Code / Codex on a normal paid plan. The fancy multi-agent / worktree setups are useful later, but I’d start with a really small loop so they unders
3.
Agent guardrails are mostly theater(github.com)
3 points by brian_r_hall 5mo ago|0 comments
4.
by brian_r_hall 6mo ago
Do you have any favorite products on indiehustles?
5.
by brian_r_hall 7mo ago
The frustrating part is watching all the careful thinking about reliability and failure modes get thrown out the window the second something new gets hyped. It's not even that people disagree with the principles, they just stop applyin
6.
by brian_r_hall 7mo ago
The permission scope debate always ends up in the same place. Lock it down too much and it's useless, loosen it up and you're back to square one. And the boundary keeps moving as the agent gets more capable anyway. What nobody&#x2
7.
by brian_r_hall 7mo ago
Context and governance end up being the same surface area approached from different ends. You're trimming what the agent sees, we've been working on what it's allowed to do once it sees it. Curious if compression ever shifts
8.
by brian_r_hall 7mo ago
The deny list problem is real but I think the harder issue is that context matters so much. Deleting a temp file and deleting a config file look the same to a classifier. We've been approaching it from the policy side, define what the
9.
Show HN: Faramesh – open-source runtime enforcement for AI agents(faramesh.dev)
1 points by brian_r_hall 7mo ago|0 comments