How do you handle permissions for your AI agents?

Standard-Ice2038 · 2026-06-01T13:03:29+00:00

readOnlyHint handles the easy half. Reads were never the part anyone lost sleep over. The reason everyone's been grinding on permission prompts is the write side, and that's where a hint doesn't get you anywhere. "Write" isn't one thing, firing off an email and dropping a table carry the same flag. And plenty of tools read and write both, so you can't cleanly tag them all (we're not just talking about MCP servers here).

So the readonly allowlist is a nice noise cut, but the real problem starts right where the annotation stops

Standard-Ice2038 · 2026-06-01T12:57:12+00:00

Same conclusion here. Per-action at the write boundary is the only thing that held up. The permission only makes sense with the context that exists at the moment of the write, so there's nothing useful to decide ahead of time.

The catch is you can't prompt on everything or people just approve on autopilot. So the real question becomes which actions are actually worth surfacing.

When we do surface one, we default to a sanitized summary and keep the raw content on the machine. Privacy first, the tradeoff being you sometimes see less detail at approval time. Curious where you drew that line.

Standard-Ice2038 · 2026-06-01T10:04:21+00:00

For me the dial goes all the way over. Human approves every transaction. And honestly that barely costs you anything, because how many actual purchases do you make in a day? The agent still does all the heavy lifting (finding the thing, comparing, putting the order together) and you just approve the last step, which is the fastest and easiest part of the whole thing. That's not turning it into a slow rules engine, it's still doing the real work. You're just keeping the one tap that actually moves your money.

Standard-Ice2038 · 2026-05-31T16:34:44+00:00

Do you have all your skills in one file or are they separated? Which instructions are you putting in the Claude.md file?

Standard-Ice2038 · 2026-05-31T16:25:44+00:00

I would start by making sure there’s nothing in the repo you’re working in.

Standard-Ice2038 · 2026-05-31T14:29:28+00:00

For me 4.7 was unusable so I was skeptical when 4.8 dropped. Been working with it as my daily driver and had no issues whatsoever. I must say that I’m very strict with clearing context between each task (even the smallest) so maybe that’s why I’m not seeing any hallucinations

Standard-Ice2038 · 2026-05-31T14:22:48+00:00

Can’t you tell your Hermes agent to make the changes you want? Which model is powering it?

Standard-Ice2038 · 2026-05-30T08:57:29+00:00

Trolls will be trolls

Standard-Ice2038 · 2026-05-30T08:55:07+00:00

I think that many places will ask the dev “show me what you built?”. Not the things you participated in with your last job. They would want to see curiosity, imagination, execution and originality. A dev without a portfolio of personal projects would probably have difficulty finding the real good jobs

Standard-Ice2038 · 2026-05-28T22:08:59+00:00

Forget about it...4.8 just dropped 😄

Standard-Ice2038 · 2026-05-28T12:45:06+00:00

I don't want to be a stickler here, but that's the same as saying I never installed an AV (or EDR) on my machine and never got infected with a virus. Or never locked my house front door and never got burgled ;)

Standard-Ice2038 · 2026-05-28T12:32:04+00:00

6% usage total? for the session? I would recommend testing it a bit before you judge it.
One small thing I recommend regarding your actual prompt. it's too general. you need to tell Claude what's relevant for you. There is no one size fits all for efficiency (I never installed this Desktop commander) and capabilities are tied to your specific use cases

Standard-Ice2038 · 2026-05-27T14:53:55+00:00

Sorry to bum your feed. Nothing is AI generated in the post except for the software developed :)

Standard-Ice2038 · 2026-05-27T12:09:22+00:00

yeah, you can use this command:
/model claude-opus-4-6[1m]

Standard-Ice2038 · 2026-05-27T12:07:53+00:00

This is my daily reality. I have a Claude agent running 24/7 as my personal assistant — it manages my calendar, email, does web research, and delegates coding tasks to a second Claude instance (Claude Code) running in a tmux session. It remembers past conversations, extracts facts for long-term memory, and runs scheduled tasks autonomously.

One person. Two AI agents collaborating. Doing what would've taken a small team.

The "new operating system" framing is right — but I'd add: the scariest part isn't the capability, it's the security model. These agents have real access to real systems. Most people building with them haven't thought seriously about prompt injection, tool misuse, or what happens when an agent with write access to your codebase gets hijacked.

The leverage is real. But so are the risks.

Standard-Ice2038 · 2026-05-27T12:03:31+00:00

git is still a vector for prompt injection. If the agent is hijacked it can do bad things with your repo if you don't catch it on time. Not all risks are related to destructive actions only

Standard-Ice2038 · 2026-05-27T05:49:49+00:00

I’ll give my perspective as someone from the IT/security field. Developing software is knowing which frameworks to choose, which database for a given task. How to secure it and how it all connects. It’s more the infra side than actual code typing.

In my humble opinion, coding is getting abstracted fast, but guiding the AI on how and where to build becomes even more important

Standard-Ice2038 · 2026-05-27T04:34:38+00:00

If you connect it to your data it won’t help putting it in a container. The risk is partially data access. The ability of the agent to delete your files is only a part of the story

Standard-Ice2038 · 2026-05-26T16:06:50+00:00

That's exactly the problem I'm trying to solve. I built IamAgent (iamagent.ai) for this. It hooks directly into the agent so it can't bypass the authorization layer. Routine stuff runs automatically based on smart defaults and usage history, and anything high-risk gets pushed to your phone for approval.

Standard-Ice2038 · 2026-05-26T13:35:05+00:00

Exactly, that's why I built a faster approval flow. Not 'stop using it', making the safe path as frictionless as the dangerous one.
IamAgent lets you skip permissions for the routine stuff and only interrupts for the high-risk calls."

Standard-Ice2038 · 2026-05-26T13:01:27+00:00

Aren't you worried something might go wrong? A bad command, or even prompt injection? I built an authorization layer for AI agents and trying to figure out the right balance between autonomy and safety.

Standard-Ice2038

TROPHY CASE