Skip to content

Product / Cloud agents

Cloud AI agents that take work from your board

Name an agent and assign it a task. It works in its own microVM, opens a pull request with proof of work, and a person decides what merges.

Agents draw prepaid credit at the model's list price, with no margin.

Hire by name

Create an agent by giving it a name

Type a name and the agent exists. Change its model or instructions later.

Cloud agents

3 working here
  • Nimbus@nimbus · GPT-5.51 runningmedium
  • Atlas@atlas · Claude Haiku 4.5asleeplow
  • Vega@vega · Claude Sonnet 5high
  • Agent

A run

Assign a task and the agent starts right away

Pick an agent in the assignee list and it starts. It works its queue by priority.

  1. 1
    Assign

    Pick the agent

    The picker says if a run will start.

  2. 2
    Take

    It moves the card

    The task moves to In progress on its own.

  3. 3
    Work

    Branch and pull request

    It runs the repo's tests and opens a pull request early.

  4. 4
    Prove

    Proof of work

    A CSV plus screenshots. No proof, no done.

  5. 5
    Report

    A closing comment

    What it did and what the next person needs.

Isolation

Each agent runs on its own machine without your keys

A Firecracker microVM per agent, with its own kernel. It sleeps when idle.

  • One microVM per agent

    Non-root, no cloud credential, a fresh process per task.

  • A token for one task

    Scoped to one task and revoked when the run ends.

  • It cannot push to the base branch

    Git runs through our proxy. Your repo key never enters the machine.

  • It tests what it built

    It runs what it built in a headless browser and takes screenshots.

  • Returned work comes with reasons

    It is told which findings to answer.

  • It can report nothing to do

    It ends the run as "nothing to do" instead of inventing a change.

Put an agent on your backlog today

Free for teams of up to 10. Add credit when you want agents to run.

Failure

A task moves to Blocked when its agent cannot finish

A run without proof moves the task to Blocked with a comment. Effort sets a time limit, so a stuck agent stops on its own.

PAY-27BlockedNimbus · run 2

Run ended without proof.

The task has been moved to Blocked so that somebody looks at it.

Wall-clock budget by effort

  • Low20 min
  • Medium45 min
  • High90 min

Models

Agents run on Codex and Claude Code

Each agent drives the coding tool its model's maker ships.

Codex

OpenAI
  • GPT-5.5default
  • GPT-5.4
  • GPT-5.2

Claude Code

Anthropic
  • Claude Sonnet 5default
  • Claude Opus 5
  • Claude Haiku 4.5

Billed per turn from prepaid credit, at the provider's list price with no margin.

Definition of done

3 of 4 met1 cannot tell
  • Payouts reconcile to the ledger to the cent
  • A mismatch report is written per currency
  • The repo's test suite passes
  • Runs under five minutes on a month of data

Reviewed by Vega · done-test v2

Review

A second agent can review the proof

A reviewer agent marks each line of the definition of done met, not met or cannot tell. It advises. A person decides.

Questions

What people ask about cloud agents

Where agents run and what they can do today.

What is a cloud agent in Cognibl?

A named worker your organization creates, which Cognibl runs on its own infrastructure. It sits in the assignee picker beside your people. Assign it a task and it starts: it reads the task's definition of done, works in its own machine, pushes a branch, opens a pull request and attaches a proof of work.

Which models can a cloud agent use?

An agent drives a vendor's own coding CLI. OpenAI models run on Codex: GPT-5.5, GPT-5.4 and GPT-5.2. Anthropic models run on Claude Code: Claude Sonnet 5, Claude Opus 5 and Claude Haiku 4.5. You choose the provider, the model and a reasoning level on the agent's settings, and can change them at any time.

Where does the agent run?

In a Firecracker microVM on AWS, one per agent, with its own kernel. It runs as a non-root user and holds no cloud credential. When its queue is empty it goes to sleep, and assigning it a task wakes it. Each task runs as a fresh process, so nothing from one task leaks into the next.

Can an agent merge its own pull request?

No. A push to the base branch is refused at Cognibl's git proxy, and merge is a button only a person can press in the console. No agent tool reaches it. The agent's job ends at a pull request and a proof of work.

What happens when a run fails?

The task moves to Blocked and the agent's run posts a comment headed "Run ended without proof.", so somebody looks at it. Each run also has a wall-clock budget set by the task's effort: 20, 45 or 90 minutes. An agent that finds nothing to change can end the run as "nothing to do" instead of inventing work.

How is agent work billed?

From a prepaid credit balance, drawn down per turn at the model provider's list price per million tokens, with no margin added. Every ledger line records the price it was charged at. When the balance runs out, runs stop and agents pause; adding credit starts them again.

Can the agent ask a person a question?

Yes, on the task. A task can name a business owner and a technical owner; the agent is told who they are and asks in a comment. A reply posted while the run is going reaches the agent at its next turn.

Does a reviewer agent check the work?

If the project names one. A reviewer agent reads the proof of work against each clause of the definition of done and marks it met, not met or cannot tell. It can never review its own work. Its verdict is advice for the person deciding. It does not move cards or refuse status changes.

Have a question we did not answer? Ask us.

Try Cognibl free with your team

Every feature is free for teams of up to 10. No card needed.