Guides

Get NORDON installed and running from scratch. This takes about 2 minutes.

1. Install the CLI

   npm install -g @sodasoft/nordon-cli

2. Initialize your config

   nordon init

   This creates your config file and data directories. Everything stays on your machine.

3. Start the daemon

   nordond &

   The daemon runs in the background and handles everything automatically.

4. Link your project

   cd /path/to/your/project
   nordon link-repo

   This tells NORDON to track this repository. Repeat for each project you want to use with NORDON.

5. Verify everything works

   nordon doctor

   You should see all checks pass. If anything fails, see the troubleshooting page.

Connect NORDON to Claude Code so it can capture events and inject memories automatically.

1. Find your Claude Code settings file

   The file is located at:

   • macOS / Linux: ~/.claude/settings.json
   • Windows: %USERPROFILE%\.claude\settings.json
2. Open the file in any text editor

   If the file doesn't exist yet, create it. If it already has content, you'll merge the hooks into it.

3. Add the NORDON hooks

   {
     "hooks": {
       "PostToolUse": [{
         "matcher": "*",
         "command": "nordon hook post-tool \"$TOOL_NAME\"",
         "timeout": 5000
       }],
       "Stop": [{
         "matcher": "",
         "command": "nordon hook session-end",
         "timeout": 10000
       }]
     }
   }

4. Save and restart Claude Code

   Claude Code picks up the new hooks on the next session. NORDON will start capturing events and building memories automatically.

5. Verify it's working

   After your next Claude Code session, check that events are flowing:

   nordon logs --limit 5

NORDON creates memories automatically from your coding sessions. You can search, review, and curate them to improve what gets injected.

1. Search for memories

   nordon memories search "auth middleware"

   Returns memories matching your query. Results show the memory ID, title, and a short summary.

2. Inspect a specific memory

   nordon memories inspect abc123

   Shows the full memory content, including when it was created, how many times it has been used, and its current status.

3. Approve useful memories

   nordon memories approve abc123

   Approving a memory tells NORDON it was helpful. Approved memories are more likely to be injected in future sessions.

4. Reject unhelpful memories

   nordon memories reject abc123

   Rejecting a memory tells NORDON it wasn't useful. Rejected memories are less likely to appear in future injections.

On the Pro plan, NORDON is branch-aware. This means memories are scoped to the branch you are working on, so you get the most relevant context.

1. Link your repo (if not already done)

   cd /path/to/your/project
   nordon link-repo

2. Work normally on your branches

   NORDON automatically detects which git branch you are on. Memories created while on a feature branch are tagged with that branch.

3. Memories follow your branch

   When you switch branches, NORDON adjusts which memories are most relevant. A memory created on feature/auth will be prioritized when you return to that branch.

4. Merged branches share context

   When you merge a feature branch into main, the memories from that branch become available on main too. Nothing is lost.

5. Preview branch-specific injection

   nordon inject --preview

   This shows you exactly what context would be injected for your current branch and repo.

On the Team plan, you can share memories across your team. This means everyone benefits from what any team member learns.

1. Create a workspace

   Your team admin creates a workspace from the NORDON dashboard or CLI. This is a shared space where team memories live.

   nordon dashboard

2. Invite team members

   Send invitations to your team from the dashboard. Each member needs their own NORDON account with a Team license.

3. Share memories

   When a team member creates a useful memory, they can share it to the workspace. Shared memories are visible to everyone in the team.

4. Approve shared memories

   Team admins can review and approve shared memories before they appear in everyone's injections. This ensures quality control.

5. Enable sync

   nordon sync enable

   Sync keeps your local memories in sync with the team workspace. All data is encrypted end-to-end.

Start with the free plan and upgrade when you need more features.

1. Check your current plan

   nordon plan show

   This shows your current plan, active features, and usage limits.

2. Choose an upgrade

   nordon plan upgrade

   This opens the pricing page in your browser where you can select Pro ($29/mo) or Team ($79/user/mo).

3. Complete the purchase

   After payment, you'll receive a license key by email.

4. Activate your license

   nordon plan activate <your-license-key>

5. Verify the upgrade

   nordon plan show

   You should see your new plan and all unlocked features listed.

Instead of manually starting the daemon every time, install it as a system service so it runs automatically when you log in.

1. Install the service

   nordon service install

   This registers NORDON as a system service. It works on macOS (launchd), Linux (systemd), and Windows (Windows Service).

2. Check service status

   nordon service status

3. The daemon starts automatically

   After installing the service, the daemon starts when you log in. No need to run nordond & manually.

4. Uninstall the service (if needed)

   nordon service uninstall

Export your memories for backup, migration, or sharing. Imports merge memories into your existing database without duplicates.

1. Export all memories

   nordon memories export > memories.json

   This saves all your memories as a JSON file. Store it somewhere safe as a backup.

2. Import memories

   nordon memories import < memories.json

   This loads memories from a JSON file into your database. Existing memories are not overwritten.

3. Transfer to a new machine

   To move NORDON to a new machine, export on the old machine, install NORDON on the new machine, then import:

   # Old machine
   nordon memories export > memories.json
   
   # New machine
   npm install -g @sodasoft/nordon-cli
   nordon init
   nordond &
   nordon memories import < memories.json

4. Schedule regular backups

   Add the export command to a cron job or scheduled task to create automatic backups:

   # Example cron job (daily at midnight)
   0 0 * * * nordon memories export > ~/backups/nordon-$(date +%Y%m%d).json