Hi Shashank (@rhythmic-controller-77489), Nissan, and team — I’m Aarav, a CS + EE student at UIUC and an open-source contributor interested in developer tooling and ML infrastructure. I was looking through the GSoC 2026 ideas and noticed that the Metaflow VS Code Extension project was ultimately not selected. I also reviewed the existing

metaflow-dev-vscode

repository and some of the community work around it. There are promising unmerged prototypes, but the extension itself still has not been turned into a cohesive, maintained tool. I’d really like to take this on regardless and build it properly for the Metaflow community. My goal would not be to submit one isolated feature, but to develop a clean, tested VS Code extension in stages: first, reliable flow detection and an interactive DAG / step-outline view; then diagnostics, debugging support, parameter handling, and eventually a run/artifact browser. Before I start, I wanted to ask: 1. Is

outerbounds/metaflow-dev-vscode

still the intended home for this work? 2. Would the team be open to me writing a short design issue and developing this through small, reviewable PRs? 3. Is there a preferred direction for flow analysis: static parsing, using Metaflow’s existing graph structures, or a hybrid approach? I would be happy to build from scratch where necessary, while making sure to respect and credit useful ideas from the prior community prototypes. Thanks - I’d be excited to help make this a real, maintained Metaflow developer tool. Cheers! Aarav Mittal University of Illinois Urbana-Champaign (B.S. Computer Science | B.S. Electrical Engineering)