Kedro
ExtensionFreeA Kedro VSCode Extension.
Capabilities10 decomposed
static-code-navigation-with-kedro-schema-awareness
Medium confidenceEnables Go-to-Definition and Find-Reference navigation within Kedro projects by parsing pipeline.py files and resolving references to configuration files (catalog.yml, parameters.yml) using static AST analysis. Implements bidirectional linking: from pipeline definitions to YAML configs and vice versa, without executing code or requiring runtime introspection. Uses VSCode's built-in language server protocol (LSP) to register custom definition and reference providers scoped to Kedro project structure.
Implements Kedro-specific schema-aware navigation that understands the relationship between pipeline.py node definitions and YAML catalog/parameter files, enabling bidirectional linking that generic Python IDEs cannot provide without Kedro domain knowledge
Outperforms generic Python IDEs (PyCharm, Pylance) for Kedro projects because it understands Kedro's configuration-driven architecture and can resolve references across Python code and YAML files, whereas generic tools treat YAML as unstructured text
schema-based-autocompletion-for-pipeline-definitions
Medium confidenceProvides context-aware autocomplete suggestions when typing dataset or parameter names in pipeline.py files by matching against the Kedro data catalog and parameters schema. Triggered by typing a double-quote character within a pipeline definition, the extension queries the project's catalog.yml and parameters.yml to suggest valid identifiers. Uses VSCode's CompletionItemProvider API to register custom completion handlers that validate suggestions against Kedro's schema, preventing typos and invalid references.
Implements Kedro-specific completion that validates suggestions against the actual data catalog and parameters schema, ensuring only valid references are suggested, whereas generic Python autocomplete has no awareness of Kedro's configuration structure
More accurate than generic Python IDE autocompletion because it understands Kedro's catalog-driven architecture and can validate suggestions against the actual project configuration, reducing invalid references compared to text-based completion
hover-based-metadata-extraction-for-pipeline-elements
Medium confidenceDisplays contextual metadata when hovering over pipeline elements (dataset names, parameter keys, node definitions) by extracting information from Kedro configuration files and pipeline definitions. Implements VSCode's HoverProvider API to parse YAML catalog entries and parameter definitions, then renders formatted tooltips showing dataset type, location, description, and parameter values. Performs static metadata extraction without executing code or querying runtime state.
Extracts and displays Kedro-specific metadata (dataset type, location, parameter values) in hover tooltips, providing inline access to configuration information without context switching, whereas generic IDEs show only Python docstrings
Faster than manually opening catalog.yml to check dataset properties because metadata is displayed inline on hover, reducing context switching compared to generic Python IDEs that lack Kedro schema awareness
schema-validation-for-kedro-configuration-files
Medium confidenceValidates catalog.yml and parameters.yml files against Kedro's schema in real-time as the developer edits, providing inline error markers and diagnostic messages for invalid configurations. Implements VSCode's DiagnosticsCollection API to register a custom validator that parses YAML files and checks them against Kedro's schema definition, reporting missing required fields, invalid data types, and malformed entries. Validation runs on file save and during editing, with errors displayed in the Problems panel and inline in the editor.
Implements Kedro-specific schema validation that understands Kedro's configuration requirements and validates YAML files against the actual Kedro schema, whereas generic YAML validators only check syntax and basic structure
Catches configuration errors earlier than running `kedro run` because validation happens in the editor during development, reducing iteration time compared to discovering errors at runtime
interactive-pipeline-visualization-with-node-navigation
Medium confidenceRenders an interactive flowchart visualization of the Kedro pipeline DAG in a VSCode sidebar panel using Kedro-Viz, displaying nodes, datasets, and dependencies as a directed acyclic graph. Implements hyperlink navigation from flowchart nodes to their corresponding Python function definitions and from data nodes to their catalog entries. The visualization updates when pipeline definitions change, with an optional auto-reload feature that refreshes the graph without manual server restart. Uses Kedro-Viz as an embedded visualization engine, rendering the DAG in a webview panel within VSCode.
Embeds Kedro-Viz directly in VSCode as an interactive sidebar panel with hyperlink navigation to source code, enabling pipeline visualization without context switching to a separate browser window, whereas standalone Kedro-Viz requires opening a web browser
More integrated than standalone Kedro-Viz because the visualization is embedded in the editor with direct navigation to code, reducing context switching compared to opening Kedro-Viz in a separate browser tab
command-palette-pipeline-execution-launcher
Medium confidenceProvides a VSCode Command Palette command (`kedro: Run Kedro Viz`) that launches the Kedro-Viz visualization server and renders the pipeline flowchart in the sidebar panel. Implements VSCode's Command API to register custom commands that invoke Kedro CLI operations (e.g., `kedro viz`) through the selected Python interpreter. The command integrates with VSCode's task system to run Kedro commands in the background, displaying output in the integrated terminal and handling errors gracefully.
Integrates Kedro CLI commands directly into VSCode's Command Palette, allowing pipeline operations to be invoked without opening a terminal, whereas typical Kedro workflows require manual CLI invocation in a separate terminal window
Faster than manual CLI invocation because Kedro commands are accessible via keyboard shortcut in the Command Palette, reducing context switching compared to opening a terminal and typing commands
python-interpreter-selection-and-environment-management
Medium confidenceIntegrates with VSCode's Python extension to allow selection of the Python interpreter used for Kedro operations (pipeline execution, server initialization, code analysis). Provides a command (`> Python: select interpreter`) that delegates to the Python extension's interpreter picker, allowing developers to switch between virtual environments, conda environments, or system Python installations. The selected interpreter is used for all Kedro CLI operations and code analysis within the extension.
Delegates interpreter selection to VSCode's Python extension, providing seamless integration with VSCode's environment management rather than implementing custom environment handling, ensuring consistency with other Python tools in VSCode
More reliable than custom environment management because it leverages VSCode's battle-tested Python extension, reducing bugs and ensuring compatibility with other Python tools in the editor
kedro-project-discovery-and-configuration-selection
Medium confidenceProvides a command to select and configure the active Kedro project when multiple projects exist in the workspace or when the extension needs to be pointed to a non-root project directory. Implements VSCode's QuickPick API to present available Kedro projects and allows configuration of the project path. The selected project becomes the context for all subsequent code navigation, visualization, and command execution. Configuration mechanism is undocumented but likely stored in VSCode workspace settings.
Provides project selection UI for monorepo and non-root project scenarios, whereas most Kedro tools assume a single project at workspace root, enabling use cases with multiple projects
Enables monorepo workflows that single-project-focused tools cannot support, allowing developers to work with multiple Kedro projects in one VSCode workspace
language-server-lifecycle-management-with-restart-capability
Medium confidenceManages the lifecycle of the Kedro language server (`vscode-kedro` server) that powers code analysis, navigation, and validation features. Provides a command (`kedro: restart server`) to manually restart the language server when it becomes unresponsive or when project configuration changes require reinitialization. The language server is implemented as a separate process that communicates with VSCode via the Language Server Protocol (LSP), handling all static analysis and schema validation operations.
Exposes language server restart as a user-accessible command, allowing developers to recover from server issues without reloading VSCode, whereas most LSP-based tools require full editor restart
Faster recovery from server issues than restarting VSCode because the language server can be restarted independently, reducing downtime compared to full editor restart
pipeline-view-filtering-and-selection
Medium confidenceProvides a command (`kedro: Select Pipeline View`) to filter the Kedro-Viz visualization to display only specific pipelines when a project contains multiple pipelines. Implements VSCode's QuickPick API to present available pipelines and allows selection of which pipeline(s) to visualize. The visualization updates to show only the selected pipeline's nodes and dependencies, enabling focused exploration of large multi-pipeline projects. Filtering is applied to the Kedro-Viz rendering without modifying the underlying project configuration.
Provides pipeline-level filtering in the visualization UI, allowing focused exploration of individual pipelines in multi-pipeline projects, whereas standalone Kedro-Viz displays the entire project DAG without filtering
Reduces cognitive load when exploring large multi-pipeline projects because developers can focus on one pipeline at a time, compared to viewing the entire project DAG which becomes visually overwhelming
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Kedro, ranked by overlap. Discovered automatically through the match graph.
@undisk-mcp/mcp-schema
Machine-readable MCP tool schemas for Undisk — enables IDE autocompletion and code generation for any language
Database Client
Universal database client for VS Code.
Kwaipilot: KAT-Coder-Pro V2
KAT-Coder-Pro V2 is the latest high-performance model in KwaiKAT’s KAT-Coder series, designed for complex enterprise-grade software engineering and SaaS integration. It builds on the agentic coding strengths of earlier versions,...
Dot
Virtual assistant that help with data analytics
Buildkite
** - Manage [Buildkite](https://buildkite.com) pipelines and builds.
Powerdrill AI
AI agent that completes your data job 10x faster
Best For
- ✓Kedro pipeline developers building data workflows
- ✓Teams maintaining large multi-pipeline projects with complex dependencies
- ✓Data engineers refactoring pipeline configurations
- ✓Kedro developers writing pipeline definitions for the first time
- ✓Teams enforcing strict data catalog governance
- ✓Large projects with hundreds of datasets where manual lookup is impractical
- ✓Kedro developers reviewing pipeline code and understanding data dependencies
- ✓Teams conducting code reviews of pipeline changes
Known Limitations
- ⚠Only searches within <package_name>/pipelines/ directory structure; nested pipelines must follow this convention
- ⚠Cannot resolve dynamic references (e.g., dataset names constructed at runtime)
- ⚠No cross-workspace navigation; limited to single VSCode workspace root
- ⚠Requires Kedro project to be at workspace root; does not support arbitrary subdirectories
- ⚠Autocompletion only triggers on double-quote character; no fuzzy matching or prefix-based suggestions
- ⚠Does not suggest parameter paths for nested YAML structures; only top-level keys
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
A Kedro VSCode Extension.
Categories
Alternatives to Kedro
Are you the builder of Kedro?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →