The Agent IDE where nobody waits

Keep working while your agent does. Branch off, merge back, and line up what’s next without interrupting.Branch off, merge back, and never wait on your agent.

Join waitlist

Trusted by teams at

charges endpointmain

Go with the middleware approach. Key on Idempotency-Key + route + body hash.

Adding an idempotency middleware that stores the response and replays it.

retry policy?2

›4 tool calls+70 −2

Merged from thread: add dedupe in the provider

working

retry policy?thread

YouWhat’s our retry policy on the provider call?

Agent3 attempts with backoff, but no dedupe. I’d add it in the provider.

Merge conclusion

Every open question gets its own thread

Work through open questions as parallel threads while the main line keeps moving. Tangents branch off, and only the conclusion merges back.

charges endpoint workingturn complete

✓Editcheckout.ts+4

✓Editsubscriptions.ts+4

✓Editinvoices.ts+3

Use deriveKey() from the middleware. Don’t inline the hash.

Assert the Idempotent-Replay header in the spec.

Next3 queued

1Use deriveKey() from the middlewarenext stepsent

2Assert the Idempotent-Replay headerend of turnsent

3Migrate the subscriptions pathhold

Decide the next step before your agent is free

Queue your next message for right away, the end of the turn, or on hold. Steer mid-task, or fan out into parallel branches.

src/routes/charges.ts+5 −1

41export const idempotency = mw(async (req, next) => {

42 const key = deriveKey(req)

43 const record = await redis.get(key)

44 if (record) {

45 if (record.hash !== hash(req)) return conflict()

46 return replay(record)

47 }

48 const res = await next()

49 await redis.set(key, res, { ttl: env.TTL })

50 return res

Edit · charges.ts:45call 12

Why a 409, not a replay?

“Reused key with a different body is a 409, not a replay. Same rule as charges.ts:88.”

thread · retry policy?

Edit · charges.ts:49call 7

Why a configurable TTL?

“Spec: Redis, 24h TTL, configurable per environment.”

idempotency-spec.md

The full story behind your code, not just a diff

Every line links to the tool call that wrote it, so your agents see the reasoning behind any code instead of reopening settled decisions.

Get your flow state back