Cresta opens self-service for developers: build agents in your repo
Cresta now lets developers build, test and deploy customer-facing AI agents with Conductor, a CLI and a Python SDK. Keep the agent code in a repo you control.
Cresta opened its AI agent platform to developers with end-to-end self-service. Teams can now build, test, deploy and tune customer-facing AI agents on Cresta without waiting on Cresta's own engineers. For small businesses that hire a studio or a contractor to build support agents, the real change is not the platform. The agent becomes code in a repo, and you can own a repo.
What actually happened
Per Cresta's October 29 announcement, developers work through three tools. Conductor is Cresta's agent builder, and the release says it fits into a team's own repository and CI/CD pipeline. The Cresta CLI gives developers and coding agents access to the platform from the terminal. The Cresta AI Agent SDK lets developers write custom code in standard Python and connect agents to their own systems. Cresta says developers can build in-house or for clients.
Conductor runs on the Claude Agent SDK. In an Anthropic case study, Cresta says Conductor started as an internal tool for its forward-deployed engineers. It became a product when its output matched what an experienced engineer would build. Cresta reports that early deployments cut initial deployment time roughly in half.
Atento and TELUS Digital are named as partners. The release has no pricing and no public sign-up price. Speed claims such as "as little as one week" to production are Cresta's own numbers. Treat them as marketing until you see one of your own workflows ship.
Why it matters for your business
Agents as code beat agents as clicks. A no-code builder hides the logic in a vendor's UI. A repo gives you diffs, review, tests and a history of who changed the refund rule and when. If a contractor builds your support agent, ask for the repo, not a login.
Your test set is the asset. Cresta tests Conductor on fixed build tasks and reruns them when a new model ships. Do the same for your agent: twenty real customer conversations with the right answers, run on every change. That file outlives any vendor.
Check the exit. The SDK is Python, but the runtime is still Cresta's. Find out what you can export (prompts, tools, test cases, transcripts) before you sign. Portable parts are leverage at renewal time.
Key takeaways
- Cresta now offers end-to-end self-service for developers building customer-facing AI agents
- Tooling: Conductor in your own repo and CI/CD, the Cresta CLI, and a Python AI Agent SDK
- Conductor is built on the Claude Agent SDK; Cresta reports deployment time cut roughly in half
- No pricing announced; speed claims are company-reported
- Own the repo and the test set, and confirm what you can export before you commit
Who owns the code behind your support agent? We build customer-service agents as code in your repository, with a regression test set from your real tickets and no lock-in to one platform. See how we build or look at what we have shipped.
Sources: Cresta via PR Newswire, Anthropic: Cresta case study.
- #cresta
- #ai-agents
- #customer-service
- #claude-agent-sdk
- #developer-tools
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
TanStack AI 1.0: Stable Core, 23 Providers, Experimental Harness
TanStack AI 1.0 ships 23 provider adapters and a stable core, but the agent harness is still 0.x. Build on the core, keep the harness behind a wall.
Read itshopify app security check: put Shopify's app scanner in CI
Shopify's app security check CLI scans for unverified webhooks, cross-shop data access and leaked keys. It never fails by default. Run it in CI with --blocking.
Read it