Devices
Sign a terminal into your library, check its access and expiry, and disconnect or reconnect a machine.
A signed-in terminal holds a token for your library. It does not need your password in a command or script.
Open in Puni to open these settings.
#Connect a machine
- In Settings → Devices → Connect a machine, copy the command, or run it below.
- Open the address the terminal prints, sign in, and type the code it shows.
- Check what the request says it is, the access it asks for, and when and where it started before approving.
- Return to the terminal and wait for sign-in to complete.
puni auth login --base-url https://puni.designApprove only the request you just started: a code someone sent you will show another time or place. A machine asks for read and write; run the command with --scope share if it should also publish share links. If its code expires, run the command again for a fresh one. The terminal token lasts thirty days and is stored at ~/.config/puni/credentials.json with access limited to your user.
#Inspect connected devices
Settings → Devices → Connected lists each machine, when it connected, its last activity and when its token expires. Agent-client tokens appear separately in Settings → Agents.
#Disconnect and reconnect
Choose Disconnect on the machine's row to revoke its access. That terminal must run the sign-in command again before it can use the library. An expired token also needs a new sign-in.
Local scene-file commands can work without a library connection. Remote project commands need a signed-in machine with the appropriate access.
Read Scopes and tokens for access levels, or Auth commands for terminal details.
Was this useful?