Skip to main content
Kliff
Sign inStart free

Cloud agents for enterprise teams

Nexus Cloud Agents work on your repositories with detailed metrics for every team, memory your whole organization shares, and a verification layer that checks each change before it reaches review.

Start an agentSee pricing

Its own computer for every agent. Free plan with 1,000 credits a week.

Checkout retriesExample, turn 2 on acme/checkout

Why are some customers charged twice when checkout is slow?

Done4 steps18,920 tokens
  1. Started the computer4s
  2. Searched for idempotencyKey2s
  3. Read payments/client.ts3s
  4. Ran bun test payments12s

Found the double charge

When the first request times out, retry() makes a new idempotency key, so the payment provider treats the retry as a second charge.

Found the double charge. When the first request times out, retry() makes a new idempotency key, so the payment provider treats the retry as a second charge.

Checkout retriesTurn 3

Pick up where we left off: reuse the idempotency key on retries and add a test.

Starting1 steps5,247 tokens
  1. Started the computer

Started the computer

Message Checkout retries

Your first agent in three steps

Connect GitHub once. After that, every agent and automation works from the same repositories.

Kliff3 repositories

  1. Connect GitHub

    Install the GitHub App on the repositories Nexus may read, and group them into projects if they belong together.

  2. Start an agent

    Pick a project or up to five repositories and describe the work. The agent clones them onto its own computer.

  3. Come back any time

    The computer sleeps when the agent is idle and keeps its files, so your next message picks up where the last one stopped.

Everything your teams need to run agents

Metrics, shared memory, and verification, on top of agents and automations that share your repositories, guardrails, and credits.

  • Metrics for every team

    See runs, pull requests, and cost for each team, member, and repository, so leads know where agent time goes.

  • Memory your organization shares

    What one agent learns about your codebase, every agent can use: conventions, decisions, and fixes that worked.

  • Checked before review

    A verification layer checks each change against the request and your tests before anyone is asked to review it.

  • A computer of its own for every agent

    Each agent works on a project or up to five repositories on its own computer, and keeps its files while it sleeps.

  • Reviews on every pull request

    Nexus Review comments on the lines its findings are about. It never approves, so merging stays with your team.

  • Issues into draft pull requests

    Mention @nexus implement or add a label, and a draft arrives on its own branch for your team to review.

  • Automations your team sets once

    Run your team’s instructions on a schedule, on each pull request, or when CI fails.

  • Tools your admins approve

    Owners and admins add remote MCP servers and switch on each tool. No tool runs until it is allowed.

  • One credit pool for the organization

    Credits refill every week at model list price, and every agent turn and run shows what it used.

Built on tools you already use

GitHub holds the work, Claude Code drives every agent, Cloudflare runs the computers and models, and MCP brings in your own tools.

  • GitHub
  • Claude Code
  • Cloudflare
  • Model Context Protocol
  • Kimi

Questions, answered

Agents, automations, safety, and credits, in short answers.

  • Sign up, install the Nexus GitHub App on the repositories you choose, then start an agent on a project. To try automations, comment @nexus review on a pull request.

Start with one agent

Connect GitHub, pick a project, and send your agent its first task.

Start an agentSee pricing

Free plan includes 1,000 credits a week