What Mesh does not do

Key boundaries, scope limits, and operational guarantees of Mesh.

Mesh is an outbound egress gateway designed to catch secrets and personal data before they leave your machine. It has specific boundaries:

• Mesh does not inspect provider responses. Provider responses are relayed to the client unmodified and are not inspected. Mesh is an egress control on what you send, not an inbound filter on what you receive.
• Mesh does not stop an AI agent from reading files on your computer. It cannot make unrestricted filesystem access inherently safe. Operating-system sandboxing and least privilege come first.
• Mesh scans only traffic from connected tools. In version 0.0.7, that means Claude Code and Codex. Other AI apps or terminal tools are not routed.
• A connected tool is not the same as a protected one. Restart the tool after connecting. smesh client list shows “protected” only after recent traffic through Mesh, and “not verified” is a reason to check, not proof of protection.
• Name detection is statistical and incomplete. Do not use Mesh as a de-identification control.
• Mesh fails closed. If a request cannot be scanned, it is stopped rather than sent unchecked.
• Do not bypass checks. Never switch a tool to a direct provider address just to make a failing check pass.