Swylink
Swylink Docs
CLI setup, auth, keys, and IDE wiring
Recovery

Troubleshooting

When onboarding fails, the issue is usually session state, the MCP config path, or a wrong server URL. Check these in order.

Selected IDE
Cursor
.cursor/mcp.json
Swylink keeps the bridge explicit for this IDE by rendering --ide cursor and the correct MCP config path everywhere in the docs.
Section

No active CLI session

If setup token generation or exchange fails, your local auth state may be missing or expired.

  • Run `npx @swylink/cli auth whoami --api-base-url https://api.swylink.com`
  • If it reports no session, run `npx @swylink/cli auth login --api-base-url https://api.swylink.com` again
  • If login works but setup token generation or bridge start is blocked, verify the account has an active subscription in the dashboard
Section

IDE stays offline

The IDE usually stays offline when the config points to the wrong file or the command still resolves to localhost instead of your production backend.

  • Confirm the file path matches .cursor/mcp.json for the selected IDE
  • Confirm the config includes `--ide cursor`
  • If you expect production, keep `--server wss://api.swylink.com/ws` explicit in the generated config
  • Run `npx @swylink/cli doctor --ide cursor` to check for config conflicts
Minimal debug loop

Run the exact `start` command manually in a terminal first. If it connects there, the remaining issue is almost always the IDE config file or the process environment.

Section

Language and localization

The CLI supports multiple languages for output messages. Set the language explicitly if auto-detection is wrong.

  • Use `--lang pt` (or en, es, fr, de, zh) to override the detected language
  • You can also set the `SWYLINK_LANG` environment variable
Continue
Move through the full CLI path from auth to IDE connection, or jump back to the start if you are documenting onboarding for a new user.