Troubleshooting
Start with this. It names whatever is in the way:
bash
memnox doctorMy agent stopped and nothing says why
Four things stop work without a rule saying so. Check each:
bash
memnox approvals # a call is waiting for you
memnox paused # the loop breaker paused a session
memnox budget # a budget ran out
memnox lock --list # another agent holds the fileThen:
bash
memnox approve <id> # answer the waiting call
memnox resume <session> --by <you> # let a paused session carry on
memnox lock --release <id> # free a fileIt was refused and I want to know why
bash
memnox why # the rule, the reason and what to do instead
memnox why --evidence # with what it was based on
memnox trace <id> # one action, end to endOr ask the agent why was that stopped?
The rule is wrong
Test the command, then fix the rule in memnox.policies.toml:
bash
memnox policy test "gh pr merge 12" # which rule matched, and its answer
memnox policy check # does every rule file loadTo stop being asked for a while instead:
bash
memnox allow gh.pr-merge --for 2h --reason "release day"It keeps asking me
bash
memnox approve <id> --session # yes for the rest of this session
memnox approve <id> --group # yes for every similar call waiting
memnox next --hand-over # allow what you always approveNothing is being checked
bash
memnox status # is the mode off, or protection stopped?
memnox doctor --wiring # is each seam actually in the path
memnox start # if someone ran memnox stopIf the mode is observe, nothing is blocked on purpose:
bash
memnox config set mode enforceAn editor started from the dock may not see the shell wrappers. Start the agent through Memnox to be sure:
bash
memnox run -- claudeI need it out of the way right now
bash
memnox stop --for 30m --reason "debugging the deploy" # on the record, back on by itself
memnox uninstall # remove it completelyAfter an update
bash
memnox update # the latest version, with the wiring pointed at it
memnox doctor # check nothing came loose