Publishing a prompt is safer when more than one person is editing

The prompt console is where staff edit the instructions the assistant runs on. As more than one person starts tuning prompts, three rough edges in publishing have been smoothed.

A publish no longer quietly overwrites someone else’s. If somebody else publishes — or rolls back — a file while you have it open, publishing yours is now refused instead of silently replacing a change that was already live. Your draft is kept exactly as you left it, and you are shown the version that landed alongside the one you were about to publish, so you can fold their change into yours and publish again. Rolling back is protected the same way.

One broken version pointer no longer blocks the whole workspace. When a file was recorded as published at a version that had gone missing, publishing anything that shared with it used to be refused — and because a couple of files are used by every part of the assistant, one missing version could make nothing publishable at all. Now publishing that file simply repairs it, and only a publish that genuinely depends on the unrepaired file stays refused.

A clearer message when the store can’t be reached. A file that no part of the assistant reads yet is now refused with the same clear “can’t reach the workspace, nothing changed, try again” message as every other file, rather than failing with a raw error.

Nothing about what the assistant answers on changes here — this is about making the console safe to live in day to day.