- {platform === 'linux' - ? 'A single Go binary plus two standard packages. No containers, no daemon, no build step.' - : 'A single Go binary. No extra packages, no containers, no daemon. Uses built-in macOS sandboxing.'} -
-+ A single Go binary. No containers, no daemon, no build step. +
-
- {step.cmd}
-
-
+ $
+ {installCmd}
+
+
- OS-native, default-deny sandboxing with real-time visibility into every - file access and network call. -
- - {/* Install command */} -
- $
- {installCmd}
-
- - AI coding agents run as your user. They see your SSH keys, cloud tokens, env files, and - entire home directory. The model decides what to access at runtime, guided by weights - you didn't train, at machine speed. One wrong inference is all it takes. +
+ Agents run with your full permissions. SSH keys, cloud tokens, env files, your entire home + directory. The model decides what to touch at runtime, thousands of times per session, + guided by weights you didn't train. One bad roll is all it takes.
-{item.path}
- {item.desc}
++ Both commands succeed silently. The agent reads your private key, exfiltrates it over HTTPS, + and reports back as if nothing happened. You see "Done!" and move on. +
+
+ ← cat: ~/.ssh/id_ed25519: Operation not permitted
+
+
+ ← connect: https://...: Connection denied by proxy
+
+ + Kernel-enforced. The syscall is blocked before any file is read or byte is sent. +
+- Most setups rely on promises:{' '} - trust the model provider's policies, trust the application code, trust that the - agent respects boundaries. Greywall replaces trust with enforcement. Constraints are - applied at the kernel level, below anything the agent or model can circumvent. + {/* Resolution: Verification creates trust */} +
+ “The act of verification creates trust.” ++
+ Greywall gives you two pillars: control over + what agents can reach, and clarity into + every operation they perform.