CLI

The weside CLI brings your companion to the terminal. Same companion, same memory as the app — for people who’d rather not leave the command line. It’s open source (Apache 2.0), written in Go, and lives at github.com/weside-ai/weside-cli.

Install

# Homebrew (macOS/Linux)
brew tap weside-ai/tap
brew install weside-cli

# npm
npm install -g weside-cli

# Shell script
curl -fsSL https://raw.githubusercontent.com/weside-ai/weside-cli/main/scripts/install.sh | sh

# From source
go install github.com/weside-ai/weside-cli@latest

Pre-built binaries for Linux, macOS (Intel + Apple Silicon), and Windows are on the releases page.

Sign in and talk

weside auth login                # log in
weside companions list           # see your companions
weside companions select nox     # pick a default
weside chat -m "Hey, how are you?"
weside chat --stream -m "Tell me a story"

weside auth login opens a browser for a standard OAuth login (PKCE) — pick Google, Apple, or email there, same as signing in on the web or in the app. That’s the normal way in.

Note

weside auth login --dev and the WESIDE_TOKEN environment variable are developer/CI shortcuts — for headless machines and scripted pipelines where a browser isn’t available, not the everyday path.

What you can do

The CLI covers the full surface of your companion:

• Companions — weside companions list | show | create | select | update | delete
• Chat & threads — weside chat, weside threads list | show | delete; pipe with echo "Hi" | weside chat nox
• Memories & goals — weside memories search "query", weside memories list, weside goals list
• Provider & data residency — weside provider show | presets | set | byok
• Tools — weside tools discover and weside tools exec <name> '<json>'

Memory search is semantic, not keyword — “how does auth work” finds memories about authentication even without the word.

Built for scripts

Everything speaks --json, so the CLI drops cleanly into pipelines:

weside companions list --json | jq '.companions[0].name'
curl -H "Authorization: Bearer $(weside auth token)" https://api.weside.ai/api/v1/auth/me

Under the hood the save and tools commands talk to the same MCP server the we plugin uses. One companion, one API, three ways in.