New: send one ticket to four agents and keep the best result. Release notes
Cloud machines for coding agents

Your backlog,
quietly cleared.

Ivet gives Claude Code, Codex and the rest a real desk in the cloud: a full machine, your repo and your tools. You come back to finished branches.

Talk to us Try Ivet free

New teams get $100 of agent time on us.

How it works

01 How it works

Write the ticket.
Ivet handles the rest.

Ask from anywhere

Mention Ivet in Slack, tag it on an issue, or type into the console.

#eng-requests
@Ivet

Pick the agent

Claude Code, Codex, Cursor or Opencode, each on its own private machine.

Upgrade the queue worker to Node 22
  • Claude Codereading repo…
  • Codexreading repo…
  • Cursorreading repo…
  • Opencodereading repo…
m-2f9c · debian 12 · 4 cores · 8 GB

Review and ship

You get a branch, a short summary and proof it works. Merge it or send notes.

ivet/queue-worker-node22
+96−142checks 31/31
✓ Ready for review · #3071

02 Connect

Ivet goes where
requests already happen.

There's no new inbox to watch. Ivet listens in the tools your team already writes in and turns a message into a running job.

Console

Working · 4

  • Throttle inbound GitHub hooks
  • Retry S3 uploads on 503
  • Paginate the audit log
  • Fix typo in signup email

Waiting on you · 2

  • Remove v1 session tables
  • Docs: rotating API keys
  1. import { bucket } from './throttle'
  3. router.post('/inbound/github', async (ctx) => {
  4. const kind = ctx.req.header('x-github-event')
  5. const org = payload.installation?.id ?? 'unknown'
  6. const slot = await bucket.claim(`org:${org}`)
  7. if (!slot.granted) {
  8. ctx.header('Retry-After', String(slot.wait))
  9. return ctx.json({ error: 'busy' }, 429)
  10. }
  11. await jobs.enqueue(kind, payload)
  12. return ctx.json({ queued: true })
  13. }) // per-org throttle
Leave a note for the agent…

CHANGED

  • inbound.ts +9
  • throttle.ts +27
  • inbound.spec.ts +38

Open any run in the console to follow along, comment on specific lines, or take over the keyboard.

Slack
# support-escalations9:15 AM
RT Rafael

@Ivet customers say the invoice PDF shows yesterday's date. Can you take a look?

Linear
CORE-419Picked up

Add a timezone picker to billing settings

OwnerIvet
GitHub and GitLab

Comment @ivet on an issue or pull request. It reads the thread, reproduces the bug and pushes a fix to the branch you choose.

Schedules and API
POST/v1/jobs
{ "agent": "codex", "repo": "acme/web",
  "brief": "upgrade eslint, fix the warnings" }

Trigger runs from cron, a deploy pipeline or your own scripts with one request.

03 Insights

See what every
agent hour paid for.

Each run records who asked, which agent and model did the work, and which tools it used. Your bill reads like a receipt.

Branches shipped
1,284

▲ 18% this month

Machine hours
3,912

▲ 9% this month

Merged first try
71%

▲ 4 pts

Median run
14 min

▼ 3 min

Oct 1Oct 8Oct 15Oct 22
  • Claude Code46%
  • Codex28%
  • Cursor17%
  • Opencode9%

04 Machines

Every task gets
its own machine.

Ivet starts a fresh Linux machine for each job, set up the way you described it once. Agents build, test and click through your app before asking for a review.

SETUP

  • bun install
  • docker compose up
  • npx playwright install

INCLUDED

  • 6 MCP servers
  • 9 skills
  • 22 secrets
m-ivet-7f3aStarting
DEPS1,912 resolved
SERVICESpostgres:16redis:7
BROWSERchromium
LINKEDgithubsentrylinear

05 Use cases

Good at the work
nobody schedules.

Most teams start with small recurring chores and work up from there.

Dependency upgrades used to be a quarterly project. Now they happen every Tuesday night.
UpkeepNightly schedule
Pull requests show up with a first review done and the small fixes already pushed.
Code reviewEvery pull request
Our designers file a card in Linear and get a preview link back before lunch.
Small featuresFrom the issue tracker

06 FAQ

Questions

Didn't find your answer? An engineer reads every message.

Email us

Claude Code, Codex, Cursor and Opencode. They share the same machine setup, so you can choose a different agent for each job or give one job to several and compare.

A fresh Linux machine with your repo checked out, packages installed and services running, plus only the tools and credentials you've approved.

No. A job can end in a branch, a comment, a short write-up or a recording of the agent testing your app. You decide what done looks like.

On GitHub or GitLab. Connect your account, then pick which repositories Ivet can open.

Machine time is billed by the minute based on size. Each plan's monthly fee comes back as usage credit, and new teams start with $100 free.

The machine is wiped when the job ends. Secrets stay encrypted and are only passed to the machines you allow.

Give your agents
a place to work.

Setup takes about five minutes.

Talk to us Try Ivet free