VibeControls is one service with several ways in. They all sign in with the same Burdenoff account, act on the same workspaces, and are permission-checked the same way, so you can start something in one and pick it up in another.
Apps
Developer and machine clients
| Client | Status | Install | Read more |
|---|
Agent (vibe) | Available | npm install -g @vibecontrols/agent | Installing the Agent |
CLI (vibecontrols) | Available | npm install -g @vibecontrols/cli | CLI Reference |
| MCP server | Available | npx -y @vibecontrols/mcp | MCP Server |
| Node SDK | Available | npm install @vibecontrols/sdk | Node SDK |
| Python SDK | Available | pip install vibecontrols-sdk | Python SDK |
| VS Code extension | Available | code --install-extension AlgoshredTechnologies.vibecontrols | VS Code Extension |
| Browser extension | Coming soon | Not in the Chrome Web Store yet | Browser Extension |
What is the same everywhere
- One account. Sign in once per app with your Burdenoff account. Multi-factor authentication and single sign-on work the same in every app.
- Same permissions. Every app calls the same API, and your roles decide what each one can do. See Roles and Permissions.
- Same notifications. Notifications you receive in the web app also reach the desktop app, and any device where you turned on push. See Push notifications.
Next steps