WisyLink CLI (npm package)

Official coding-agent CLI for WisyLink — device login, interactive chat, live build previews, files, and links.

npm i -g @wisylink/cli

wisylink login

Opens a browser device-authorization flow (https://wisylink.com/cli/authorize). Approve only a code you just started with wisylink login in your own terminal. Credentials are stored at ~/.config/wisylink/credentials.json (or under an absolute $XDG_CONFIG_HOME) with mode 0600 in a 0700 directory; on Windows the file is private through your user profile's permissions. Works for every plan, including Community.

wisylink logout ends the session on the server and removes the local file.

wisylink whoami
wisylink logout

API keys still work for scripts. Usage bills against your subscription limits.

export WISYLINK_API_KEY="your_api_key"
wisylink links list --json

Keep your API key out of shell history and version control: set WISYLINK_API_KEY from your CI's secret store. A value passed with --api-key is visible to other users of the machine in the process list.

• On a terminal the CLI prints readable text: spinners, the session and preview links, build reports.
• --json prints the result as one JSON object on stdout and errors as a JSON object on stderr, with no spinners or prompts. Use it in scripts and CI. It takes no value and works before or after the command.
• wisylink login --json writes the device code and URL as a JSON object to stderr, waits for approval, then prints { "ok": true, "user": … } on stdout.
• files and links commands also print JSON on their own when stdin or stdout is not a terminal. chat prints text unless --json is given.
• Versions before 0.3 printed JSON only and rejected --json. A script that reads chat output must add --json when it moves to 0.3 or later.

wisylink login
wisylink logout
wisylink whoami

Interactive REPL (TTY):

wisylink chat

One-shot:

wisylink chat --message "Build a landing page for Ember Coffee." --file-id 67e6f6e6c5a91e4d2d9b0a11

Continue a link (one-shot, or without --message to open the REPL on it):

wisylink chat --link-id k3x9a2 --message "Make the hero darker."
wisylink chat --link-id k3x9a2

After each turn the CLI prints the session URL (https://wisylink.com/chat/<id>) and the hosted preview URL.

• **Login session:** while a build is running the CLI polls its status, animates the live report, and **Ctrl+C** stops the build. A build waiting behind another one for the same link shows as queued; the CLI keeps waiting.
• **API key:** the CLI prints the build notice and returns. Check later with wisylink links get <link-id>; status is one of building, queued, completed, aborted, idle.

Automation:

# WISYLINK_API_KEY comes from the CI secret store
wisylink chat --message "…" --json

The JSON has id, url, status, answer, created_at, updated_at and session_url with an API key; with a login session it has id, url, session_url, building and answer, plus rejected_files when a file was left off because it would exceed your storage quota.

wisylink files upload "./asset.png"
wisylink files get 67e6f6e6c5a91e4d2d9b0a11
wisylink files delete 67e6f6e6c5a91e4d2d9b0a11

Uploads use <=4 MB chunks (up to 25 MB total). The file type is read from the file's content, not its name. Works with a login session or an API key.

wisylink links list --page 1 --limit 20
wisylink links get k3x9a2
wisylink links delete k3x9a2

--limit is 1..100 (default 20) with an API key; a login session returns at most 25 links per page.

import { CreateWisyLinkClient } from "@wisylink/cli";

const client = CreateWisyLinkClient({ apiKey: "<api-key>" });
const result = await client.chat({
  message: "Build a landing page for Ember Coffee.",
  fileIds: ["<file-id>"],
});
console.log(result); // { id, url, status, answer, created_at, updated_at }

// Continue the link, then list, read and delete links by their 6-character id.
await client.chat({ message: "Make the hero darker.", linkId: result.id });
const { items } = await client.listLinks({ page: 1, limit: 20 });
await client.getLink("k3x9a2");
await client.deleteLink("k3x9a2");

Methods throw before sending a request when an id, the message (1..5000 characters) or the file id list (at most 10) is invalid.

• Session tokens live only in ~/.config/wisylink/credentials.json (mode 0600).
• API keys from WISYLINK_API_KEY / --api-key are never echoed or logged.
• All requests go over HTTPS to https://api.wisylink.com.
• Use --json in CI so output stays machine-readable with no TTY animations (see Output).