Review changes together
Blueprint keeps collaboration tools on the prompt detail page so authors and reviewers can inspect how a prompt changes over time and how it behaves with different inputs.Revision History
Open a prompt’s detail page and review Revision History to compare saved versions. Use the history to understand what changed before you adopt or fork a revision.Run History
Run History records previous executions so you can compare inputs and outputs. Use it to reproduce a result, investigate a regression, or confirm that a variable change improved the prompt.Annotations
Highlight prompt text to add an annotation for collaborators. Use the annotations panel and the Hide Annotations control to review feedback without changing the underlying prompt. Resolve or incorporate feedback deliberately, then save a new revision.Use AI-assisted review carefully
When the current prompt view offers AI annotation suggestions, treat them as proposals. Verify every suggestion against the prompt’s purpose, safety requirements, variables, and expected output before applying it.Compare prompt behaviors
- Run this Prompt tests the prompt with live variable inputs.
- Chat with Prompt supports iterative conversation while the prompt guides the interaction.
- Open in AI opens the prompt in the related AI workspace for additional testing.
Team review checklist
- Record the intended behavior and required variables.
- Use non-sensitive test inputs and capture representative edge cases.
- Review changes for unintended instructions, tool access, or data exposure.
- Check the output format, uncertainty handling, and human-review requirements.
- Fork or create a new revision before making a substantial change.
Collaboration history helps explain what changed; it does not prove that a prompt is safe or correct. Keep human review in the loop for consequential use.