Something wrong?
Tell us.

Telling us, in three steps

1. Register once. Give us an email address. We send a six-digit code to it, good for 15 minutes. You type it back.

   $ ns-brain feedback register you@example.com
   $ ns-brain feedback verify 123456

2. Say what broke. From any project, in a sentence: what you ran, what you expected and what happened instead. A longer report can come from a file.

   $ ns-brain feedback "recall finds nothing for a title I can open by id"
   $ ns-brain feedback - < report.txt

3. Read our reply. When we answer, your next session's brief says so. ns-brain feedback list shows everything you sent and every reply.

What we receive: your text, your email address, your ns-brain version, your operating system and edition. The project's name only if you add --project. Never your memories. A report that looks like it holds a password or a key is refused before it leaves your machine, unless you add --allow-secret because it is a false positive.

You can have five reports open at a time. ns-brain feedback forget-me --yes erases your registration. A report tells us something; it never makes anything happen on your machine.

Security problems go by email instead, to security@fightclub.pro.

When it is not doing what you expected

Most surprises are the brain refusing to guess. These four commands answer most of them: which file it opened, which project it thinks this is, which build you have and whether the brain is healthy.

$ ns-brain env      # paths, the project name, git, the clock
$ ns-brain stats    # counts, and the database path on line two
$ ns-brain doctor   # is the brain in good shape
$ ns-brain version

The session started without the brief

Run ns-brain wakeup in the project.

• It prints the brief: the hooks are not set up. Run ns-brain init again. It replaces the hooks rather than adding more.
• It says there is no brain here: you are outside the project. Run it from inside, or set BRAIN_HOME to the brain directory.
• Command not found: the binary is not on this PATH. Your agent's PATH is often not the same as yours.
• It prints, but the session still shows nothing: some agents run hooks only for new sessions. Open a new one rather than resuming.

A search finds nothing

• Read the first line of the result. When no memory shares your words, it says so and shows the whole area instead.
• Use fewer words, or the words a memory's title would use.
• Search a wider area. A search in deploy:prod sees deploy and everything global, but nothing filed beside it.
• If you can open a memory by its id but a search never finds it, ns-brain reindex rebuilds the search index.

It shows no memories but you know there are some

It opened a different file. ns-brain stats prints which one on its second line. A project with its own file and the shared store cannot see each other's memories.

It refused to do something

Read the message. Every refusal says what it is protecting and how to get past it when you really mean it: a memory that already covers the same thing, a pinned rule, a delete that would bring back facts you corrected, text that looks like a password. Do not work around a refusal you do not understand. That is how memories get lost.

Something looks damaged

ns-brain doctor checks the brain and says what is wrong. ns-brain doctor --fix repairs what it can and names the rest.

It will not open after an upgrade

Do not try to fix it by hand. ns-brain upgrade --apply made a backup first. ns-brain backup --list --verify lists the copies and checks each one. ns-brain backup --restore <file> --apply puts one back.

Still stuck? Tell us, with the command you ran and what it printed.