Verdog

Appearance

Getting started ​

Install the command-line client and VS Code extension, then execute and modify the Countdown workflow.

Requirements ​

  • VS Code 1.106 or later.
  • Python 3.12 or later.
  • Git.

Install the CLI ​

The verdog-cli package provides the verdog command and depends on the separate verdog-runtime package.

Install the CLI with uv:

sh
uv tool install verdog-cli
verdog --help

The second command should print the CLI usage. Verify that it also works in VS Code's integrated terminal, since the extension invokes this executable. If the command is not found, run uv tool update-shell, then restart the terminal and VS Code.

Install the VS Code extension ​

Install Verdog from the Visual Studio Marketplace. Its extension identifier is verdog.verdog-vscode. It provides the workflow canvas, diagnostics, and the Runs view.

Run the example ​

Continue with Countdown. The walkthrough clones a complete project, prepares its dependencies with verdog sync, checks the workflow, and executes it. It then introduces a small change to the input and shows how to inspect the result.

Create a new project

After working through the example, run Verdog: New Project from the Command Palette. Select an empty directory and specify a project name and Python package name, such as demo.example. The initial workflow connects its entry directly to its exit. See Project structure and Visits for the generated files and authored implementations.

Service use and data ​

Graph generation and verification use the hosted service and send declared project files, including pinned dependencies. Opening or refreshing a graph in a trusted workspace also sends project manifests for structural termination analysis; Restricted Mode disables this automatic analysis.

Python type checking and workflow execution run locally. Agent nodes may send prompts and other context to their configured provider. The example specifies its provider setup before the first agent invocation.

Compiler operations require no sign-in. Catalogue access uses GitHub sign-in, which is separate from provider authentication. See Permissions and Logging for access requirements and execution artifacts.