osFoundry / Platform
Prompts
Every system prompt is a versioned record. Diff between versions, roll back, share to community.
What it is
Prompts is the system-prompt manager inside osFoundry Studio. Instead of a system prompt being a single text box you overwrite and forget, every save becomes a versioned record. The prompt that drives an agent, a loop, or a team keeps its full history, so you can always see what it said last week, who changed it, and what a given edit actually did to behavior.
The workflow is built around three moves. Diff shows a side-by-side comparison between any two versions, so a subtle change — a reworded instruction, a dropped constraint, an added guardrail — is visible instead of buried in a wall of text. Roll back restores an earlier version when a "small tweak" quietly breaks output, without you having to remember or paste back the old wording. Share to community publishes a prompt you trust so other people can start from it, and lets you pull in prompts others have proven. Because osFoundry is a local-first desktop workspace, your prompt history lives with your workspace on your device; sharing to the community is a deliberate action you take, not a default.
This matters because a system prompt is the highest-leverage piece of text in any agent — it decides tone, scope, refusals, and format across every run. Editing it blind is how working behavior silently regresses. Versioning turns prompt engineering into something you can review, compare, and undo, the same way you would treat code. And since osFoundry is bring-your-own-key, the same versioned prompt runs against whatever model you point it at — local, cloud, or self-hosted — so improving a prompt improves it everywhere you use that agent, with no reseller sitting between you and the model.
Key capabilities
- Every system-prompt save is stored as a distinct version with its full edit history retained
- Diff any two versions side by side to see exactly what wording changed between them
- Roll back to a previous version in one step when an edit regresses agent behavior
- Share a proven prompt to the community, or start from prompts others have published
- Reuse the same versioned prompt across any model you bring your own key for — local, cloud, or self-hosted
Use cases
- Prompt engineer: compares two versions of an agent's system prompt to confirm a reworded instruction, not model drift, caused a change in output
- Team lead: rolls back a shared agent to last week's prompt after a quick edit started producing off-format responses
- Builder: publishes a well-tuned research-agent prompt to the community and pulls in a vetted summarization prompt to adapt for their own workspace
Frequently asked questions
How is a system prompt versioned in osFoundry?
Each time you save a system prompt in Studio it becomes its own versioned record rather than overwriting the previous text. The prior versions stay available, so you can open the history, compare, and restore any earlier one instead of relying on manual copies.
Can I compare two versions of a prompt to see what changed?
Yes. Prompts includes a diff view that puts two versions side by side and highlights the differences, so a small edit — a dropped constraint or a reworded rule — is obvious instead of hidden in a long block of text.
What does sharing a prompt to the community involve?
Sharing is an explicit action: you publish a specific prompt version so others can start from it, and you can pull in prompts other people have shared. Because osFoundry is local-first, your prompt history otherwise stays in your own workspace on your device until you choose to share.