Reference · Troubleshooting

Troubleshooting

The handful of things that trip people up first — what you see, why it happens, and the fix. Most are a reload or a version away from working.

Plugin changes didn't take effect

You edited or updated an agent, command or skill, but the change isn't live in the session. These changes are reload-gated: they only register on a reload/restart.

Gotcha Agent, command and skill changes register only on a session restart. Restart the session, then verify the change live.

Node version errors

Agentry requires Node ≥ 24. The agentry mem store uses node:sqlite, which isn't available on older runtimes, so an older Node fails before anything useful happens.

Gotcha Check with node --version. If it's below 24, upgrade Node before launching.

agentry: command not found

The plugin puts agentry on the Bash tool's PATH while it is enabled, so a terminal outside Claude Code may not have it. The slash commands fall back on their own. By hand, run the script it wraps, from the installed plugin's folder, with the same arguments: 

node "${CLAUDE_PLUGIN_ROOT}/scripts/lane.mjs" exec show T-4

CLAUDE_PLUGIN_ROOT is that folder inside Claude Code; in another terminal, put its path in. board.mjs, lane.mjs and mem.mjs sit side by side in scripts/. agentry --version prints the build that is running.