# Onboarding Guide

{% hint style="info" icon="user-gear" %}
**Permission Requirement**

Platform Admin role
{% endhint %}

## Prerequisites

Before creating your first Vibe-Shift pipeline, confirm the following:

* An Opsera account.
* A GitHub, GitLab, or Bitbucket repository containing your vibe-coded app
* A GitHub Personal Access Token with the following scopes:
  * `repo` — full repository access
  * `admin:repo_hook` — webhook registration for auto-deploy

> **Note on token scopes:** Your GitHub PAT must include both `repo` and `admin:repo_hook`. Without `admin:repo_hook`, the GitOps webhook cannot be registered and pushes to `main` will not trigger the pipeline automatically.

## Create Your First Vibe-Shift  Pipeline

<figure><img src="/files/SZPoLRcFdDyhZglAaB5L" alt=""><figcaption></figcaption></figure>

Follow these steps to go from a Git repo to a deployed production app.

{% stepper %}
{% step %}

### **Step 1 — Sign in to Opsera Agents Portal**

Navigate to **agent.opsera.ai** and sign in with your credentials. Confirm you see the Platform Admin badge in the top-left navigation.
{% endstep %}

{% step %}

### **Step 2 — Open the Vibe-Shift dashboard**&#x20;

Click **Vibe-Shift** from the left navigation.
{% endstep %}

{% step %}

### **Step 3 — Create a new pipeline**&#x20;

&#x20;Click `+ New Vibe-Shift Pipeline` in the top right. Enter a pipeline name (e.g. Task Management App). Choose your authentication method:

* **Personal Access Token** (recommended) — paste your GitHub PAT
* **GitHub App** — use if your org enforces GitHub App auth

Required scopes: `repo`, `admin:repo_hook`. Click **Next**.

Search your repositories from the dropdown, or paste the repo URL directly. Then set:

* **Branch** — default is `main`
* **App Name** — becomes the deployed container/app identifier
* **Environment** — select `dev` or `prod`

Auto-deploy is enabled by default. A GitHub webhook is registered automatically — every push to `main` triggers the full pipeline without any manual action. Expand **Advanced Options** for additional configuration if needed. Click **Create**.
{% endstep %}

{% step %}

### **Pipeline runs automatically**&#x20;

On creation, the pipeline kicks off immediately. Six autonomous steps run in sequence (see below). Monitor progress in real time on the pipeline detail view. On success, the pipeline shows a green Success badge and Healthy deployment status.
{% endstep %}

{% step %}

### One Command Deploy

&#x20;If using Claude Code, Cursor or VS Code, you can use it to deloy your app in the IDE chat. Vibe-Shift handles the rest autonomously via MCP Protocol.
{% endstep %}

{% step %}

### View the Vibe-Shift Dashboard

Once your pipeline is created, it kicks off automatically. Here is how to read the interface:

* The Execution View (Pipeline Flow)
* The Insights View (Analytics)

  [Read more here](/vibe-shift/vibe-shift-dashboard.md)
  {% endstep %}
  {% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.agents.opsera.ai/vibe-shift/onboarding-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.