Debugging workers with shared durable objects

[ctusch]

What versions & operating system are you using?

System:
OS: Windows 11 10.0.26200
CPU: (12) x64 AMD Ryzen 5 9600X 6-Core Processor
Memory: 14.26 GB / 31.11 GB
Binaries:
Node: 24.7.0 - C:\Users\Admin\AppData\Local\fnm_multishells\15856_1767042627589\node.EXE
npm: 11.5.1 - C:\Users\Admin\AppData\Local\fnm_multishells\15856_1767042627589\npm.CMD
bun: 1.3.0 - C:\Users\Admin.bun\bin\bun.EXE
npmPackages:
wrangler: ^4.54.0 => 4.54.0

Please provide a link to a minimal reproduction

https://github.com/ctusch/cf-workers-shared-do-inspector-bug

Describe the Bug

I have two cloudflare workers, A and B. Worker B uses durable objects of worker A. I want to debug worker B locally using devtools.

If I run both workers with separate wrangler dev commands, worker B cannot access worker A's durable objects, even though it shows as connected. (Error: Cannot access "MyDurableObject#sayHello" as Durable Object RPC is not yet supported between multiple dev sessions.)

If I run worker B with wrangler dev and add worker A via an additional -c argument the durable object access works. But in Chrome DevTools only the sources for worker A are loaded and I cannot debug errors in worker B.

The order of the -c arguments does not affect which sources are available in devtools. It seems like wrangler only loads sources from the first .wrangler directory in alphabetical order.

Please provide any relevant error logs

No response

[serban-mihai]

This never got patched in years, unfortunately it's also the most common use-case for most workflows including ours.
Please anybody from the wrangler development team address this asap, deploying all workers (and DOs) and debugging them on remote it's a pain, for those who have deployment automation in Actions would also avoid filling the git history with debug commits for a single feature