--- title: Usage Guide date: 2026-03-02 sidebar_position: 3 --- ## Creating a Pipeline 1. Use **File > New File > RocketRide Pipeline**, or click **+** in the RocketRide sidebar, to create a new `.pipe` file. 2. The visual editor opens automatically for `.pipe` files. 3. Drag components from the component palette onto the canvas. 4. Configure each component's properties in the properties panel. 5. Connect component outputs to inputs by drawing connections between lanes. 6. Save the file, changes are auto-saved. ## Running a Pipeline 1. Click the inline **Run** button on the pipeline item in the RocketRide sidebar, or press **Play** on the source node in the canvas. 2. The **Status** page opens with real-time execution monitoring. 3. Watch data flow through components, view completion metrics, and check for errors. ## Debugging a Pipeline 1. In the **Run and Debug** view, start the **RocketRide: Launch Pipeline** debug configuration (a `rocketride`-type launch configuration). 2. The debugger opens with breakpoint support. 3. Set breakpoints on components to pause execution. 4. Step through the pipeline and inspect variable values at each breakpoint. ## Attaching to a Running Pipeline If a pipeline is already running on the server: 1. In the **Run and Debug** view, start the **RocketRide: Attach to Pipeline** debug configuration. 2. The **Status** page opens and streams real-time data from the running pipeline. ## Deploying to Cloud 1. Open the pipeline's **DEPLOY** page from the RocketRide sidebar (the file view's DEPLOY page). 2. Configure deployment settings. 3. Click **Deploy** to push the pipeline to RocketRide.ai cloud. ## Cloud Connection — Custom Server Cloud mode connects to the production RocketRide Cloud by default. **Settings → Development** (or **→ Deployment**) → connection mode **Cloud** offers a custom-server opt-in for staging or self-hosted cloud environments: - **Use custom server** (per group: `rocketride..useCustomServer` plus `rocketride..cloudUrl`, where `` is `development` or `deployment`): when checked, a URL field appears and sign-in plus all traffic target that server. When unchecked (or the URL is empty), the default cloud server shown under the checkbox is used — the default comes from the extension's setting declaration, nothing is baked into the webview bundles. - **Save and reconnect:** the panel probes whichever server the form currently names (compatibility check), and **Sign In** deliberately uses the form's in-form value — the OAuth code is exchanged against the server you see, even before Save. Everything else (deploys, runs, checkout) rides the active connection, so after changing the server: save the settings, sign out, and sign in again to establish the session on the new server. - **Session/server mismatch:** the extension records which server each sign-in was made against. If the form later targets a different server, the Cloud panel says so and withholds the Subscribe/checkout surface until you sign in on the selected server — billing always happens on the server the panel describes, never a previous one. - **Invalid or unreachable URLs:** the compatibility probe fails and the panel reports that the configured server does not support RocketRide Cloud; sign-in stays available only for servers that pass the probe. An empty custom URL falls back to the default server. ## Pipeline Editor The visual editor provides: - **Component palette**: Browse and search available nodes (sources, LLMs, stores, etc.). - **Canvas**: Drag-and-drop workspace for arranging components. - **Properties panel**: Configure selected component settings (API keys, models, connection strings, etc.). - **Lane connections**: Draw lines between component output and input lanes to define data flow. ## Pipeline Execution Defaults Trace verbosity, the idle timeout (TTL), task arguments, and debug output for pipeline runs are configured once in **Settings → Pipeline** — they are workspace settings, not per-pipeline options: - **Pipeline Trace Level** (`rocketride.pipelineTraceLevel`, default `full`): how much execution-trace data the engine emits — `full`, `summary`, `metadata`, or `none`. Higher levels populate the **Flow** and **Trace** tabs, but `full` inlines entire payloads (including images), which can noticeably slow runs that process large images. - **Pipeline TTL** (`rocketride.pipelineTTL`, default `900` = 15 minutes): how long the engine keeps a pipeline alive without activity before stopping it. Fixed choices from 15 minutes to 8 hours, plus "Run forever or until you stop it" (`0` = no timeout). - **Task Arguments** (`rocketride.taskArguments`, default empty): additional command-line arguments passed to each pipeline task process. The engine splits the string using shell parsing rules, so quoted paths are preserved. - **Pipeline Debug Output** (`rocketride.pipelineDebugOutput`, default `false`): appends `--trace=debugOut` to the task arguments (unless they already contain a `--trace=` flag) for detailed task trace logging. The extension host reads these from the workspace settings and passes them to the engine on each `run`/`restart` (the `status:pipelineAction` message carries only the action and source). The engine process itself starts with no extra flags — these settings apply per task, not to the server. ## `.env` Auto-Sync After a successful engine connection, the extension syncs the workspace `.env` only for the **development** connection group using a self-hosted mode (local, Docker, service, or direct/on-prem connection). It writes the resolved `ROCKETRIDE_URI` (including a dynamic local port when applicable) and `ROCKETRIDE_APIKEY`, preserves existing comments and variables, and does not rewrite the file when its contents are already current. The RocketRide **Python SDK** reads the workspace `.env` automatically from its process working directory; the TypeScript SDK and CLIs read only process environment variables, so export the values first (for example, `set -a; source .env`). Cloud connections are not synced because their OAuth token is not an SDK API key. Deployment connections, workspaces with no folder open, and unreadable `.env` files are also skipped; a sync failure never affects the connection itself. Keep `.env` gitignored. The extension never automatically removes these keys: disconnecting, engine exit, or switching to cloud leaves the last-synced values in place. Remove them by hand if you no longer want them. Each development-group self-hosted connection syncs again, so a hand-edited `ROCKETRIDE_APIKEY` is overwritten on the next successful connection. ## Monitoring Execution The **Status** page shows: - **Component status**: Pending, running, completed, or failed indicators for each component. - **Data flow**: Visual representation of data moving through the pipeline. - **Metrics**: Completion rates and timing charts. - **Errors**: Detailed error messages and logs for failed components. ## AI-Assisted Development When enabled, the Copilot and Cursor integrations provide: - Pipeline structure suggestions based on your use case. - Component configuration recommendations. - Error diagnosis and fix suggestions. - Pipeline optimization tips. Enable these in settings under `rocketride.integrations.copilot` and `rocketride.integrations.cursor`.