The node
The node
Every command the node answers to, by what you are doing.
The node is the cantor command on your computer. One process runs in the
background and keeps your library; every other command talks to it over a
local socket, so nothing here needs sudo or a second terminal.
Running
Section titled “Running”| Command | What it does |
|---|---|
cantor status |
Name, key, relay link, and how many phones are paired |
cantor start, stop, restart |
Bring the background node up and down |
cantor logs |
What the node has been saying |
cantor run |
The node itself, in the foreground |
Models
Section titled “Models”| Command | What it does |
|---|---|
cantor pull |
Download a model |
cantor list |
What is installed, and what the catalog offers |
cantor rm |
Remove a model and reclaim its space |
cantor backends |
Which engine runs your models: CPU, CUDA, Metal or Vulkan |
Phones
Section titled “Phones”| Command | What it does |
|---|---|
cantor pair |
Show a one-time code for a phone to scan |
cantor pairings |
The phones this node trusts |
cantor revoke |
Stop trusting a phone |
cantor rename |
Name a phone, or the node |
Making and keeping current
Section titled “Making and keeping current”| Command | What it does |
|---|---|
cantor generate |
Make a song from the terminal |
cantor upgrade |
Move to the newest release |
On every command
Section titled “On every command”cantor --help prints the usage, and cantor --version the version.
--control-socket PATH points a command at a node listening somewhere other
than the default; you only need it if you started one that way. Where files
live, and what node.toml holds, is in Files and settings.