Glide

Your wallets, USD and EUR bank accounts, and cross-border payments in your terminal.

Install

With Node 20.12 or newer:

npm install -g @glideco/cli
glide

Or run npx @glideco/cli.

Without Node, install a standalone binary to ~/.local/bin:

curl -fsSL https://glide.co/install.sh | sh

For a system install, use sh -s -- --system. The script verifies SHA256 checksums from the public glide-co/cli releases. Pin a release with GLIDE_CLI_VERSION=cli-v0.2.0.

On macOS or Linux, brew install glide-co/tap/glide uses the same binaries from the glide-co/homebrew-tap repository. The tap setup and checksum template are documented in packaging/homebrew/README.md.

First run

Run glide, press Enter, and sign in in your browser. Your browser asks you to approve access to this terminal. The CLI waits, then shows your full wallet addresses and the next steps. Use the arrow keys and Enter to choose.

$ glide
Welcome to Glide.
Your wallets, bank accounts and payments in one place.
Press Enter to sign in with your browser
[Enter]
Sign-in code: BCDF-2345
https://glide.co/dashboard/agent-connect?code=BCDF-2345
Waiting for browser sign-in
Signed in as [email protected]

Glide
Alex ([email protected])

Here's your EVM wallet:
0x1234567890123456789012345678901234567890

Here's your Solana wallet:
11111111111111111111111111111111

USD account: not open yet
EUR account: not open yet

What would you like to do?
> Get a USD bank account
  Get a EUR bank account
  Make a cross-border payment
  Quit

Each option leads to verification if you have not completed it. “Start verification now?” defaults to Yes. Enter opens the hosted verification page and the CLI waits for its status. If it is under review, run glide status later. After approval, bank accounts provision through the existing onboarding flow. Existing accounts appear with masked details on home; glide account shows full details and can download your confirmation letter.

For a payment, choose a saved bank recipient or enter a new name, then enter what they should receive and their currency. Glide opens the bank-transfer page with these details filled in. Review the live fee and exchange rate and approve with your browser wallet before sending. The CLI cannot send funds. Personal bank payouts do not yet have a pending-action browser approval API, so quotes, wallet approval and the final payment status remain in the web app.

Ctrl-C quits cleanly. Browser links are also printed for remote terminals. Bare glide in CI or without a TTY prints help. Output respects NO_COLOR.

Commands

glide login                      Sign in with your browser
glide home                       Wallets and the interactive menu
glide account                    Full USD and EUR account details
glide account --currency EUR     Show one account
glide account --letter           Save the confirmation letter
glide status                     Verification and masked account status
glide pay                        Guided bank payment with browser approval
glide connect                    Browser pairing for AI tools
glide onboard                    Install AI tool configurations
glide logout                     Remove saved local sessions
glide dev --help                 Self-host and developer tools
glide --help                     Customer commands
glide --version                  CLI version

Prompt-free equivalents (browser actions still require a human):

glide login --yes
glide home --once
glide home --usd --yes
glide home --eur --yes
glide pay --recipient "Alex" --amount 100 --currency EUR --yes

--yes starts sign-in or verification. It never approves a payment. --api http://localhost:3000 selects a local server for sign-in. Saved sessions are bound to that server. glide signup keeps the older email signup path.

Developer commands live under glide dev: demo, doctor, migrate, docs:env, partner submit, consistency, deploy, secrets sync, policy lint, vault status, and audit export. Their old invocations work in 0.2.0 with a one-line move notice.

Browser sessions use ~/.glide/credentials.json, the same path as connect, written atomically with mode 0600. Customer credentials grant read access to your own home/account only. They do not authenticate to money-moving APIs. The older email session is in ~/.glide/onboarding.json. logout removes both.

Development and releases

pnpm --filter @glideco/cli check-types
pnpm --filter @glideco/cli test
pnpm --filter @glideco/cli lint
pnpm --filter @glideco/cli build
pnpm --filter @glideco/cli build:binaries

The ESM bundle and standalone binaries include every dependency. There are zero runtime dependencies. See the CLI changelog for release notes and the recorded mock flows for a repeatable walkthrough. Version 0.2.0 is already set in package.json.

After merging the release-ready PR, from the updated main branch, release 0.2.0 with one line:

git tag cli-v0.2.0 && git push origin cli-v0.2.0

.github/workflows/cli-release.yml checks that the tag matches package.json, checks types, tests and lint, builds and smoke-tests the bundle and five standalone binaries, verifies SHA256SUMS.txt, uploads the assets to glide-co/cli releases, and publishes @glideco/cli to npm. Manual dispatches build and validate, including npm publish --dry-run, without publishing either channel.

npm trusted publishing is configured for organization glide-co, repository glide-mono, and workflow filename cli-release.yml. The workflow uses a GitHub-hosted runner, Node 22, npm 11.5.1 and id-token: write for OIDC. No npm token is required. See npm's trusted publishing requirements.

Before pushing the release tag, configure CLI_RELEASE_TOKEN on the source repository with Contents: read and write on the public glide-co/cli repository. The workflow checks this prerequisite before building. GITHUB_TOKEN cannot publish to another repository. The first tagged run initializes an empty public release repository with a small README before uploading assets. After the release exists, update Formula/glide.rb in glide-co/homebrew-tap with the matching checksums, following the tap instructions.

License

MIT. See LICENSE.