Use Design Language Connect from the terminal
Connect, update and sign in your AI tools with pfdl connect, on any system with Node.js 20.
pfdl connect is the engine behind Design Language Connect, in the pfdl command line. Use it on Linux systems other than Ubuntu, on a portal that doesn't offer the app, or when you prefer a terminal. It needs Node.js 20 or later.
Get started
- Download the command line from your portal and sign in. Replace the address with your portal's:
curl -fsSO https://pfdl.example.com/downloads/pfdl.mjs
node pfdl.mjs connect sign-in --portal https://pfdl.example.com
- The command prints an address and a code, then waits. Open the address, check the code and choose Approve. See Sign in to Connect for what approving does. Ctrl-C cancels.
- Connect a tool:
node pfdl.mjs connect add claude-code --portal https://pfdl.example.com
On Linux, the Connect page (/connect) shows these commands with your portal's address filled in, with a Copy commands button.
Commands
node pfdl.mjs connect status # each tool, how it's connected, and the organisation you're signed in to
node pfdl.mjs connect add <tool> # connect a tool
node pfdl.mjs connect update [tool] # update one tool, or with no tool everything that's behind
node pfdl.mjs connect remove <tool> # take the design language out of a tool
node pfdl.mjs connect sign-in # approve this computer in the browser
node pfdl.mjs connect sign-out # sign out and revoke this computer's token
Tools: claude-desktop, claude-code, codex, antigravity, vscode, cursor. Claude Desktop has no Linux version.
Options:
--portal <address>uses another portal. Without it, the command usesPFDL_PORTAL_URL.--jsonprints machine-readable output.
In Windows PowerShell:
irm https://pfdl.example.com/downloads/pfdl.mjs -OutFile "$env:TEMP\pfdl.mjs"
node "$env:TEMP\pfdl.mjs" connect add vscode --portal https://pfdl.example.com
One sign-in for both
The command line and the app share one sign-in, kept in the same folder: ~/Library/Application Support/PFDL/ on a Mac, %LOCALAPPDATA%\PFDL\ on Windows, and ~/.config/PFDL/ (or $XDG_CONFIG_HOME/PFDL) on Linux. Other pfdl commands, such as pfdl mcp and pfdl create, use that sign-in when PFDL_TOKEN isn't set. PFDL_TOKEN always wins.
If something goes wrong
| What you see | What to do |
|---|---|
| The usage line, with exit code 2 | Check the command and the tool's name against the lists above. |
connect update exits with 1 | At least one tool failed; each line with ✗ says why. |
pfdl-data.json not found | The command doesn't know your portal. Add --portal <address>, or set PFDL_PORTAL_URL. |
For the rest of the command line, see The pfdl command line.