Getting Started
This page walks you through installing RunForge, preparing a dataset, and running your first deterministic training session.
Prerequisites
Section titled “Prerequisites”- VS Code 1.85 or later
- Python 3.8+ with
scikit-learn,joblib, andnumpy - A CSV dataset with a column named
label
Installation
Section titled “Installation”From the Marketplace
Section titled “From the Marketplace”Search for “RunForge” in the VS Code Extensions panel, or install from the VS Code Marketplace.
From Source
Section titled “From Source”git clone https://github.com/mcp-tool-shop-org/runforge-vscode.gitcd runforge-vscodenpm installnpm run compileThen press F5 in VS Code to launch the Extension Development Host with RunForge loaded.
Prepare Your Dataset
Section titled “Prepare Your Dataset”RunForge expects a CSV file with:
- A column named
label— this is what the model will predict - All other columns as numeric features
- No header-less data
Rows with missing values are dropped automatically (the count is logged).
Your First Run
Section titled “Your First Run”- Open a workspace containing your CSV file
- Open the Command Palette (
Ctrl+Shift+P) - Run
RunForge: Train (Standard)for a quick run, orRunForge: Train (High Quality)for a more thorough session - Training runs in a Python subprocess — you’ll see progress in the VS Code output panel
What Happens During a Run
Section titled “What Happens During a Run”- The dataset is validated (label column must exist, values must be numeric)
- A SHA-256 fingerprint of the dataset is computed
- Data is split 80/20 train/validation (deterministic, stratified)
- The pipeline is fit (StandardScaler + selected classifier)
- Metrics are computed against the validation set
- Interpretability features are extracted (feature importance or coefficients, depending on model)
Where Artifacts Go
Section titled “Where Artifacts Go”All run artifacts are saved under .ml/runs/<run-id>/:
| File | Contents |
|---|---|
run.json | Metadata — run ID, dataset fingerprint, git SHA, Python path, extension version, model family, profile |
metrics.json | Core metrics: accuracy, num_samples, num_features |
metrics.v1.json | Detailed per-profile metrics |
artifacts/model.pkl | Trained scikit-learn pipeline |
artifacts/feature_importance.v1.json | Feature importance (RandomForest only) |
artifacts/linear_coefficients.v1.json | Coefficients (LogisticRegression, LinearSVC) |
artifacts/interpretability.index.v1.json | Unified interpretability index |
Choose a Model
Section titled “Choose a Model”Configure the model family in VS Code settings:
{ "runforge.modelFamily": "random_forest"}Available models: logistic_regression (default), random_forest, linear_svc.
Choose a Training Profile
Section titled “Choose a Training Profile”Profiles provide pre-configured hyperparameter overrides:
{ "runforge.profile": "thorough"}Available profiles: default, fast, thorough. See Reference for details.
Workspace Trust
Section titled “Workspace Trust”RunForge spawns Python from runforge.pythonPath (a workspace-settable path). To prevent an untrusted workspace from inducing RunForge to execute arbitrary Python, every spawn goes through VS Code’s workspace trust guard. Grant trust via the Manage Workspace Trust UI when prompted; without it, training and other Python-spawning commands return a structured error.
Cancel a Run
Section titled “Cancel a Run”While training is running, fire RunForge: Cancel Active Training from the Command Palette. RunForge sends SIGTERM to Python and gives it a 5-second window to write a durable .cancelled marker before falling back to SIGKILL. See Cancel and Recovery for the full state machine.
Inspect Results
Section titled “Inspect Results”After training, use these commands from the Command Palette:
RunForge: Browse Runs— browse all runs with quick actionsRunForge: View Latest Metrics— see detailed accuracy, precision, recall, F1RunForge: View Latest Feature Importance— see which features matter (RandomForest)RunForge: View Latest Linear Coefficients— see model coefficients (linear models)RunForge: Inspect Model Artifact— see pipeline structureRunForge: Export Latest Run as Markdown— save a formatted summaryRunForge: Recover Index— re-append orphaned runs intoindex.jsonif a write failed (see Cancel and Recovery)
Next Steps
Section titled “Next Steps”See the Reference for the full list of commands, settings, and the interpretability framework. For lifecycle controls (cancel, recovery, workspace trust), see Cancel and Recovery.