Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Copado Developer ExtensionNew to Visual Studio Code? Get it now.
Copado Developer Extension

Copado Developer Extension

Copado Labs

|
2,493 installs
| (0) | Free
VS Code companion for the Copado Salesforce CLI plugin.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Copado CLI for Visual Studio Code

Ship Salesforce work with Copado without breaking flow. Copado CLI is the VS Code companion for the Copado Salesforce CLI plugin (sf copado …). Bind user stories, stay aligned with Git, and drive Copado from a dashboard built for daily delivery—not a separate toolchain bolted on after the fact.

Your CLI. Your org. Your repo. The extension runs the Salesforce CLI the same way you do in a terminal; Copado auth and plugin behavior stay where you already manage them.


Features

Copado dashboard (Activity Bar)

Open Copado in the Activity Bar for an accordion sidebar with live workspace context:

Plan Settings

Search and set Copado plan defaults (project, epic, feature, environments, sprint, release, theme, team, source credential) via the CLI.

Plan Settings panel

Connections

Copado org and default Salesforce org status, with Re-link and Switch actions.

Connections panel

Current Work

Bound user story, branch, last push, and one-click Push, Validate / Promote / Deploy, and Open in org.

Current Work panel

Dependency assistance

The Dependencies section helps identify metadata dependencies introduced by the changed files on your current branch.

  • Calculates dependency data with sf copado dependency get --from-changes --json.
  • Marks dependencies as Missing when they are not already present, tracked, or staged locally.
  • Shows what introduced each dependency, so you can trace it back to the changed metadata.
  • Lets you View a dependency by resolving it locally or retrieving it to a temporary location and opening the file.
  • Lets you Add a missing dependency by retrieving the metadata and staging the resolved file paths with Git.
  • Re-evaluates dependency status when Git staging/index state changes, so newly staged dependencies move out of the missing list.

Dependencies panel

My Work

User-story list driven by presets in .copado/queries.json; pick a preset and apply a story from the list.

My Work list panel

Jobs and debugging

  • Open job executions in Salesforce, list steps, or download logs to a temp file.
  • Copado: Show output streams CLI stdout/stderr and timings to the Copado channel.
  • Optional copado.traceWorkspaceRefresh logs dashboard refresh phase timings for performance debugging.

Recent Jobs panel

Source Control integration

In the Source Control view, when the workspace is trusted and sf is available:

  • Copado ribbon — work-context summary (story + branch) and a shortcut to Quick actions.

SCM Copado panel

  • Pre-push checklist — read-only gates for .forceignore, default org, and story binding before you push.

SCM pre-push checklist

The Git SCM title bar adds Copado shortcuts when context allows:

  • Set story
  • Push story
  • Submit story (validate / promote / deploy)
  • Open story in org
  • Show story
  • Auth get

SCM action icons

Quick actions

Copado: Quick actions opens a searchable menu of common sf copado commands with streamed output in the Copado output channel

Status bar

Status bar

A compact status item shows the bound story and current branch; click it for Quick actions.

Status bar


Requirements

  • Visual Studio Code 1.85.0 or higher
  • Salesforce CLI (sf) installed and available to VS Code’s environment
  • Copado CLI plugin for sf, installed and authenticated per your organization’s Copado guidance
  • A trusted workspace with at least one folder open
  • Git repository with a .copado directory for story binding and queries (same layout you use for sf copado story set in a terminal)

Getting started

  1. Install Copado CLI from the Extensions view (search for Copado CLI) or install from a VSIX distributed by your admin.
  2. Open the Salesforce project folder you use with Git and Copado.
  3. Trust the workspace when VS Code prompts.
  4. Click Copado in the Activity Bar to open the dashboard.
  5. Use Source Control for the Copado ribbon and pre-push checklist beside Git.
  6. Run Copado: Set story (palette or SCM title bar) to bind your user story.

Multi-root workspaces

When a command needs a working directory, the extension asks which folder to use. To pin the Copado repo without reordering folders, set copado.cliWorkingDirectory to the absolute path of that Git root—the dashboard, SCM commands, and sidebar actions use the same path as sf copado … in a terminal opened there.

Story list presets

Create or edit .copado/queries.json in your repo (or run Copado: Open .copado/queries.json from the dashboard). Presets drive the My Work story list; switch presets from the dropdown in that section.


Extension settings

Search Copado in VS Code Settings.

Setting Description
copado.salesforceCliPath Path to the Salesforce CLI binary (sf). Leave empty to resolve sf / sf.cmd from PATH.
copado.cliWorkingDirectory Absolute path to the Git repository root where .copado lives. When empty, the first workspace folder is used. Supports ~ for the user home directory.
copado.traceWorkspaceRefresh Log Copado workspace refresh phase timings to the Copado output channel (for performance debugging).

Typical workflow

Trust workspace → Link Copado auth → Set default org → Set story → Develop & commit in Git
→ Review pre-push checklist → Push story → Submit (validate / promote / deploy) → Monitor jobs

Use the dashboard for connections, current work, dependencies, and job history; use Source Control for Git-native shortcuts and the checklist.


Troubleshooting

Symptom What to try
Commands grayed out or views hidden Trust the workspace, open a folder, and ensure sf is on PATH or set copado.salesforceCliPath.
Wrong repo in a multi-root workspace Set copado.cliWorkingDirectory to your Copado Git root.
Story list empty Add presets to .copado/queries.json and refresh; confirm Copado auth and org context.
Dependencies empty Confirm the story is bound and the branch has changed files; no changed files produce an empty state.
Slow dashboard refresh Enable copado.traceWorkspaceRefresh and inspect the Copado output channel.
CLI errors Run Copado: Show output or reproduce via Copado: Quick actions.

Documentation

See your organization’s Copado CLI and DevOps documentation for plugin installation, authentication, user-story workflows, and CI/CD patterns. This extension surfaces those capabilities inside VS Code; it does not replace Copado’s CLI or platform docs.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft