STEP 3 OF 6

Install with NPM

Run the local installer, review its proposed plan, and approve changes only afterward.

Last reviewed:

On this page

Overview

Start with the public command npx personal-agentic-os@latest in a terminal. The installer should show the destination and setup plan before writing files. Do not approve unknown paths, keys, or credentials.

Run the installer

Check the prerequisites, then run npx personal-agentic-os@latest. Use npx personal-agentic-os@latest --help to inspect available commands. Package retrieval needs network access; a successful download does not mean setup is complete.

Review before applying

Review the installation mode, Vault destination, selected tools, and sources. Approve only a plan you understand. Installation telemetry is optional and off by default; its payload excludes project content, conversation text, and cost records.

After installation and on failure

Keep the generated configuration-file location for later commands. NPM handles repeatable setup; semantic discovery and memory migration use the official installation prompt with your approval. For network or permission errors, resolve the cause and inspect existing files before retrying.

Completion checklist

Treat installation as complete when the approved plan has run, you have the generated configuration location, and only selected adapters have been prepared. Do not conceal errors by deleting the Vault or rerunning setup without review. Next, check memory mode and the first tool connection before the first sync.

Sources and next actions

Was this guide helpful?

With analytics consent, your answer helps us choose and improve guides.

Help improve these guides

With your permission, views, clicks, copies, article-end visibility, feedback and broad search topics are stored as daily counts in the project’s Neon database to plan better guides. This analytics payload excludes search text, URL parameters and visitor identifiers. Hosting infrastructure processes network information when receiving requests. Your choice stays in this browser. Revoking consent stops future events, but existing aggregate counts remain.