> ## Documentation Index
> Fetch the complete documentation index at: https://docs.virtualityhub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Sign up, describe what you need, and ship your first V-Run Python workflow in minutes — with AI code generation, built-in tests, and a single-commit publish.

## Get started

Follow these steps to go from zero to a running workflow.

<Steps>
  <Step title="Sign up">
    Create an account at [run.virtualityhub.com](https://run.virtualityhub.com). You can sign up with email or Google.
  </Step>

  <Step title="Create a workflow">
    From the dashboard, click **New Workflow**. You will land in the workflow editor — a browser-based IDE with a Monaco code editor, AI chat panel, and run controls.
  </Step>

  <Step title="Write or generate code">
    You can write Python directly in the editor, or open the **AI Chat** panel and describe what you need. For example:

    ```
    Scrape the top 5 headlines from Hacker News and return them as JSON
    ```

    The AI will generate production-ready Python code and place it in the editor.
  </Step>

  <Step title="Check the config">
    The AI also generates a **config.yaml** that declares inputs, outputs, and triggers. Switch to the **Config** tab to review it. Inputs become a form that users fill out before each run.

    ```yaml theme={null}
    inputs:
      url:
        type: str
        required: true
        description: "Target URL to scrape"
      max_items:
        type: int
        default: 5
    ```

    Adjust the config if needed — for example, change a default value or mark a field as optional.
  </Step>

  <Step title="Run and test">
    Click **Run** to execute your workflow in a secure cloud sandbox. View stdout, stderr, and outputs in the bottom panel.

    Switch to the **Test** tab, write pytest tests, and click **Run Tests** to verify your logic before publishing.
  </Step>

  <Step title="Commit to publish">
    When you are happy with the results, open the **Version Control** tab, enter a commit message, and click **Commit**.

    Committing snapshots your code and makes the workflow live immediately — there is no separate deploy step. API triggers and scheduled runs always use the latest commit.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Workflows" icon="diagram-project" href="/concepts/workflows">
    Understand the anatomy of a workflow.
  </Card>

  <Card title="Triggers" icon="bolt" href="/concepts/triggers">
    Learn about manual, API, and scheduled triggers.
  </Card>

  <Card title="Testing" icon="flask-vial" href="/features/testing">
    Write and run tests for your workflows.
  </Card>

  <Card title="Version control" icon="code-commit" href="/features/version-control">
    Commit, browse history, and restore previous versions.
  </Card>
</CardGroup>