Fixes #13931

Summary

Two interactive walks. No extra pages. Copy stays short. The pictures do the work text keeps failing at: people treat the laptop as Dagger during helper prepare.

Where each visual sits

Helper prepare walk: Execution, after The Path, on steps 3 and 4

Those two lines are:

3. The engine loads the requested module.
4. The SDK exposes the module API.

Then the page already says the caller invokes a function. The visual sits in the gap between 4 and 5. That gap is prepare. The function list does not exist yet. The caller cannot invoke anything.

This is the "what happens under the hood" page. Load then expose the API is helper prepare, named as two steps. The picture is those steps drawn: engine already on, a short-lived helper, named settings (not the laptop), downloads, then the function list. Your function stays empty until that list exists.

Not Calling Functions. That page is the command after the list exists. Not Service Proxies for this walk. That page is one env var. Git has no home there.

Lazy Work, Traces, and Cloud stay as they are. The visual does not belong under them.

Call stages: Service Proxies, next to GOPROXY

That page already says set _DAGGER_ENGINE_SYSTEMENV_GOPROXY on the engine container, and that Dagger passes it into Go module downloads including SDK codegen. The four-stage walk is that sentence drawn: connect does not use GOPROXY, load is your files, prepare is the Go helper and the default proxy, your function is last and does not run if prepare cannot finish.

Custom Runner is how you start the box. Point at it. Do not put the four stages there.

Test plan

• Open /extending/how-dagger-works/execution (Next). Click each prepare step. Helper appears inside the engine. Function stays empty until the list exists.
• Open /reference/configuration/proxy. Click the four stages. Prepare is the Go download. Connect and the function are not.
• Confirm laptop, engine, and helper copy names where settings sit, without issue numbers.

Made with Cursor