Flagship outcome packs
Codelit's flagship packs are complete Agent Teams for recognizable work. Each starts with a free deterministic Sample, collects only the brief fields that bound the job, names every required connection, pauses before consequential actions, and returns evidence that can be repeated through Trigger Hub or a published Agent App.
Maintain a repository and prove a release
Autonomous Release Team starts from one GitHub issue, a base branch, selected files, and one exact patch path. It reads repository guidance and only those selected paths, creates a reviewed branch and patch, creates a Vercel preview, rechecks GitHub Actions on that branch, verifies the visible preview, then prepares the pull request, promotion, Slack proof, and source-issue update.
- Connect GitHub, Vercel, and Slack before Live run.
- Traversal, absolute, environment, and unreviewed file paths are rejected after the Agent handoff is rendered.
- Use the GitHub issue trigger for new work or a bounded weekly schedule for maintenance review.
Resolve a refund with a hard ceiling
Refund Resolution Team reconciles one Zendesk ticket, Shopify order, Stripe PaymentIntent, supplied policy, and maximum refund amount. The decision must produce one exact positive amount at or below that ceiling before the Stripe preview can be approved; the customer ticket is updated only after Stripe evidence exists.
- Connect Zendesk, Shopify, and a restricted Stripe account.
- Stripe retries reuse the approved action checkpoint as the idempotency key.
- Use a signed webhook with deduplication and a daily cap for support intake.
Qualify a lead without sending email
Lead Qualification Team combines an allowlisted HubSpot contact with visible evidence from the exact LinkedIn company URL. It preserves campaign identity and explicit outreach permission, creates only an unsent Gmail draft, then updates HubSpot after the draft succeeds.
- Connect HubSpot and Google Workspace, then save a LinkedIn Browser Operator session when sign-in is required.
- Blocked, missing, or opted-out permission stops the run before Gmail or CRM writes.
- A daily Trigger Hub schedule applies deduplication, a ten-run daily cap, and configured quiet hours.
Move from proof to repeatable work
Run Sample first, choose Use my data for a private read-only proof, then use Pro Live run for the exact approved actions. A successful receipt can become an Agent App or a hosted Trigger Hub deployment. The same workflow version, connection requirements, approval boundaries, replay protection, and recovery checkpoints remain visible at each stage.
- Complete the committed Sample and inspect its one meaningful approval.
- Connect only the accounts named on the Team Flow and complete the run brief.
- Run live once, inspect the provider and browser evidence, then publish an Agent App or enable the recommended guarded trigger.