For one person, to start

Your own governed context, for every AI you use.

You've taught Claude, ChatGPT and Cursor the same things three times. Keep what you know in one place your AI tools read, and that stays yours when you switch models. When your team needs it too, it's already built.
In their words

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.”
Your team's shared brain

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.

Get started

Three steps to a working start.

  1. 1

    Start a personal nest

    Download the free desktop app, or create one with a single command.

    Terminal
    $ npx @promptowl/contextnest-cli init --starter personal
    Download ContextNest free →
  2. 2

    Add what you keep re-explaining

    Your projects, how you like things done, your best prompts. Plain files you can read and keep.

    See plans →
  3. 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/contextnest
    Then
    $ /plugin install contextnest
Map how it can help

Ask your agent what it could do for your work.

Paste this into Claude Code once it's connected to your nest. The agent proves it can read your knowledge, then drafts an opportunity map for you to approve.
Claude Code · a fictional support team's nest
Example
  1. 1. Prove it
  2. 2. Get oriented
  3. 3. Map it
  4. 4. Save as a draft
The prompt
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.
One shared brain

Every team adds its own area.

Start with one team. The next team starts from what's already approved.

Start with your own work. Free.

Connect the AI tools you already use, and approve what they're allowed to rely on.