Linkwise CLI
Install
A single static binary with no runtime to install alongside it. Every release publishes to Homebrew and npm at the same time, from the same tag.
The shell installer and the npm package both verify the release checksum before they unpack anything. If it does not match, nothing is written.
Update
linkwise update reports the newest release and the one command that installs it. Each channel owns the file it put on disk, so the right command is not the same for everyone; update works it out from where the binary actually lives rather than asking you to remember.--run executes it for you.
You do not have to go looking. Once a day, a command run at a terminal checks in the background and prints a single line on stderr when a newer release is out. It never delays a command: the lookup runs alongside the work you asked for, and an unfinished one leaves the news for next time.
Set LINKWISE_NO_UPDATE_CHECK to turn the notice off. It is already off wherever it would be noise: piped output, --json, and any environment with CI set.
On 0.1.1 or earlier?
linkwise update arrived in 0.1.2, so an older binary answers that there is no such command. Update it once with the channel it came from, and linkwise update takes over from there. ls -l $(command -v linkwise) tells you which: a link into Caskroom is Homebrew, a link into node_modules is npm, and a plain file is the shell installer. An npm install that fails with EEXIST on /usr/local/bin/linkwise is npm finding a binary another channel put there, and refusing to overwrite it.
Installed with the shell script, switching to Homebrew?
Remove the old binary first. The installer writes a real file to /usr/local/bin/linkwise and the cask wants to put its own symlink there, so brew install stops with there is already a Binary at ... until you rm it. Going the other way, the installer refuses on its own rather than breaking your Homebrew install.
Authenticate
auth login opens the dashboard, takes the key you paste, and checks it against GET /v1/me before storing it, so a mistyped key fails at the prompt rather than on your next command. It is kept in the system keychain; on a machine without one the CLI writes it to a 0600 file and tells you it did.
In CI, skip the browser entirely and set LINKWISE_TOKEN. The CLI prefers the environment variable over anything stored, so a pipeline never picks up a developer's credentials by accident.
The full-screen app
Run linkwise with nothing after it and the terminal becomes a reader for the whole library, laid out like the Library tab in the app. Browse everything, what is unread, unsorted or archived, one collection, what arrived by email, the posts from one RSS feed, or the links that have an AI summary, then read the extracted article in place without opening a browser. Past conversations with Linkwise AI open as transcripts.
Every row on the home screen says what it does. Press / and type to narrow the list to a feature; the Search row stays and offers to search the library for the same words, so enter always goes somewhere.
d switches between the light and dark palettes and remembers the choice in config.toml. NO_COLOR drops it to plain text, the same as everywhere else.
Wherever the interface cannot be drawn, the bare command prints help exactly as it did before: output piped somewhere, no terminal on stdin, --json, or not signed in. A script that runs linkwise with no arguments sees what it always saw.
Conversations need a key with the ai:chat scope, which a key made for the library does not have. Without it the screen says so and names the scope.
Keys
j / kMove down and up. Arrow keys work too.enterOpen what is selected.escBack to wherever you came from./On the home screen, narrow the menu to a feature or search the library. Anywhere else, search titles, descriptions and content.?Every key, in one screen.dSwitch between the light and dark palettes.qQuit, leaving the scrollback as it was found.oOpen the selected link in the browser.yCopy the selected link to the clipboard.eArchive it, or restore it if it is archived.uToggle read and unread.pPin it, or unpin it.Configuration
Resolved in this order, first one wins: a command flag, then the environment, then the config file, then the default.
Environment
LINKWISE_TOKENPersonal access token. Overrides the keychain.LINKWISE_APIBase URL. Useful for pointing at a staging deploy.LINKWISE_PROFILEWhich profile to use, for multiple accounts.NO_COLORAny value disables colour, per the no-color.org convention.LINKWISE_NO_UPDATE_CHECKAny value silences the once-a-day update notice.Output and piping
Human-readable tables on a terminal, machine-readable JSON when piped. The CLI detects this rather than making you remember a flag, and --json forces it either way.
Exit codes
Distinct per failure class, so a script can tell "your key expired" from "that link does not exist" without parsing stderr. They map onto the API's error codes.
Codes
0SuccessThe command did what it said.1ErrorAnything unclassified, including a network failure.2UsageBad flags or a missing argument. Nothing was sent.3AuthNo token, or it is invalid, expired or revoked. Maps to unauthorized.4ForbiddenThe token lacks the scope, or API access is disabled. Maps to forbidden.5Not foundNo such link, collection or tag. Maps to not_found.6Rate limitedOver the limit. The CLI already waited and retried once. Maps to rate_limited.7Plan limitA quota is exhausted or the endpoint is Pro only.Commands
Each one names the endpoint it calls, so you can drop to curl for anything the CLI does not cover.
Interactive
The command with nothing after it.
linkwiseGET /v1/linksOpen the full-screen library: browse everything, unread, unsorted, archived, one collection, email, one RSS feed or the links with insights, read the extracted article in place, and read past conversations with Linkwise AI. Prints help instead wherever it cannot be drawn, so a script that runs the bare command sees what it always saw.
Saving
The command you will actually type all day.
linkwise save <url> [--title] [--description] [--collection] [--tag]POST /v1/linksSave a link. Re-running with the same URL returns the existing link rather than creating a duplicate.
linkwise open <id>GET /v1/links/{id}Open a saved link in the browser.
linkwise read <id> [--raw]GET /v1/links/{id}/contentPrint the extracted reader content to stdout, as Markdown by default.
Library
Listing and organising what you have saved.
linkwise ls [--collection] [--tag] [--archived] [--limit]GET /v1/linksList links, newest first. Paginates automatically when piped.
linkwise rm <id>DELETE /v1/links/{id}Delete a link. Soft delete, recoverable in the app.
linkwise tag <id> <tag>...PUT /v1/links/{id}/tagsReplace the tags on a link. Tags that do not exist are created.
linkwise collections [ls|new|rm]/v1/collectionsManage collections.
linkwise tags [ls|new|rm]/v1/tagsManage tags.
linkwise highlights [ls|add]/v1/highlightsRead and create highlights.
Finding
Two search modes, one flag.
linkwise search <query> [--mode fast|hybrid]GET /v1/searchSearch the library. Fast is keyword only and returns everything at once. Hybrid blends keyword with embeddings, and is the default.
linkwise search --highlights <query>GET /v1/search/highlightsSearch inside your highlights instead of your links.
linkwise discover [--save <id>]/v1/discoverPrint the recommendation feed, and optionally save one item into the library.
Feeds
RSS in, OPML out.
linkwise feeds [ls|add <url>|rm <id>]/v1/feedsManage RSS subscriptions.
linkwise feeds export > linkwise.opmlGET /v1/feeds/exportExport every subscription as OPML, importable by any reader.
AI
Pro only, and streams by default.
linkwise ask <question> [--link <id>] [--collection <id>]POST /v1/chatAsk a question over one link, one collection or the whole library. Streams to the terminal.
Not available to an API key yet. Needs a signed-in session. The chat and speech functions resolve the caller from a user JWT, so an API key cannot reach them yet.
linkwise say <id> [--voice] [--out file.mp3]POST /v1/ttsSynthesize a link to speech.
Not available to an API key yet. Needs a signed-in session. The chat and speech functions resolve the caller from a user JWT, so an API key cannot reach them yet.
Account
Who you are and what is left.
linkwise auth loginGET /v1/meOpens the dashboard, takes the key you paste, checks it works and stores it in the system keychain.
linkwise auth statusGET /v1/meShow the active profile, its scopes, and which source the key came from.
linkwise auth logout-Remove the stored key from this machine. The key keeps working until you revoke it in the dashboard.
linkwise usageGET /v1/me/usagePlan, credits and remaining quota.
linkwise update [--run]-Report the newest release and the command that installs it. Which command that is depends on how the binary was installed, so update works it out from where the binary actually lives rather than guessing. --run executes it.
linkwise completion [bash|zsh|fish]-Print a shell completion script. Source it from your shell profile.