# Guides for sharing secrets and private notes

> How to pass passwords, API keys, and private notes to people and AI agents, how the tools compare, and how Evergist works.

Source: https://evergist.com/blog/

Every link below is the markdown version of a post.

## For AI agents and automation

- [Do link previews burn one-time secret links?](https://evergist.com/blog/do-link-previews-burn-one-time-links.md) (2026-09-30): Yes, on services that reveal a secret on page load. What Slack and Safe Links fetch, and why link previews don't burn one-time links on Evergist.
- [How to give Claude Code an API key without pasting it in chat](https://evergist.com/blog/give-claude-code-an-api-key-safely.md) (2026-09-30): Put the key in a one-view encrypted note and let the agent write it to a file. How to give Claude Code an API key without pasting it. Codex and Cursor too.
- [An MCP server for sharing secrets: local, free, no account](https://evergist.com/blog/mcp-server-for-sharing-secrets.md) (2026-09-30): Run npx -y evergist mcp for a local MCP server for sharing secrets as one-time links. No account, no API key. Config for Claude Code, Codex, and Cursor.
- [One-time links vs a vault: credential sharing for AI agents](https://evergist.com/blog/one-time-links-vs-vault-for-ai-agents.md) (2026-09-30): Use a one-time encrypted link to deliver a credential once and a vault to store and rotate it. How credential sharing for AI agents splits into two jobs.
- [Accidentally pasted an API key into ChatGPT or Claude? Rotate it, then fix the habit](https://evergist.com/blog/pasted-api-key-into-chatgpt.md) (2026-09-30): Rotate the key first, then check for use and delete the chat. What to do after you accidentally pasted an API key into ChatGPT, Claude, or a coding agent.
- [A self-destructing note API with no plaintext endpoint](https://evergist.com/blog/self-destructing-note-api.md) (2026-09-30): Your code encrypts and the server stores only ciphertext. Why this self-destructing note API has no plaintext endpoint, a Web Crypto example, and shortcuts.
- [Send a secret from GitHub Actions to a person with a one-time link](https://evergist.com/blog/send-a-secret-from-ci-to-a-person.md) (2026-09-30): A working workflow step that hands a generated password to one person and keeps it out of the job log. Send a secret from GitHub Actions as a one-time link.
- [Share a secret from the command line with one command](https://evergist.com/blog/share-secrets-from-the-terminal.md) (2026-09-30): Pipe a file, the clipboard, or a generated password into npx and get an encrypted one-time link. Share a secret from the command line, nothing to install.
- [How AI agents can share secrets without leaking them into transcripts](https://evergist.com/blog/how-ai-agents-share-secrets.md) (2026-09-29): How AI agents share secrets with people and other agents without leaking them into transcripts: three handoff patterns, four ways in, and rules to copy.

## Guides

- [How to send a private note that deletes itself after reading](https://evergist.com/blog/how-to-send-a-private-note.md) (2026-09-30): Paste the text, keep the view limit at 1, pick an expiry, and send the link. How to send a private note step by step, what the recipient sees, and the limits.
- [How to share a .env file with a teammate](https://evergist.com/blog/share-env-file-with-a-teammate.md) (2026-09-30): One command turns the file into an encrypted one-time link and another saves it. How to share a .env file with your team, and when to use a secrets manager.
- [How to share sensitive information securely with a client or contractor](https://evergist.com/blog/share-sensitive-information-securely.md) (2026-09-30): Scope the credential, send it as a one-time encrypted link, and rotate at handover. How to share sensitive information securely with a client or contractor.
- [Why the encryption key sits in the URL fragment, and where it leaks](https://evergist.com/blog/url-fragment-encryption-key-explained.md) (2026-09-30): How a URL fragment encryption key works: browsers never send the part after # to the server. Where fragment keys still leak, and what limits the damage.
- [How to share a password or API key securely (without leaving it in chat)](https://evergist.com/blog/how-to-share-a-password-securely.md) (2026-09-29): How to share a password securely: four methods and when each fits, what NIST and password manager docs say, a checklist, and answers on email and chat.

## Comparisons

- [Is Privnote safe? What its policy says and what you can't verify](https://evergist.com/blog/is-privnote-safe.md) (2026-09-30): Privnote's policy says the key stays in the link and staff can't read notes. Is Privnote safe? What's verifiable, what isn't, and how to avoid clone sites.
- [A Onetime Secret alternative that encrypts before upload](https://evergist.com/blog/onetime-secret-alternative.md) (2026-09-30): Onetime Secret encrypts on its server, Evergist on your device. A Onetime Secret alternative compared row by row, and where Onetime Secret is the better pick.
- [Privnote alternatives compared: 8 private note tools checked (2026)](https://evergist.com/blog/private-note-sharing-compared.md) (2026-09-29): Privnote alternatives compared: we checked eight self-destructing note tools, ours included, for browser encryption, who can read notes, limits, and APIs.

## Evergist

- [Why we built Evergist](https://evergist.com/blog/why-we-built-evergist.md) (2026-09-30): We wanted a free way for AI agents and scripts to pass secret notes safely, with no browser to drive and no third party to trust. Here's what we built.
- [Introducing Evergist: encrypted notes for people and AI agents](https://evergist.com/blog/introducing-evergist.md) (2026-09-29): How Evergist is built: AES-256-GCM in the browser, the key in the URL fragment, one Cloudflare Worker with a Durable Object per note, and what we left out.

## Next steps

- Agent instructions, with every command: https://evergist.com/SKILL.md
- MCP server, CLI, and REST API setup: https://evergist.com/agents.md
- Short index of the whole site: https://evergist.com/llms.txt
