Connect Context Nest in one guided step — PromptOwl cloud, your company’s server, or notes only on this computer — and choose how much it runs on its own. Safe to re-run; it never replaces an existing setup.
Walk the user from "plugin installed" to "nest connected and the agent knows how to use it". The user may know nothing about Context Nest — do the work, ask only the choices below, and never hand them a command to copy unless a step says so.
Server: the URL in $ARGUMENTS if one was given, else the one chosen in Step 2 (https://nest.promptowl.ai for PromptOwl cloud). Call it <server> below. Accept it only if it is a plain https://host[:port][/path] URL (http:// only for localhost/127.0.0.1) with no spaces, quotes or shell characters; otherwise say why and stop. Always pass it to commands in double quotes.
Say this once, before connecting anything: connecting uploads nothing. Notes in a local vault stay on this machine unless the user runs ctx push; only what is written to a hosted nest lives on that server.
Check all three, quietly:
nest_index, context_search)?ctx --version. Not found → npx -y @promptowl/contextnest-cli --version. Use whichever works as <ctx> from here on; neither → no CLI. A version below 3.2.0 has no login command: treat it as too old for Step 3b and offer npm i -g @promptowl/contextnest-cli@latest, or use npx -y @promptowl/contextnest-cli@latest as <ctx> instead.<ctx> vault list --json, and <ctx> login --list when the CLI has login.An MCP server or claude.ai connector that already points at <server> but needs sign-in counts as the cloud path half done: <server> is that connector's server; ask Step 2 without its first question, then go to Step 3a item 2 for that server instead of adding another.
Already connected (MCP tools present, or at least one registered vault): if $ARGUMENTS names cloud or local, treat it as Connect another nest and go on without asking. Otherwise show a short summary (what is connected, which vault is default/pinned) and ask with AskUserQuestion: Done · Connect another nest (continue at Step 2) · Pin a vault (hand over to /contextnest:config vault). Never remove, replace, or re-default anything that already exists.
Ask all three in a single AskUserQuestion call; leave out any question $ARGUMENTS already answers (a URL answers the first). With no usable CLI and no plan to install one, also leave out the second — its settings drive hooks that need ctx (Step 3d writes them off).
https://nest.promptowl.ai · Only on this computer → a private local vault, nothing connects to a server. A company server is typed into "Other" as its URL.retrieval_mode: search, capture_mode: explicit./contextnest:recall and /contextnest:capture. → off / off.search / propose.ctx sign-in or new local vault is still registered for the whole user account — say so when it applies.Then pick the path: Only on this computer → Step 3c. A server and a CLI of 3.2.0 or later → Step 3b. A server and no usable CLI → Step 3a. cloud or local in $ARGUMENTS forces 3a or 3b.
contextnest entry to their MCP config, then run claude mcp add --transport http --scope <scope> contextnest "<server>/mcp" — <scope> is user for all projects, local for this project only. If a server named contextnest already exists, ask before using another name — never remove the existing one./mcp, pick contextnest (or the existing server/connector found in Step 1), choose Authenticate, and approve in the browser. If contextnest does not show in /mcp, restart Claude Code first./mcp offers no Authenticate or the sign-in fails, the server has browser sign-in turned off — remove the contextnest entry you added (claude mcp remove contextnest --scope <scope>) and offer the local CLI path instead.npm i -g @promptowl/contextnest-cli (needs Node ≥ 20; installs to the user's npm prefix, no admin rights). If it fails, offer the cloud path instead of debugging the machine.<ctx> login "<server>" --as promptowl — add --set-default only when vault list showed no default. If promptowl is taken, pick another alias; never pass --force. The command opens the browser and waits for approval: run it with a long timeout (10 min) and tell the user to approve the page that opened. On a server without browser login it asks for a pasted key — tell the user to create one in the server's web UI (Connect) and run ! <ctx> login "<server>" --as promptowl --key-stdin themselves, so the key never passes through you.<ctx> vault list --json: each nest shows as promptowl/<nest>.AskUserQuestion whether to pin one (each nest as an option, labelled with its description, plus Don't pin — choose per question). Pinning writes vault the way /contextnest:config does. Then go to Step 3d.Needs the CLI (install as in Step 3b item 1; if that fails, say a local vault needs it and offer PromptOwl cloud). Create ~/contextnest (or another folder the user names; if it already exists and is not empty, ask for another — never init over an existing vault), and inside it run <ctx> init --name "My notes" — add --set-default only when vault list showed no default — and use the alias it printed as <alias> from here on. Nothing leaves the machine. If the second question was skipped, apply Light in Step 3d. Then go to Step 3d.
Write the Step 2 choice as retrieval_mode and capture_mode, the way /contextnest:config does (its Step 3 merge rules; --global for all projects). With no CLI on this machine, write off / off whatever was chosen and say why: the hooks need ctx, so you use the nest's MCP tools directly instead. On the cloud path with a CLI present, say plainly that the hooks cover only the vaults ctx knows; this nest is reached through its MCP tools. Then go to Step 4.
Do not write usage rules from memory — the nest is the source of truth, and it changes without a plugin release.
nest_index, then context_overview. Read any guide or onboarding node they surface and follow it.<ctx> --vault <alias> list --limit 20 and <ctx> --vault <alias> structure --json, where <alias> is the vault just connected (promptowl, or the alias ctx init printed).Then show the user it works with one real read: search for something the nest is about and cite one hit. Finish with three lines at most — what is connected, what the agent now does on its own (per the usage choice), and how to change it (/contextnest:config). Ask before writing a test note; never write one unasked.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.