Prompt CMS / planned
Version prompts, roll back instantly, stay out of the critical path.
Prompt CMS is designed to version every prompt change, label it per environment, and roll back to a known-good version in one click. The @telemeter/prompts SDK is designed to read with a local fallback baked in, so a CMS outage is never in the critical path of a production request.
Versionsv11 → v12
EnvironmentsDev · staging · prod
FallbackLocal, always
StatusPlanned · join the waitlist
A rollback you can trust.
Each step is designed to keep prompt changes reviewable and reversible, with the SDK’s local fallback keeping a CMS outage off the request path entirely.
- 01
Version
Every prompt change is a version
Each edit creates a new immutable version instead of overwriting the prompt in place — the history of what actually shipped stays intact.
Planned: version store - 02
Label
Point an environment at a version
Dev, staging, and production each carry their own label, so a change reaches one environment before the rest.
Planned: environment labels - 03
Roll back
Undo a bad prompt in one click
Repoint an environment label to the previous version — v12 back to v11 — instantly. No redeploy, no waiting on a build.
Planned: instant rollback - 04
Fetch
Read through the @telemeter/prompts SDK
The SDK fetches the labeled version at runtime and falls back to a last-known-good prompt bundled locally, so a CMS outage never blocks a production request.
Planned: @telemeter/prompts SDK