Install
Shell (macOS / Linux)
https://cdn.lymo.jp/manifest/latest.json, downloads the matching tarball from the Lymo CDN, verifies its SHA-256 checksum, and installs lymo into ~/.local/bin. Prints a PATH hint if needed.
Override the install directory — note the env var belongs on the sh side of the pipe, not the curl side:
Verify
First run — lymo setup
lymo setup is the guided onboarding wizard. It signs you in, asks rep vs. manager, runs lymo doctor, and suggests a first command.
lymo login and lymo doctor are the non-interactive equivalents:
--no-browser to either command to print the URL instead of auto-opening.
The config file lives at ~/.config/lymo/config.json with 0600 permissions. Override with $LYMO_CONFIG_DIR or $XDG_CONFIG_HOME.
Core commands
List calls and deals
Inspect a call
Commands that take a call accept a UUID orlatest (the most recent call in your org).
Export
Bundle multiple sections into a single file. Defaults:--sections summary,checklist, --format md.
summary, transcript, checklist, events. Formats: md, json.
MCP server (agent integration)
Register the CLI as an MCP server so agent clients can access Lymo data:claude-desktop, claude-code, codex, cursor, gemini-cli, windsurf, opencode.
Run the server manually over stdio (your client normally does this for you):
Shell integration
lymo setup configures shell integration as part of onboarding. To manage it manually:
| Shell | Completion file | Activation |
|---|---|---|
| zsh | ~/.zsh/completions/_lymo | fpath + compinit block in ~/.zshrc |
| fish | ~/.config/fish/completions/lymo.fish | autoloaded by fish — no rc edits |
| bash | ~/.local/share/bash-completion/completions/lymo | [ -f X ] && source X in ~/.bash_profile (macOS) or ~/.bashrc (Linux) |
lymo shell install also adds the install dir (~/.local/bin by default, override with LYMO_INSTALL_DIR) to $PATH if it isn’t already there. Pass --no-path or --no-completion to opt out.
If you’d rather not have Lymo manage rc files, pipe the completion script directly (the gh / kubectl pattern):
exec $SHELL (or open a new terminal) to pick up the changes.
Output formats
Every command supports three rendering modes for the same underlying envelope:| Flag | Format | Use case |
|---|---|---|
| (none) | Colored ANSI | Humans reading at a prompt |
--json | JSON envelope | Scripts and pipelines |
--md | Markdown | AI agent context |
Profiles
Named profiles let you switch between organizations without re-authenticating each time.--profile is a global flag — attach it to any command.
default.
Troubleshooting
/v1/members/me), and which MCP clients the server is wired into.
If lymo doctor fails on auth, re-run lymo login. If it fails on connectivity, check that $LYMO_PLATFORM_BASE_URL (if set) points at a reachable Lymo deployment.