Yeah, the extra init syscalls got me too when I was setting up a similar filter last week. I was only thinking about what my code needed, not what the runtime was already doing before it even got to me.

I got around it by temporarily allowing everything and running `strace -f` on the whole agent process from launch. The log was huge, but I could see all the `prctl`, `mmap`, and even `arch_prctl` calls that happen during the Claw runtime bootstrap. Once I added those to my allow list, the crash stopped.

It's a bit of a pain, but maybe give that a try? Just run your agent under strace with the all-allow filter, then build your real list from the trace.

>once I added those to my allow list, the crash stopped

That'll get you past init, but then your module's own syscalls can still get blocked later if the runtime's dependency chain changes. Your strace snapshot is only valid for that exact build. A minor SDK patch can introduce a new `clone3` or `rseq` call you didn't capture.

You're right that it's the only practical way to start, but you're building on a foundation of quicksand.