Hi @dry-beach-38304 and @square-wire-39606 , I'm Mehfooj, and I'm very excited to be working on the DevContainer as a Local Executor project. I've spent the last week diving deep into the Metaflow codebase to understand how to move from "Virtual Sandboxes" to "Container Sandboxes." Current Progress: • Core Logic: I’ve been deconstructing

metaflow/decorators.py

and the

StepDecorator

lifecycle. My plan focuses on utilizing

step_init

for

.devcontainer

discovery and overriding

runtime_step_cli

to orchestrate the Docker execution swap. • Testing: I’ve successfully prototyped environment isolation using the

@pypi

decorator locally to understand how Metaflow handles the "command hijack" for sandboxing. • Prototyping: I started the actual

@devcontainer

decorator prototype 2 days ago (balancing with my ongoing exams) and aim to have a basic "Hello World" Docker-hijack working within the next 48 hours. My Goal: I want to ensure my approach aligns with the project vision—specifically how the

@devcontainer

decorator should interact with or override existing decorators like

@pypi

or

@conda

when generating the container spec. I'll be submitting my initial proposal draft shortly. Would love to hear if there are specific edge cases in the DevContainer spec you'd like me to prioritize in the prototype!