Guides

Test the four tools

An acceptance checklist for CLI, MCP, the editor extension, and Chrome.

Use a new dummy note for every lifecycle test. Avoid real credentials and recipients. The checkboxes save progress in this browser only; no test content or result is sent to PrivateNote.

Before you start

0 of 4

Create a test workspace with demo.txt containing harmless, recognizable text.Create passphrase.txt with a dummy passphrase on its first line; do not put the passphrase in the agent conversation.Record the CLI/MCP package versions and both extension versions.Use a separate recipient browser profile. Have a Free account and, if testing gated features, an eligible paid account available.

1. CLI

Basic checks

npx privatenote-cli --help
npx privatenote-cli --expire 15m --output-url-only demo.txt
npx privatenote-cli --expire 15m --output-url-only < demo.txt

0 of 7

Help lists available options. File and stdin modes both reveal exactly the dummy message.After a read-once reveal, a second reveal cannot access the content.Captured stdout without an override refuses to print the link. --output-url-only permits URL output.--json --force-stdout produces structured output. --json with --output-url-only is rejected.Login opens browser approval; whoami reports the signed-in account; logout clears that tool session.--password-file passphrase.txt requires the password on reveal. A wrong password does not disclose content.Invalid expiry is rejected. A Free account cannot create a note exceeding its expiry or read-count limit.

3. VS Code / Cursor

0 of 8

The extension activates. The PrivateNote activity-bar icon and commands are visible.Select dummy text and run Share as PrivateNote. The revealed note matches the selection exactly.Create another note with the sidebar composer and verify its content.The created link is available on the clipboard and includes its #fragment.Set a reveal password. Correct entry reveals the note; incorrect entry does not.Change default expiry and burn settings. A new note starts with the saved defaults.Sign in, check Show Account, and sign out. Repeat selection creation after returning to the editor.Repeat the core selection and composer flows in each editor you intend to support.

4. Chrome

0 of 8

Pin the extension and create a dummy note from the toolbar popup.On a normal webpage, select dummy text and use Create PrivateNote. The popup receives the intended selection.Alt+Shift+P opens the creation flow with the selected text, or the shortcut can be reassigned if another app uses it.Copy link works. Reveal in another profile and confirm read-once behavior.Password-protected creation requires the correct password on reveal.Saved expiry, burn, and theme defaults persist after closing and reopening the popup.Sign in through browser approval, confirm the displayed account, and sign out.The extension handles unavailable selection access on restricted Chrome pages without creating the wrong content.

Across all four tools

0 of 4

Create a short-lived note, leave it unopened until expiry, and confirm that it cannot be revealed afterward.Inspect a dummy-note network request if your test setup allows it: content uploads contain ciphertext, not the recognizable dummy plaintext.Check the recipient URL retains its #fragment and creation does not transmit that key in a request body.A disconnected or failing network shows an actionable error and does not claim success without a valid link.

For a bug report, record the tool version, environment, exact action, expected result, actual result, and a sanitized error. Do not include full sharing links, passphrases, tokens, or real note contents.

Test the four tools

Before you start#

1. CLI#

2. MCP server#

3. VS Code / Cursor#

4. Chrome#

Across all four tools#

Before you start

1. CLI

2. MCP server

3. VS Code / Cursor

4. Chrome

Across all four tools