claude — 80×24
> /nessie what did I decide about pricing last month?
Using the nessie skill…
nessie grep "pricing decisions" --type context
nessie grep "pricing" --type transcript
Based on your "April investor brief" (synthesized from 14 conversations across ChatGPT,
Claude, Gemini, and Perplexity):
• Rejected per-seat licensing — test showed a churn signal
• Flat pricing at $20/month is the psychological anchor
• Annual discount language rolls out next week
source: 3 contexts, 9 threads.
Once setup is complete, type /nessie in any Claude Code or Codex session to access your Nessie library. The same agents you already use, now aware of everything you've already thought.
What Claude Code and Codex can do with Nessie:
- Start with a briefing — auto-inject a compact Nessie check-in at the beginning of each new session
- Access and build your profile — read and write to your profile
- Search everything — search across your contexts, synced transcripts, Obsidian notes, profile, or all at once
- Read your contexts — pull in the full content of any context
- Read your transcripts — access your synced AI conversations from ChatGPT, Claude, Gemini, Grok, Manus, Perplexity, Claude Code, Claude Cowork, Codex, OpenCode, Cursor, Pi, Antigravity, Hermes, and OpenClaw
- Resume agent sessions — paste a transcript or source ID into a new agent session so it can read the beginning and recent tail before continuing
- Use shared knowledge — discover shared source roots, individual sessions, and collaborative folders, then search them with owner and team provenance
- Create contexts — research and read your conversation history, synthesize the result, and save it with source attribution
- Create and edit contexts — write new contexts; shared or collaboration-enrolled contexts update the same synchronized document that collaborators have open in Nessie, while private never-enrolled contexts can retain the legacy local write path
- Organize your library — create, rename, move, and delete contexts and folders, including caller-owned work inside Editor shared folders
Real examples — things people actually use this for:
/nessie what's the current state of the database migration?— pulls context from conversations across Claude, ChatGPT, and Claude Code to give you a synthesized status update with who said what and what's still open/nessie get me up to speed on Sarah before my 2pm— searches your conversation history for every mention of a person, surfaces what you've discussed, what they care about, and what you last agreed on/nessie what pricing decisions have we made in the last month?— finds every pricing discussion across all your AI tools and reconstructs the decision trail: what you considered, what you rejected, and where you landed/nessie write a memo on our competitive landscape based on my recent research— reads your transcripts where you analyzed competitors, synthesizes a structured context, and saves it to your library with source attribution/nessie create a context summarizing my last week of Claude Code sessions— reads the relevant sessions, synthesizes what you shipped, discussed, and decided, and saves the result with source attribution/nessie resume this Codex session:— reads the beginning and recent tail, writes a takeover brief, and continues from the latest state/nessie search Tiger's shared Codex sessions for the release blocker— uses team-shared sources to find relevant teammate sessions without requiring them to export or paste anything