Lev Lazinskiy

Hello, Thank you very much for this PR. We used to have an [`experimental` module](https://github.com/levlaz/circleci.py/blob/96a296823becd4b5d13145e4ae124c7b3605a7af/circleci/experimental.py) to handle these sorts of things and I would propose to re-introduce this module if...

> When I run it locally with Docker, all my tests pass without issue. Hey @erka can you share how you are running this locally with Docker? What specific commands...

> I'd suggest that most commands NOT send traces except `dagger call`, but you could force a send with `-d` or other flag which would be great for collaborative troubleshooting....

@jpadams the only one I disagree with is `run` - I think this should send traces, and I thought it actually did already?

This is related to https://github.com/dagger/dagger/pull/8412

Unfortunately there is no other workaround right now. > Is there any alternative to this right now other than a live file watcher rerunning dagger commands? I had not thought...

> I would also love this feature directly integrated into Dagger. For now I’m going to see if I can integrate Dagger with Tilt https://tilt.dev/ tilt seems interesting, I have...

> x-linking to #6260, seems like some of this would be solved by that? Yeah 100% - being able to inspect cache would be awesome! I think having a one-off...

The reason why I specified cache mounts is because I think we can use the CACHEBUSTER pattern to clear the cache, but it does not seem to have any impact...

Hey @caarlos0, when you get a chance could you please approve the workflows to run from this fork so that we can test and make sure the proposed changes will...