I’d also add that agents aren’t caching disk state after the “install” step as the documentation states they would.
It’s worth mentioning that background agents seem quite unstable in general. See Agent is unable to use sudo due to no TTY and Background Agent Docker in Docker - #18 by someguynamedmike . It feels like a bit of a moving target trying to understand how they work and where they differ from the documentation. It’s understandable if this is an early and experimental feature subject to active churn, but if that’s the expectation I wish it would be communicated out. I’ve had several times now where I spend a fair amount of time configuring them and using them for a little bit only for them to break and have to configure again, trying to infer how they work now. A feature that should be pretty powerful is ending up in a net productivity loss 