sprouts-cli
v0.1.7
Published
Sprouts CLI — IDE pairing (opens browser to sign in)
Readme
sprouts-cli
Terminal helper for Sprouts IDE pairing: starts a device session, opens the browser to /ide/connect, and saves the IDE access token to ~/.sprouts/ide-token.json.
Usage
npx sprouts-cli loginTo clear the saved token (then run login again):
npx sprouts-cli logoutThe VS Code / Cursor extension stores its own copy in secret storage — use Command Palette → “Sprouts: Sign out” there too, or it may keep using the old session.
End-user install context (extension, MCP, troubleshooting) lives on the marketing site at /docs/ide — see website/app/docs/ide. Monorepo pointers: docs/PUBLIC_RESOURCES.md, docs/DEPLOYMENT.md.
API URL
Default is http://127.0.0.1:3000 (local Sprouts backend). Override if your API is elsewhere:
- Env:
SPROUTS_API_URL=https://your-tunnel.example.ngrok-free.dev npx sprouts-cli login - File:
~/.sprouts/config.json→{ "apiUrl": "https://..." }(no trailing slash)
When production is live at https://api.getsprouts.io, set one of the above or export SPROUTS_API_URL before running.
After login, the CLI prints install hints. Set SPROUTS_EXTENSION_URL to your published Open VSX page (e.g. https://open-vsx.org/extension/sprouts/sprouts-companion) so the message links correctly. Extension id for cursor --install-extension is sprouts.sprouts-companion.
For Cursor-only in-character chat (no server LLM), configure packages/sprouts-mcp and the repo skill .cursor/skills/sprouts/SKILL.md.
Publish
npm run build
npm publish --access public(Published as unscoped sprouts-cli because the @sprouts npm org was not available to the publishing account.)
