A node is a working folder. Turns in that node run with that folder as the current directory. 
/node
/node <name>
/node apex
/node ~/code/some-project/
/node home

​
List

/node with no argument prints a table of named projects on this Mac, when a catalog is present.
  • • = active
  • (apex) = the top-level project
  • 🤝 = shared from another account
  • 🛰️ = your project, files on another of your Macs
You only see projects you are granted. Directory paths are shown to owners only. With no catalog, /node reports the single working directory (TELEKIT_WORKING_DIR). /node ~/path/ still seats a folder.

​
Switch

/node appleo — case does not matter. A unique prefix works. A multi-word id is the rest of the line (/node Test Node). Ambiguous prefix → refused, candidates listed, nothing switched. Files not on this Mac → refused, active node unchanged.

​
/node apex

Reserved handle for the top-level project on this Mac. Portable. Not a grant — without access to that project it is refused like an unknown name. If a real project is also named apex and is not the top-level one, the handle wins and the reply says so. That project stays reachable by a shorter unique prefix.

​
Folders

/node ~/path/ seats later turns in that folder. Owner only. The path is expanded like a terminal path. A trailing slash is added if you skip it. A missing directory is refused. /node home returns to the configured working directory (TELEKIT_WORKING_DIR).

​
Adding projects

/node add and /node rm are retired. You cannot create named catalog entries from Telegram. Point at a folder with /node ~/path/, or set TELEKIT_WORKING_DIR.

​
Relock

Default: switching node locks the new lane. telekit passcode relock-on-node-switch off carries the remaining unlock TTL. It never grants a node you do not already have.