RunReady

Not sure what command runs your project? Click RunReady.

RunReady finds the correct project folder, checks whether dependencies are ready, and fills the complete command in your terminal. It also copies the command to your clipboard.

Nothing runs automatically. You review the command and press Enter.

Before RunReady

With RunReady

How it works

1. Open your project in VS Code.
2. Click RunReady in the status bar.
3. RunReady opens or reuses the terminal and fills the complete command.
4. Review it and press Enter when you are ready.

The generated command can include:

• cd to the correct project directory.
• A dependency installation step when dependencies appear to be missing.
• The detected command that starts the project.

Built-in project support

• Node.js and package scripts using npm, pnpm, Yarn, or Bun.
• React, Vite, Next.js, Nuxt, SvelteKit, Astro, Angular, Electron, Express, and VS Code extensions.
• Python, FastAPI, Flask, and Django, including common nested backend layouts.
• Rust/Cargo, Go, Java/Maven, Java/Gradle, .NET and F#.
• Flutter/Dart, PHP/Composer/Laravel, Ruby/Bundler/Rails.
• Docker Compose, C/C++ with CMake, and static websites.

Detection is based on project files, declared scripts, dependencies, and common entry points. If RunReady cannot find enough evidence, it will not invent a command.

Unsupported or private toolchains

Add a .runready.json file to a project root:

{
  "name": "My worker",
  "projectType": "Private toolchain",
  "command": "acme-worker serve",
  "setupCommands": ["acme-worker install"],
  "dependencyState": "unknown"
}

dependencyState can be ready, missing, managed, or unknown. Custom setup commands are included when the state is missing or unknown and RunReady: Include Dependency Install is enabled.

For multiple choices, replace command with:

{
  "commands": [
    { "label": "Development server", "command": "acme dev", "recommended": true },
    { "label": "Production mode", "command": "acme start" }
  ]
}

Dependency checks

For Node projects, RunReady verifies directly declared packages in node_modules, including hoisted workspace packages. For Python projects, it compares direct requirements with installed distribution metadata in .venv or venv. Ecosystems such as Cargo, Go, Maven, and Gradle resolve dependencies through their own runners.

Privacy and safety

RunReady works locally and does not send project data to an AI service. It fills commands without executing them. Project scripts can still run arbitrary code, so always review the command before pressing Enter.

If the status bar is hidden, enable View > Appearance > Status Bar. You can also run RunReady: Show Status Bar Button.

Feedback and author

Report a wrong or missing command through GitHub Issues. See the support guide for the details that make a report useful.

Created by Shahan Samar - GitHub | LinkedIn