Maintaining daemon connection for faster successive sequential builds

[fenollp]

Hi! I have a somewhat unusual usage of the command: I split a multi stage build into as many build calls. I wish I could just make a single call that builds the final target, however my problem space does not allow it: the full build plan isn't known until the very end.

Now, I am looking into ways to make these successive calls faster. Today, and on each call, I notice that contexts are reuploaded, caches are re-checked, connections are re-established and so on.

Here's an example of my usage from an issue I reported and that has since been fixed: moby/buildkit#5217

Is there a way to keep a daemon connection alive so that I may reuse it throughout multiple client build calls?
Is making a dial-stdio proxy a sound idea? Can caches get corrupted this way?

What do you suggest I do? Are there unsound operations a custom build client should not attempt?
Thanks

[fenollp]

@tonistiigi Is it possible / supported to do multiple build calls (in the gRPC sense) on the same network connection? Or are there assumptions or limitations