Something not working?
A handful of things go wrong more than everything else combined, and each of them is fixed by a line you can paste. Try the one that matches your screen. If none of them do, the address at the bottom of this page reaches a person.
Try first
The common ones
command not found: ferrow
The install worked; your terminal has not noticed it yet. Close the window, open a new
one, and run it again. If it still says that, npm put the command in a folder your
terminal does not search. PATH is the list of folders your terminal
looks in when you type a command name — Ferrow is installed, it is just not on
that list. The line below asks npm where it put things and adds that folder for good.
Paste the one for your machine; it prints nothing, which is success.
macOS, in the Terminal app (it uses zsh):
echo "export PATH=\"$(npm prefix -g)/bin:\$PATH\"" >> ~/.zshrc
Linux, if your shell is bash:
echo "export PATH=\"$(npm prefix -g)/bin:\$PATH\"" >> ~/.bashrc
Windows, in PowerShell — one long line. On Windows npm keeps the
commands in that folder itself rather than in a bin inside it, which is why
this line is not just the one above with different punctuation:
[Environment]::SetEnvironmentVariable('Path', [Environment]::GetEnvironmentVariable('Path','User') + ';' + (npm prefix -g), 'User')
Then close the terminal and open a new window — the old
one keeps the old list — and type ferrow again.
command not found: node
Node is not installed, and Ferrow needs version 20 or newer. Install it from nodejs.org — the button marked LTS — then close the terminal, open it again, and install Ferrow:
npm install -g @ferrow/ferrow
If node --version answers but the number is
below v20 — v18.20.4, say — that Node is too old for
Ferrow. The same LTS installer from nodejs.org replaces
it, with nothing to uninstall first; close the terminal, open a new one, and check
node --version reads v20 or higher before installing again.
npm install -g says permission denied, or EACCES
npm is trying to write into a folder your account does not own. Do not re-run it
with sudo — that leaves root-owned files behind and the next
install fails from the other side. On macOS and Linux, give npm a folder you already
own:
mkdir -p ~/.npm-global
npm config set prefix ~/.npm-global
Then install Ferrow again, and run the PATH line for your
machine from the first answer above — npm prefix -g now prints this new
folder, so the same line adds the right one.
The name is scoped — @ferrow/ferrow — but the
command it installs is just ferrow. If you would rather install from a file
you can check first, the download page ships the same thing as a tarball
with its sha256.
You paid on the website and this computer does not know
Paying and switching on a machine are two steps on purpose — nothing about your purchase reaches your laptop until you tell it to. One line does it:
ferrow activate <your key>
Your key looks like ferrow_ followed by a long string, and it is on the page
you landed on after paying. The same command accepts the cs_ checkout
reference or the whole web address of that page, so whatever you copied will do.
Ferrow has no completed purchase for that reference yet
Stripe's confirmation can take a few seconds to reach Ferrow. Wait a moment and run the same command again — nothing is charged twice by trying. If it has been a few minutes, that is worth an email.
You lost the key
It is still in your account. Sign in at app.ferrow.ai and open Settings → Account, where you can reveal and copy it again for a second machine. If you cannot get into the account either: open app.ferrow.ai, press Account at the top, and under the log-in form use Forgot your password? — it emails the address on the account, so check your email and follow it back in. If that email never arrives, or you have lost the mailbox too, write to us and a person will sort it out.
Then
Write to us.
One address, read by a person:
support@ferrow.ai
There is no ticket system, no bot and no phone queue. Ferrow is pre-1.0 and small, so a reply takes as long as it takes a person to get to it — usually a day or two, and longer at a weekend. We would rather say that than print a number we cannot hold to. In the app, the Report a bug button at the foot of the window does the same job, without leaving it.
Before you write, run ferrow doctor and paste what it prints.
It states which Ferrow you are on, where your vault is, and what is and is not set up — the
things we would otherwise have to ask you for. It reads your own machine, asks ferrow.ai
one question — whether a newer Ferrow is out — and prints no key, ever. Then add these
four lines:
node --version prints.cs_ checkout reference, or the email address you paid
with. Never send us your key, your password or your card number — we do not need any
of them, and we will not ask.That is worth reporting on its own, even when nothing is broken for you. The docs are hand-written against the real program, and every place they drift is a place the next reader gets stuck.
Also
Where the answers already are.
ferrow help prints the whole command surface, grouped.
ferrow doctor checks the install and names anything it finds.