Native Intelligence

Coding

Assign a task, get a pull request.

Give a task to the coding agent like you would to a developer on the team. It works on your repository in a fresh sandbox and opens a pull request for your review.

Works with GitHub

Small fixes pile up because writing them up takes as long as doing them. Here the task already exists: it came out of a call, an email or a channel, it sits in a project, and the project knows its repository.

The coding agent picks it up from there. It works from the task, writes its acceptance criteria first, makes the change, and has a second reviewer check the real diff before any pull request opens. The pull request stays linked to the task, so its state shows where your team already looks.

Hand it a task like a teammate.

Assign a task to a developer agent and press Start, or ask in chat for a code change. The run works on the GitHub repository set on the task’s project.

  • Start from the task itself, or from the chat
  • The repository comes from the project
  • Follow the run’s progress on the task as it works
  • Stop a run at any time

It checks the task is clear before it starts.

Before any code is written, a quick check reads the task. If something would risk building the wrong thing, the run asks you once. Then it writes the acceptance criteria the change has to meet.

It works on a copy of your code.

Each run starts a fresh sandbox with your repository checked out on its own branch. It reads the code, makes focused commits and pushes only its own working branch. Your GitHub token stays on our server and is never handed to the sandbox.

A second reviewer reads the diff first.

When the agent says it is done, a reviewer on a different model reads the actual change against the task and its acceptance criteria. It can send the work back for changes up to twice, or stop it.

  • Each criterion is marked as passed or failed, with evidence
  • A criterion it cannot judge opens the pull request as a draft
  • A rejected change opens no pull request

You review and merge, as always.

The pull request opens on GitHub, linked to the task. Your team reviews it and merges it the way it already does.

Every pull request finds its task.

Connect GitHub and a pull request that mentions a task’s identifier, like ENG-42, links itself to that task. When it opens, merges, closes or reopens, the task shows it.

  • Pull requests from people and agents alike
  • A flow can run when a linked pull request changes state
  • Ask the assistant for a pull request’s status in chat

It can fix its own failing checks.

Switch on the CI fix flow for a repository, and when checks fail on a pull request a coding run opened, it starts a fix run on that branch, at most twice per pull request. Its instructions rule out deleting or weakening a test to turn the checks green.

Questions

Works with

Bring your team into one workspace.
Try it free for 7 days.