Nodus
GitHub

For AI assistants

Public instructions you can hand to an AI assistant before it operates Nodus in your repo.

Overview Getting started Install Add package from link For AI assistants

Give this page to the assistant when you want it to operate Nodus for you. It tells the assistant how to identify the repo role, choose the target adapter, prefer safe defaults, and finish with nodus doctor.

Confirm these facts first

  • Decide whether the repo is already using Nodus packages or authoring a Nodus package.
  • Identify the target tool: codex, claude, cursor, copilot, opencode, or agents.
  • Work out whether the user wants install, sync, update, inspect, remove, or package initialization.

Prefer these defaults

  • Treat nodus.toml as the source of truth for requested dependencies and nodus.lock as the source of truth for resolved revisions.
  • Do not tell users to hand-edit .codex/, .claude/, .cursor/, .github/, .opencode/, or .agents/ outputs.
  • Default to project-scoped installs and install the whole package unless the user clearly asks for narrower components.
  • Prefer tags for released packages. Use branches or revisions only when the user clearly needs them.
  • After changing package state, finish with nodus doctor.

Fetch the raw assistant prompt directly:

https://nodus.elata.ai/prompts/README.md

Check whether Nodus is installed:

nodus --version

If the user only has a package link, normalize it first:

/packages/

For a first project-scoped install, start here:

nodus add owner/repo --adapter <adapter>

Then validate the result:

nodus doctor

Related public pages