Creation
Local input stays out of model-facing tools.
Claude Code always opens the browser handoff for creation. Its skill explicitly prohibits reading a local file or note merely to create a link.
NexFade for Claude Code
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
The plugin package validates locally; community submission follows the beta gate.
The NexFade-owned beta marketplace is prepared, but no public-install claim is made until claude-community review completes.
Management
Minimal operational metadata only.
The remote MCP tools support list, status, and explicitly confirmed revoke operations without exposing encrypted content or link fragments.
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 Claude Code, 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