Awesome timing – we deployed a fix for what you’re describing, after discovering it ourselves about an hour ago while working on a Job: Update to 0.18.0-0.18.4
It wasn’t a matter of public/private on the cluster; it was a little JavaScript issue that slipped through the cracks.