Privacy and trust are the product.
WaitLayer is built to measure sponsor delivery without collecting the private work developers do in their terminal. A hard boundary sits between WaitLayer and everything you do — enforced before any data leaves your machine.
Blocked before anything leaves your machine.
A short, fixed allowlist — describes the ad, not the work.
The allowlist is enforced in the client. If a field is not on it, it is never assembled into a payload.
Every field has a reason.
No third-party bundle patching.
WaitLayer uses official integration points, local status-line commands, hooks, and wrappers where available. It does not modify third-party editor bundles to inject sponsor surfaces.
If a message is sponsored, it says so.
- Every sponsor line is clearly labeled
- No hidden endorsements
- No disguised recommendations
- No unlabeled native ads
- No misleading sponsor placement
Platform-safe by default.
WaitLayer does not authenticate to Claude, OpenAI, or other agent providers. It does not proxy model requests, route subscription credentials, patch third-party binaries, or collect terminal output. It uses official local extension points where available and owned terminal runtime surfaces where appropriate.
Surfaces stay under control.
WaitLayer is designed so individual surfaces can be disabled, diagnostic-only, or ads-enabled as platform policies and technical constraints evolve.
The full policy set.
Some payout methods may require identity, tax, sanctions, wallet-risk, or compliance checks. Availability may vary by region.