VibeControls
Overview & Onboarding2 illustrations

Install and Connect Your First Agent

A guided path from a one-line install command on your own machine to a registered, connected agent in your workspace.

These images are illustrations of the concept, not screenshots of the actual product.

Overview

Onboarding is where most developer platforms lose people, so this concept concentrates on the shortest credible path from nothing to a working agent. VibeControls is agent-based: a lightweight runtime installs on a machine you already use, and everything else in the product talks to that runtime. The two illustrated screens cover the two halves of that first step, installing on the machine and registering it with the workspace.

The problem is that connecting a laptop, a server or a build runner to a control plane usually means reading a setup guide, generating credentials somewhere else, opening a firewall and hoping the handshake works. The design compresses that into a copyable command, an optional version pin and a three-item checklist that names exactly what happens next, so a newcomer knows what to expect before they run anything.

The getting-started illustration presents the install page with two tabs, one for installation and one for command reference. The install card explains the prerequisite and links to full documentation, then offers the command itself across three package options, each in a code block with a copy control. A field beneath it lets a team pin a specific agent version rather than take the latest, which is what a platform team would want when rolling the agent out consistently. The numbered next steps describe starting the agent, taking the printed connection URL and key into the registration screen, and confirming the agent's status.

The add-agent illustration picks the story up inside the workspace. A modal opens over the agents list with a two-stage stepper, setup then validate. A collapsible panel repeats the install instructions so nobody has to go back, and the form itself asks for a display name, the target machine it belongs to, the connection URL and the agent key, with the key masked behind a reveal control. A link to create a new target covers the case where the machine is not registered yet, and the primary button submits and connects in one action.

Taken together the pair shows the intended shape of onboarding across VibeControls: the machine stays yours, the credential is generated locally, and the workspace holds only what it needs to reach the agent. Once that first agent is connected, the fleet views, sessions, projects and automation surfaces all have something to work with.

What this concept shows

  • An install page with separate installation and command-reference tabs
  • A single copyable install command offered in three package variants, each in a code block with a copy control
  • An optional field for pinning a specific agent version instead of taking the latest
  • A numbered next-steps checklist covering starting the agent, registering it and verifying its status
  • An add-agent modal with a two-stage setup and validate stepper
  • A collapsible install-instructions panel inside the registration form so the commands stay at hand
  • Form fields for display name, target machine, connection URL and agent key, with the key masked behind a reveal control
  • An inline route to create a new target when the machine is not yet registered

How it works

  1. Open the getting-started page and read the prerequisite note and the linked installation documentation.
  2. Choose an install variant, copy the one-line command and run it on the machine you want to manage.
  3. Optionally pin a specific agent version so the whole team installs the same build.
  4. Start the agent locally and note the connection URL and key it prints.
  5. Open the agents area, choose to add an agent, and complete the setup stage with a name, a target, the connection URL and the key.
  6. Submit and connect, then move to the validate stage and confirm the agent reports as online in the workspace.

Who it's for

  • Developers setting up their first machine on a developer control plane
  • Platform engineers standardizing agent rollout across a fleet
  • DevOps engineers connecting staging, production and build hosts
  • Team leads onboarding new engineers quickly
  • Educators and bootcamp instructors setting up reproducible environments

Illustrations

2 illustrations of this concept. Select one to view it full size.

Install the Agent

The install page offers a copyable command, an optional version pin and a short numbered checklist.

This illustration shows a getting-started page inside the workspace shell, with the standard grouped navigation on the left and search, organization and account controls across the top. The heading explains that the page installs and configures the agent command-line tool, and two tabs separate installation from command reference. An install card summarizes the prerequisite, notes that the agent is started with a single command after installation, and links out to the full installation documentation. Below it, a tabbed code block presents three install variants with one recommended by default, each shown as a monospace command with a copy control and a line confirming that no package manager is required. An optional field invites a specific agent version to be pinned, with a sample version as placeholder text. A numbered next-steps list closes the page, describing starting the agent, registering it from the agents area with the printed connection URL and key, and verifying its status.

Add Agent Wizard

A modal registers a running agent: name, target, connection URL and a masked agent key.

This illustration shows a registration modal layered over the agents area. A two-stage stepper marks setup as current and validate as next. A collapsible install-instructions panel sits at the top, listing the three package options and a copyable start command, with a line explaining that the connection URL and key printed by the agent go into the fields below. The form asks for a display name, a target chosen from a dropdown that shows the connection type alongside it, a connection URL, and an agent key rendered as masked dots with a reveal control and a short key prefix. An inline link offers to create a new target, and cancel and connect buttons close the form. Behind the modal, an agents table shows identifier and status columns with success, warning and error pills, above a bar chart panel with a legend of status chips. All values are sample data.

Topics

  • install developer agent
  • connect agent to workspace
  • one line agent install command
  • agent onboarding wizard
  • register agent api key
  • pin agent version
  • developer control plane setup
  • add agent to fleet
  • agent tunnel url
  • first time developer onboarding

Related concepts

All VibeControls concepts
Get started freeBrowse all concepts

We use cookies for essential site functions and, with your consent, for analytics to improve VibeControls. We don't use advertising or cross-site tracking cookies. See our Cookie Policy.

Preferences