A brain shared by a team: persistent memory for coding agents. Every project attached here starts each agent session from what the team already knows and writes back what it learns.
First machine. Install the client, then sign in from the root of a project. An admin approves the code it prints (on day one, you, at /login) and it offers to attach that project:
curl -fsSL https://brain.fightclub.pro/install.sh | sh cd ~/code/your-project ns-brain hive login --server https://hive.fightclub.pro
Another project on a machine already signed in. No second login; run one of these in the project's root.
A project with no brain yet:
ns-brain init --hive https://hive.fightclub.pro
A project with a local brain, which is copied up first:
ns-brain hive join --apply
Signed in to more than one organisation on this machine? Add --org <slug>
to either command to say which. ns-brain hive status lists the ones you hold, and
the choice is written into the project's brain.json, so you say it once.
Another machine, or a colleague. ns-brain hive login there;
an admin approves the code on the dashboard or with ns-brain hive approve.
Then, day to day. Your coding agent does this through the hooks: a brief when a session opens, related memories with every prompt, a nudge to store what it learned. You can do all of it from a terminal in the project too:
$ ns-brain remember --type decision \
--title "Payments go through Stripe Checkout, not Elements" \
--body "Keeps us out of PCI scope. Decided with finance."
remembered #2 on https://hive.fightclub.pro [reported]
$ ns-brain recall "stripe payments"
#2 [decision] (score 1.188) Payments go through Stripe Checkout, not Elements — alice@acme.example, 2026-09-28 15:01
Keeps us out of PCI scope. Decided with finance.
$ ns-brain prefer "Run the test suite before every commit"
$ ns-brain log --kind deploy --summary "v2.3.0 to production"
$ ns-brain task add "renew the push certificate" --when 2026-11-01
$ ns-brain note web "the checkout decision is in api: recall stripe"
$ ns-brain brief # what the next session starts from
A colleague's session in the same project recalls #2 tomorrow without being told it exists. That is the point.
Step by step, for everything a person does: registering, adding a project, letting a colleague in, several organisations, a lost laptop, the end of the trial and upgrading. Every command, flag, role and error message is in the docs. An agent sent here should read /llms.txt.