Command line

Starting nodecode from cron, a pipe or ssh without -t

It exits with code 2. nodecode needs a terminal (no controlling tty); run it in one.

Instead: Use a terminal or ssh -t. With no terminal at all, run nodecode serve, or nodecode gateway on on Linux and macOS.

Putting --store or --ephemeral in front of add, profile, gateway, update or web

Those five take the rest of the line as their own. Exit code 2. nodecode: add is a command of its own: nodecode [-p NAME] add ...

Instead: Only -p NAME goes in front of them: nodecode -p work add nc://web.

Reaching for --ephemeral for a clean start

Only the store is new. Config, layer, memory and skills stay the profile's. New definitions still go to the real layer.

Instead: Use a throwaway home: HOME=$(mktemp -d) nodecode.

Two -p on one line

Exit code 2. nodecode: -p names a second profile, play; a launch runs one

Instead: One profile per launch. Run the other in its own terminal.

--version in front of a command

It answers and exits. nodecode --version add nc://web prints the version and installs nothing.

Instead: Ask for the version on a line of its own.

-p with a profile you have not made

Exit code 2. nodecode: no profile "ghost". "nodecode profile create ghost" makes one.

Instead: Run the line it names, then nodecode -p ghost.

A capital or a dot in a profile name

Refused before anything starts. nodecode: "Bad.Name" is not a profile name: a-z, 0-9, _ and -, 64 at most, starting with a letter or digit

Instead: Lower case and hyphens: bad-name.

Setting $NODECODE_HOME and keeping -p on the line

-p wins. The variable is read only when no -p is given.

Instead: Use one of the two.

Importing to replace what is already here

An existing fact here always wins.

Instead: Add --overwrite.

Importing while another gateway answers the same bots

That gateway is stopped and disabled, so the bots answer from here. The report names the command that gives them back.

Instead: --keep-running leaves it running. Its bots land off here and come on once it stops.

--yes on the first run

It applies without the preview, keys and tokens with it.

Instead: Run it once without --yes. The preview opens in the setup walk.

add in a script, without --yes

With no terminal to ask, nothing is installed. Exit code 1. nodecode: channel-slack is code from the hub and there is no terminal to ask: nothing was installed; add --yes to install it

Instead: Read the repository at the pinned commit first. Then put --yes on the line.

A misspelt name

Exit code 1. nodecode: no cell "websarch" is shipped or on the hub. Did you mean "websearch"?

Instead: Take the name it offers. Every cell is on the Cells tab.

Answering y without opening the repository

Hub code runs inside Nodecode with full access to your files and keys.

Instead: Open the repository at the commit it prints. Answer after. See Cells.

Deleting a profile to start it over

delete removes its whole home: store, layer, memory and secrets.

Instead: Make an empty one beside it: nodecode profile create fresh --blank.

nodecode gateway on on Windows

Windows has no background gateway.

Instead: Run nodecode serve in a terminal you leave open.

--check to update

It stages and classifies the release. It applies nothing.

Instead: nodecode update.

Pasting the link into a chat or an issue

The link carries the operator token, after the #.

Instead: Keep the link to yourself.

resume from a script or a pipe

Exit code 2. nodecode resume needs a terminal (no controlling tty); run it in one.

Instead: Run it in a terminal.