ctx-pad

name	ctx-pad
description	Manage encrypted scratchpad. Use for short, sensitive one-liners that travel with the project.
allowed-tools	Bash(ctx:*)

Manage the encrypted scratchpad via ctx pad commands using natural language. Translate what the user says into the right command.

When to Use

• User wants to jot down a quick note, reminder, or sensitive value
• User asks to see, add, remove, edit, or reorder scratchpad entries
• User mentions "scratchpad", "pad", "notes", or "sticky notes"
• User says "jot down", "remember this", "note to self"

When NOT to Use

• For structured tasks (use ctx task add instead)
• For architectural decisions (use ctx decision add instead)
• For lessons learned (use ctx learning add instead)

Command Mapping

User intent	Command
"show my scratchpad" / "what's on my pad"	ctx pad
"show me entry 3" / "what's in entry 3"	ctx pad show 3
"add a note: check DNS" / "jot down: check DNS"	ctx pad add "check DNS"
"delete the third one" / "remove entry 3"	ctx pad rm 3
"change entry 2 to ..." / "replace entry 2 with ..."	ctx pad edit 2 "new text"
"append '-- important' to entry 3" / "add to entry 3: ..."	ctx pad edit 3 --append "-- important"
"prepend 'URGENT:' to entry 1"	ctx pad edit 1 --prepend "URGENT:"
"move entry 4 to the top" / "prioritize entry 4"	ctx pad mv 4 1
"move entry 1 to the bottom"	ctx pad mv 1 N (where N = last position)
"import my notes from notes.txt"	ctx pad import notes.txt
"import from stdin" / pipe into pad	cmd | ctx pad import -
"export all blobs" / "extract blobs to DIR"	ctx pad export [DIR]
"export blobs, overwrite existing"	ctx pad export --force [DIR]
"merge entries from another pad"	ctx pad merge FILE...
"merge with a different key"	ctx pad merge --key /path/to/key FILE
"show entries tagged later" / "filter by #later"	ctx pad --tag later
"show everything except #later"	ctx pad --tag ~later
"what tags do I have" / "list my tags"	ctx pad tags
"tag entry 5 as urgent"	ctx pad edit 5 --tag urgent
"undo" / "I deleted the wrong thing" / "bring it back"	ctx pad undo

Execution

List entries:

ctx pad

Show a single entry (raw text, pipe-friendly):

ctx pad show 3

Add an entry:

ctx pad add "remember to check DNS config on staging"

Remove an entry:

ctx pad rm 2

Replace an entry:

ctx pad edit 1 "updated note text"

Append to an entry:

ctx pad edit 3 --append " - this is important"

Prepend to an entry:

ctx pad edit 1 --prepend "URGENT: "

Move an entry:

ctx pad mv 3 1    # move entry 3 to position 1

Compose entries (pipe show into edit):

ctx pad edit 1 --append "$(ctx pad show 3)"

Import lines from a file:

ctx pad import notes.txt

Import from stdin:

grep TODO *.go | ctx pad import -

Export blobs to a directory:

ctx pad export ./ideas
ctx pad export --dry-run        # preview without writing
ctx pad export --force ./backup # overwrite existing files

Merge entries from another scratchpad:

ctx pad merge worktree/.context/scratchpad.enc
ctx pad merge --key /path/to/other.key foreign.enc
ctx pad merge --dry-run pad-a.enc pad-b.md

Filter by tag:

ctx pad --tag later             # entries with #later
ctx pad --tag ~later          # entries WITHOUT #later
ctx pad --tag later --tag ci    # entries with both (AND)

List all tags:

ctx pad tags
ctx pad tags --json

Tag an entry:

ctx pad edit 5 --tag urgent
ctx pad edit 5 --append "checked" --tag done   # combine with other ops

Undo the last destructive change:

ctx pad undo

Every destructive ctx pad op (add, edit, mv, rm, merge, normalize, resolve, tag) writes a snapshot of the prior pad to .context/scratchpad.history/ before overwriting. ctx pad undo restores the most recent snapshot. Running undo twice in a row is a redo (the first undo itself snapshots before promoting the older state). Empty history is not an error: prints "No pad history to restore." and exits 0.

Interpreting User Intent

When the user's intent is ambiguous:

• "update entry 2" with new text → replace (full rewrite)
• "add X to entry 2" → append (partial update)
• "put X before entry 2's text" → prepend
• "prioritize" / "bump up" / "move to top" → mv N 1
• "deprioritize" / "move to bottom" → mv N last

When the user says "add": check context:

• "add a note" / "add to my pad" → ctx pad add (new entry)
• "add to entry 3" / "add this to the third one" → ctx pad edit 3 --append (modify existing)

Important Notes

• Keep the encryption key path (~/.ctx/.ctx.key) internal to ctx pad commands: exposing it grants full decryption access to all pad entries
• Always use ctx pad to access entries: reading scratchpad.enc directly yields unreadable ciphertext
• If the user gets a "no key" error, tell them to obtain the key file from a teammate
• Entries are one-liners; do not add multi-line content
• After modifying, show the updated scratchpad so the user can verify the change