Configuration

When you run nordon init, NORDON creates a configuration file. The location depends on your operating system:

You can edit this file directly with any text editor, or use CLI commands to change individual settings.

The config file uses the TOML format. Here are the options you can set:

You can override config file settings with environment variables. These take priority over whatever is in your config file.

Here is where NORDON stores its files on each platform:

macOS / Linux

Windows

Minimal (defaults)

After running nordon init, your config file looks like this. Everything uses sensible defaults:

# ~/.config/nordon/config.toml

api_port = 7533
injection_mode = "auto"
log_level = "info"

Custom port

If port 7533 is already in use, pick a different one:

api_port = 9000
injection_mode = "auto"
log_level = "info"

Remember to also start the daemon on the new port:

nordond --port 9000 &

Verbose logging

When troubleshooting, turn on debug logging to see everything NORDON is doing:

api_port = 7533
injection_mode = "auto"
log_level = "debug"

Then check logs with:

nordon logs --limit 100

Custom data directory

Store all NORDON data in a specific folder:

api_port = 7533
injection_mode = "auto"
log_level = "info"
data_dir = "/home/you/nordon-data"

To connect NORDON with Claude Code, you add hooks to your Claude Code settings file. These hooks tell Claude Code to notify NORDON about tool usage and session events.

Settings file location

Hook configuration

Add this JSON to your settings.json file:

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

What each hook does

• PostToolUse — Runs after every tool call in Claude Code. NORDON captures these events to understand what happened during your session and build memories from them.
• Stop — Runs when a Claude Code session ends. NORDON processes the session's events and creates or updates memories.