Can I return my order after 45 days?
Make your next prompt work better.
Try an idea against your actual application. See what changes, keep the useful versions, and take the result back into your code.
One question. Two instructions.
01 / CHANGE THE INSTRUCTIONSUPPORT AGENT
system / v2
Answer the customer’s question.
Use only the supplied policy.
Cite the source in your answer.
{{question}}{{policy}}
The return window is 30 days, so an order delivered 45 days ago is outside the policy. [1]
Grounded in the supplied policy
A small prompt change. A traceable difference.TRY THE TWO VERSIONS ↑
THE QUESTION THAT MATTERS
Can it handle the questions my customers actually ask?
01Answers from your business content.
02Actions connected to your systems.
03A team that can take over.
PROMPTS02
Try a new instruction. Keep a version you trust.
A prompt change can improve one answer and break another. Work on a draft, test the result, and publish a version your application can name.
↳
Work in drafts
Edit messages, models, and variables without changing the published prompt your application uses.
↳
Publish a stable version
Each publication creates an immutable numbered version. Pin a version when reproducibility matters.
Change the draft. Keep a stable version.
v1Published
v2Tested & published
DraftWork in progress
+ Use only the supplied policy.+ Cite the source in your answer.
Your application can keep using v1 while you work.
PLAYGROUND03
Ask a real question. See the whole result.
Connect your application and give it an input. The Playground keeps the output and its trace together, so you can inspect what happened and try again.
↳
Connect your application
Expose your app through the CLI bridge with a workflow input object or agent messages.
↳
Try a focused change
Run new inputs against the connected app, with input schemas guiding the form where available.
TerminalCLI
Connect your local app. Reload on save.
npx datool connect ./handler.ts --watchKeep this terminal running, then select your app in Playground to try an input and inspect its trace.
SDK, CLI & MCP04
A few lines. Your existing application.
Keep your models, tools, and application code. Fetch managed prompts with the SDK, connect your app through the CLI, or work with Datool from an MCP client.
↳
Instrument with the SDK
Capture application inputs, outputs, spans, and model activity in your project.
↳
Work from the terminal
Use the CLI to connect applications, inspect recorded evidence, and run evaluation workflows.
app.tsJAVASCRIPT
Loading editor…
Fetch a published prompt version, then render it with your application's variables.
THE BUILD TOOLKIT
A shorter path from idea to evidence.
START WITH ONE REQUEST