Skip to main content

VibeDeck Dashboards

VibeDeck is your personal action dashboard inside VibeControls. It is a collection of tiles — each tile represents a command, script, or webhook that you can execute with a single click.

Think of VibeDeck as a launchpad for your most frequently used operations. Instead of opening a terminal and typing the same commands over and over, you put them on a VibeDeck tile and click.

Navigate to VibeDeck in the VibeControls sidebar to access your dashboard.

What VibeDeck Is For​

  • One-click deploys: A tile that runs your deploy script on the right agent
  • Quick health checks: A tile that pings your services and shows output
  • Shared runbooks: A VibeDeck your whole team can open to run standardized operations
  • Webhook triggers: A tile that fires a webhook to kick off an external workflow
  • Script runners: A tile that executes a parameterized script and streams output back

Creating a VibeDeck Layout​

A VibeDeck is a named layout containing one or more tiles. You can have multiple VibeDeck layouts for different projects, contexts, or teams.

Creating a New VibeDeck​

  1. Navigate to VibeDeck in the sidebar
  2. Click New VibeDeck
  3. Enter a name and optional description
  4. Optionally associate it with a vibe — this makes it easier to find when browsing vibe-related actions
  5. Click Create

Your new VibeDeck opens in edit mode, ready for you to add tiles.

Adding Widgets (Tiles)​

Each tile on a VibeDeck is a widget. Widgets come in three action types:

Widget TypeWhat It Does
CommandRuns a shell command on a selected agent
ScriptExecutes a script file (or inline script) on an agent
WebhookFires an HTTP POST to a configured URL

Adding a Command Widget​

  1. In VibeDeck edit mode, click Add Widget
  2. Choose Command
  3. Fill in:
  • Label — what appears on the tile button (e.g. "Restart Dev Server")
  • Agent — which agent runs the command
  • Command — the shell command to execute (e.g. pm2 restart all)
  • Working directory (optional)
  • Description (optional)
  1. Click Save Widget

Adding a Script Widget​

  1. Click Add Widget → Script
  2. Fill in:
  • Label — tile button text
  • Agent — which agent runs the script
  • Script — write an inline script or point to a file path on the agent
  • Shell — which shell to use (bash, sh, zsh, etc.)
  1. Click Save Widget

Adding a Webhook Widget​

  1. Click Add Widget → Webhook
  2. Fill in:
  • Label — tile button text
  • URL — the webhook endpoint to call
  • Method — typically POST
  • Headers (optional) — any additional HTTP headers
  • Body (optional) — JSON payload to send
  1. Click Save Widget

Arranging Tiles​

In edit mode, drag tiles to rearrange them on the grid. The layout is flexible — tiles can be placed in any order.

Click Done editing to save the layout and switch to view mode.

Running a Tile​

In view mode, click any tile to execute it.

  • Command and Script tiles: Output streams in a popup panel. You can see the live output as it runs. When execution completes, a success or error status is shown.
  • Webhook tiles: A spinner shows while the HTTP request is in flight. The result (HTTP status code and response) is shown once the request completes.

All tile executions are logged. Click the History icon on a tile to see past executions, their timestamps, and their output.

VibeDeck layouts can be shared via a public link — recipients do not need a VibeControls account to view the dashboard.

  1. Open the VibeDeck you want to share
  2. Click Share (link icon in the header)
  3. Toggle Public link on
  4. Copy the generated URL

The public URL looks like: https://app.vibecontrols.com/vibecontrols/deck/<token>

Anyone with this link can view the VibeDeck layout and see tile labels and descriptions. By default, public viewers cannot execute tiles — they see the tiles in a read-only state.

Allowing Public Execution​

If you want public viewers to be able to run tiles:

  1. Open the Share settings
  2. Enable Allow execution from public link
  3. Set an expiry for the link (strongly recommended)

⚠️ Warning — public execution grants remote command execution. Anyone with the URL can run any tile on this deck — not just the tile you intended to share — on your agents, with no authentication. Treat the link like a long-lived credential: always set an expiry, share it through trusted channels only, and revoke the link as soon as it is no longer needed.

In Share settings, toggle Public link off. The previous URL immediately stops working. You can generate a new link at any time.

Embed Codes​

You can embed a VibeDeck in an external page (an internal wiki, a web dashboard, or a documentation site) using an HTML iframe embed code.

  1. Open the VibeDeck
  2. Click Share → Embed
  3. Copy the iframe snippet
  4. Paste it into your external page
<iframe
  src="https://app.vibecontrols.com/vibecontrols/deck/<token>"
  width="800"
  height="600"
  frameborder="0">
</iframe>

The embedded VibeDeck respects the same public/execution permissions as the shared link.

Organizing Multiple VibeDeck Layouts​

If you have many VibeDeck layouts, keep them organized by:

  • Naming by context: "Frontend Deploy", "Database Ops", "Staging Checks"
  • Associating with vibes: Attach each VibeDeck to the vibe it belongs to — then it appears on that vibe's detail page for quick access
  • Pinning favorites: Pin frequently used VibeDeck layouts at the top of the list

Tips​

  • Keep tile labels short and action-oriented: "Deploy to staging", "Run tests", "Clear cache" — not "This button will run the deploy script for the staging environment".
  • Add a description to tiles that are not obvious — descriptions appear as tooltips when you hover over a tile.
  • For tiles that can have destructive effects, add a distinctive visual — use the tile description to include a warning like "⚠ Restarts the database".
  • Share a VibeDeck with your team instead of maintaining a shared runbook document — the VibeDeck IS the runbook.