Features · Versions
Git-shaped history for prompts.
Every important change to a prompt is a commit with a message. Branch to try an idea, tag what shipped, merge it back.
A history you can read and trust.
Prompts change for good reasons and for bad ones. A commit records what changed and why, a branch lets you try something without touching the version people use, and a tag names the one that shipped.
- Commit the working copy with a message
- Branch from any commit, check out an older version
- Tag or release a commit
- Merge a branch; conflicts come back for you to resolve
See exactly what changed.
A one-line edit should look like one line. Compare two versions and read the difference before you decide to keep it, ship it or revert it.
{ "tool": "versions", "action": "commit",
"args": { "entity_type": "prompt", "entity_id": "<id>",
"message": "Cut to six sentences, no promises" } }A normal day
Try it on a branch.
Branch
Create a branch called shorter from main. Main stays exactly as it is.
Change and commit
Cut a sentence, run your eval, commit with a message that says why.
Merge and tag
Merge shorter into main. If both sides changed the same lines, you choose. Tag the result.
Questions
About versions.
What can I version?
Prompts, workflows and agents. Each has commits, branches, tags and releases, and merge.
What happens when a merge conflicts?
Merging a branch into the current one returns the conflicts so you can resolve them. Nothing is overwritten silently.
How do I go back to an older version?
Create a branch from the older commit and check it out. The newer history stays where it is.