Clockbook Codezen

Describe the change. Review the diff.

Codezen works on your repository the way a colleague would — reads the surrounding code, makes the change, writes the test, and hands you something you can actually review.

  • Runs against your real repository, not a sandbox copy
  • Every change arrives as a reviewable diff
  • Tests written and run before you see it
refund-webhook.tsprompt → diff → tests green
typescript
1// Refunds retry on timeout — dedupe on the provider event id.
2export async function onRefund(event: RefundEvent) {
3 const seen = await store.claim(event.id, { ttl: "24h" });
4 if (!seen.fresh) return { status: "duplicate" };
5
6 const order = await orders.byCharge(event.chargeId);
7 await ledger.credit(order.id, event.amount, event.currency);
8 return { status: "refunded", orderId: order.id };
9}
Review
  • +18 −4 across 2 files
  • refund-webhook.test.ts · 7 passing
  • Flagged: no retry cap on ledger.credit

Shipping with Codezen

NorthwindCadenceVerity LabsLoop Goods

How it works

Three things that make it usable on real code.

It reads before it writes

Codezen indexes the repository and follows the conventions already there — your error handling, your test style, your naming. The diff looks like the rest of the file.

  • Repository-wide context
  • Matches existing patterns
  • No rewriting things you did not ask about

Tests come with the change

A change without a test is a guess. Codezen writes the test it had to pass, runs the suite, and shows you the result alongside the diff.

  • Test written per change
  • Full suite run before hand-off
  • Failures reported, not hidden

It stops when it should

Ambiguous requirements, destructive migrations and anything touching production data come back to you with a question instead of a commit.

  • Asks rather than guesses
  • Never force-pushes
  • Full audit of every action taken

Demo

See Codezen working.

A change requested, written, tested and handed back as a diff.

Automations

Templates that put Codezen to work.

Engineering

Autonomous Code Loop

Hand the agent a coding goal: it iterates in an isolated worktree, commits small steps, then gates and opens a clean PR.

autonomous-codingcode-loopworktree
Engineering

Issue To Pr

Point at a tracked issue: a cloud sandbox clones the repo, implements the fix agentically, and opens a PR that closes it.

issuescloud-sandboxautomation
Engineering

Release Notes

Turn everything merged since the last release into clean, user-facing release notes published to your workspace.

release-noteschangelogdocs
Engineering

Website Launcher

Brief to live site: generate the design, review it as an HTML plan, build it in a web-builder sandbox, and deploy.

websitedesigndeploy

MCP & REST

Point it at your own tools.

Codezen speaks MCP and REST, so it can query your database, open your tickets and read your logs — with scoped credentials you issue and revoke.

What teams report.

—
of Codezen pull requests merged without rework
—
reduction in time from ticket to open PR
—
of changes shipped with a test attached

Numbers intentionally blank — fill from your own telemetry and say the sample size and period here.

What engineers ask first.

Replace with your real data-handling answer — this is the first question every engineering buyer asks and a vague answer loses the deal.