Getting Started
Choose your path and get up and running in minutes. No configuration required.
Choose Your Path
Common Issues
Authentication failed or token not found?
Run `npx vibex-sh login` to authenticate. This opens your browser and saves the token to `~/.vibex/config.json`. If you're using the SDK, make sure the `VIBEX_TOKEN` environment variable is set.
How do I reuse an existing session?
Use the `-s` or `--session-id` flag: `echo '{"data": 123}' | npx vibex-sh -s your-session-id`. The session ID is shown when you first create a session.
SDK not working in production?
Ensure `VIBEX_TOKEN` and `VIBEX_SESSION_ID` are set as environment variables. The SDKs are fail-safe and will silently disable if these are missing, so check your environment configuration.
Logs not appearing in the dashboard?
Check your internet connection first. The CLI requires an active connection to send logs. Also verify you're authenticated with `npx vibex-sh login`. For SDKs, check that environment variables are correctly set.
Can't install or run npx vibex-sh?
Make sure you have Node.js installed (version 14 or higher). If `npx` is not found, install Node.js from nodejs.org. You can also use `npm install -g vibex-sh` for a global installation.
What happens if I hit rate limits?
vibex.sh has two types of limits: MPS (messages per second) and monthly log volume. When MPS limits are exceeded, excess logs are dropped gracefully—your SDKs handle this automatically. When monthly volume is exceeded, new logs may be rejected until the next billing cycle. You'll receive notifications as you approach limits (80-90%). Upgrade your plan for higher limits.
Need More Help?
Check out our comprehensive documentation or reach out for support.