Proof to Live
Proof to Live removes the setup maze between seeing a team work and proving it on data you control. Codelit shows one next action at a time and keeps consequential tools inactive during the private proof.
Begin with a truthful Sample
Complete the template's Sample, including its approval checkpoint. It calls no external service and spends no model budget, but follows the same responsibilities, handoffs, terminal, and receipt shape as a real run.
- Open a template and choose Try agent.
- Review the generated evidence and approval request.
- Finish the sample and choose Use my data from its receipt.
Complete one checkpoint at a time
Codelit detects the smallest useful read-only source, reuses a healthy App and prior Team or Thread resource, and selects a sole safe match automatically. It asks only for missing authentication, a genuinely ambiguous scope, a model key when needed, or the brief field the outcome did not provide. The original request survives OAuth and resumes at the same checkpoint.
- Only one connected source is read.
- The selected model uses your browser-local BYOK key.
- The open tab must remain available while the personalized proof runs.
Keep proof and action separate
The personalized proof omits external writes, browser control, and unrelated tools even when the original Team contains them. Its receipt can be reviewed or shared with redaction controls. Choose Live run only when the proof is sound and you want Codelit's managed Pro runtime to recheck Apps, entitlements, approvals, and budgets before acting.
Automate only after the proof is useful
Choose Automate this proof to open Trigger Hub with the compatible runtime already selected. Use a schedule, one connected-app event, or a signed webhook, then review the daily cap, quiet hours, health state, and result delivery before publishing.
- Open-tab schedules stop when the browser tab closes.
- Hosted Pro automations continue after the tab closes.
- Hourly, six-hour, daily, and weekly schedules use the same guarded deployment path.