News for hackers. Stuff that matters.
Re:Launch HN: Alter (YC S25) – Access control for multi-user... by Nishit9 on Saturday October 24, 2026 @03:46AM (#50219074)
Question on the cross-user case, which I don’t think the memory partitioning answer upthread fully covers. Say the agent pulls a deal record under the CEO’s grant and writes a summary into a shared Slack channel. Later a contractor’s session reads that channel and emails the summary somewhere. Every call passes on its own, since the contractor is allowed to send email. Does the policy engine know anything about where an argument came from, like which grant originally fetched it, or only who’s calling and which endpoint? I ask because I’ve been building something that tracks where send destinations first showed up, and it’s noisy. In my testing it also denied sends where the user typed the address themselves, because the same address was in tool output.
Re:Launch HN: Alter (YC S25) – Access control for multi-user... by kdodhia on Wednesday October 28, 2026 @08:29AM (#50272542)
hey Nishit, kevan here. sorry we completely missed your comment and your question

short answer is no, the policy engine doesn't know where an argument came from across calls. each call is judged on its own: which agent, which end user it's acting for (plus the delegation chain), which grant, which operation and the params on the request. so in your example the contractor's send passes if their policy allows it

we put the controls at the two ends instead of following the data through the middle - write side: the CEO's grant posting into a shared channel is its own call, so you can require approval for it or just deny it - send side: we parse sends into recipients, so a contractor can be limited to emailing inside the company domain, or anything external needs a human approval on the exact frozen request

every call is audited with the agent, end user and grant, and calls in the same run share a trace id. your case spans two sessions though, so the thing linking them is the slack message itself, not a trace

your noise point is honestly why we haven't done taint tracking yet, the "user typed the address but it was also in tool output" case is exactly the hard bit. it's a really interesting scenario though, we'll look into whether it makes sense for us to support this kind of thing natively.

Re:Launch HN: Alter (YC S25) – Access control for multi-user... by Nishit9 on Thursday November 05, 2026 @12:11AM (#50375466)
Thanks Kevan, that's really clear, and no worries. Your send-side rule would have caught my example without any taint tracking, since the contractor just can't email outside the domain.

Since that comment I fixed two of the noisy cases in mine (an address that only appeared inside a longer address, and display names). The one where the user typed an address that also shows up in tool output is still open, because the proxy never sees the prompt.

One question back, if you can share it: customers who turn on "anything external needs a human approval on the exact frozen request", do they keep it on after the first few weeks, or does the approval volume push them to a domain rule instead?

Re:Launch HN: Alter (YC S25) – Access control for multi-user... by simfinii on Friday November 06, 2026 @08:54PM (#50400875)
Hey Nishit, Srikar here! Great question.

We've seen approval volumes pile up for some customers, but they've generally chosen to keep HITL in place for sensitive operations.

What's interesting is that, over time, customers get a much better sense of where fine-grained authorization rules are sufficient and where human approval is actually necessary. Initially, they tend to require HITL for more operations than they really need to.

As they see more requests come through, they start replacing some of those approvals with more precise authorization rules. So the scope of HITL naturally gets narrower over time, but it remains in place for the operations that genuinely warrant human oversight.

Hope that answers your question!

Re:Launch HN: Alter (YC S25) – Access control for multi-user... by Nishit9 on Saturday November 07, 2026 @11:40AM (#50405900)
Thanks Srikar, that's useful. The narrowing over time is the part I'd like to understand better. When a customer swaps an approval for a rule, what do they look at to decide it's safe, the approval history for that action (same destination approved every time), or something else like who's asking?