The SDK that we use for VEXcode and VCS is different from that used by our partner developers. Our “cold” image (really the stdc++ library) is already part of vexos, for this reason the VEXcode binary that is downloaded is usually already very small and we don’t feel we need the complexity of using the technique that’s been implemented by PROS at this time. vexos 1.0.6 should improve wireless download reliability for all development environments and also enables the use of stdout via the controller for wireless debug, this is already implemented in VEXcode.
It’s part of the SDK but we have not exposed it as part of a C++ class. I’m sure that will be added before next season.
This is a limitation of the controller firmware and available communications bandwidth to the v5 brain, I’m not expecting any significant changes to this in the near future.