Your own governed context, for every AI you use.
What you say when AI starts to drift.
Each of these has the same cause: the knowledge your AI needs has no governed home that every agent reads from. Find your problem →
- “I re-explain my work at the start of every session.”
- “Switching to a better model means teaching it everything again.”
- “My best prompts are scattered across three apps.”
- “I want my team to use what I've set up, without copying it.”
What goes in, and the agents that run on it.
What goes in
- How you work and what you're working on
- Your best prompts and checklists
- Notes, decisions and reference material
- Anything you'd hand a new teammate
Each area gets an owner who approves changes, so agents read the version your team signed off on.
Daily brief
Starts your day from your notes and priorities.
Never sees: Anything you haven't put in the nest.
Writing partner
Drafts in your voice from your own examples.
Never sees: Other people's private notes.
Three steps to a working start.
- 1
Start a personal nest
Download the free desktop app, or create one with a single command.
Download ContextNest free →Terminal$ npx @promptowl/contextnest-cli init --starter personal - 2See plans →
Add what you keep re-explaining
Your projects, how you like things done, your best prompts. Plain files you can read and keep.
- 3
Connect your agent and ask it to map how it can help
In Claude Code, add the ContextNest plugin (or use the Connect button in a hosted nest), then paste the prompt below. It reads your nest, proves it, and drafts an opportunity map for you to approve.
In Claude Code$ /plugin marketplace add promptowl/contextnestThen$ /plugin install contextnest
Ask your agent what it could do for your work.
- 1. Prove it
- 2. Get oriented
- 3. Map it
- 4. Save as a draft
You're connected to my ContextNest nest. Before anything else, prove it: search the nest, open two or three documents, and tell me their titles and one line from each. If you can't read real documents, say so and stop. Don't guess what's in the nest. Use search and single-document reads. If one way of reaching the nest fails, try the other tools you have (the ContextNest MCP tools, the ctx command line or the REST API) before you give up. If the nest is empty or nearly empty, ask me three questions first: what my team does, which questions people ask us most, and which documents we'd trust an agent to answer from. Then work from my answers. Then build me an opportunity map: 1. Five things you can do for me today with what's in the nest. For each one, name the documents it relies on. 2. What's missing: the documents or decisions that would let you do three more things, and who on my team probably owns each one. 3. The agents you'd run on this nest: what each one does, and what each one should not be allowed to see. Save the map back to the nest as a draft titled "How AI can help us: opportunity map". Don't publish it or share it anywhere. Ask me before you publish anything.
Every team adds its own area.
Start with your own work. Free.
Connect the AI tools you already use, and approve what they're allowed to rely on.
