Creation
Local input stays out of model-facing tools.
Supported MCP App hosts show a local note field or file picker. Other Codex clients receive the browser handoff and must not read a local file for creation.
NexFade for ChatGPT and Codex
Create and manage encrypted links without putting readable content in tool arguments.
NexFade creates revocable, expiring links for files and notes. Choose an expiration, optionally burn after the first intentional open or require recipient-email verification, then check or revoke links later.
Availability
Public directory submission is pending production beta and review.
A single universal OpenAI plugin package will serve ChatGPT and Codex after OpenAI approval.
Management
Minimal operational metadata only.
Authenticated tools can list owned link IDs, report lifecycle status, and revoke only after explicit confirmation.
Fallback
Browser handoff preserves the boundary.
If the host cannot render the NexFade interface or run local encryption, it opens the NexFade website with nonsensitive defaults only. Content is never copied into a fallback tool call.
Trust boundary
What local encryption does—and does not—mean.
NexFade encrypts content in its interface before ciphertext upload and does not receive the AES key or complete fragment-bearing link. The interface is displayed by ChatGPT and Codex, so that host platform's privacy terms also apply.
Restricted data is not allowed in marketplace integrations.
Do not use the integration for payment-card data, protected health information, government IDs, passwords, API keys, MFA or one-time codes, or other authentication secrets.
Policies and support