# Install OpenContext with your agent Use this prompt with a local agent that can install software and read your filesystem. It sets up the command-line tool (CLI) and Model Context Protocol (MCP) workflow; OpenContext does not provide an Agent2Agent protocol server. ## Copy this prompt ```text Help me install OpenContext on this computer and create -Context-Vault using my preferred username. Read https://getopencontext.com/install-agent.md, https://getopencontext.com/agent-install.json, and https://getopencontext.com/for-agents.md first. Check current availability. Use the verified full local runtime, not a client-only MCP package or the unrelated public npm package named opencontext. If no public download is available, use an authorized checkout or ask me for access or the maintainer-supplied package. Do not invent a download URL. Follow the installation guide, check prerequisites and any published checksum, preserve existing vaults, and connect your Model Context Protocol (MCP) client or command-line tools. Preserve existing client configuration and verify the connection. Complete setup without requiring the frontend. Preview a metadata-only scan of my home directory for documents and useful hidden context. Exclude applications, system folders, credentials, caches, and dependencies. Include application folders or other locations only when I explicitly request them. Show me the scope, exclusions, incomplete coverage, document count, token estimate, time range, and cost estimate where pricing is known. Explain the actual billing provider and any unknown subscription allowance. If subscription execution is unsupported, say so and do not switch to paid provider execution. Wait for my approval of the scope and estimate before ingestion or paid model calls. Then use the existing privacy reviews and deterministic graph-writing pipeline. Report progress and bring privacy holds back to me for review. Keep my vault local; offer the frontend as an optional view of the same vault. ``` ## Current availability The source repository is private, and a public runtime download is not available yet. Use an authorized checkout or a verified full local-app release supplied by the maintainer. A build is not automatically a published release. Do not install an unrelated package named opencontext from a registry. Read the [installation manifest](https://getopencontext.com/agent-install.json) for current availability and the [complete local agent guide](https://getopencontext.com/for-agents.md) for configuration, estimates, and review controls. ## Local bootstrap With Node.js 22 or newer, npm, git, and the authorized full local application in place, run these commands from that folder. Replace USER with the actual username: ```bash npm run setup:agent node cli/opencontext.js serve --username USER ``` Keep the runtime running. From a second terminal in the same folder: ```bash node cli/opencontext.js setup --username USER --json node cli/opencontext.js scan preview --json ``` Review scope, exclusions, coverage limits, and cost/time/token estimates before authorizing ingestion. Subscription allowance is unknown to OpenContext, and subscription-mode previews cannot execute ingestion. Do not switch to paid execution without the user choosing it. Setup does not require opening the frontend; the local browser handoff is optional. Explore the [agent index](https://getopencontext.com/llms.txt) or [full agent instructions](https://getopencontext.com/agents.md).