Problem

When running cu as an MCP server, since it's using the Dagger SDK, it'll automatically provision an engine for that SDK. When calling cu terminal outside an existing dagger session, we're calling (https://github.com/dagger/container-use/blob/main/cmd/cu/terminal.go#L39) the dagger CLI which if it uses a different version than the one provisioned by cu, will trigger and engine replace by default.

In summary, cu and dagger binaries mismatching is hurting users given that they find themselves having unwanted behaviors and strange issues.

Solution

Make cu and dagger place nice together by allowing cu to be able to use whatever engine you have provisioned as long as it's compatible.