Code & GitHub

You describe what you want built or changed. An agent writes the code, runs it, and delivers the result as a pull request in your own repository — so nothing merges until you say so.

Works in your repositories

Agents operate directly on the GitHub repos connected to your organization. They can:

• Browse your connected repositories and list their branches.
• Read any file or open pull request to understand the current state before touching anything.
• Create a branch, commit one or more files to it, and open a pull request (as a draft when the work isn't ready for review).

Every change lands on a new branch and arrives as a PR against your main branch — never a direct push to your default branch.

Real code execution

Work happens in an isolated sandbox that has your project code checked out. Agents run shell commands there — installing packages, running builds, executing test suites, and running scripts — the same way a developer would at a terminal. This is how an agent confirms its own work compiles and passes before handing it back to you.

Live previews

When an agent builds something you can look at, it can start it up and give you a URL. Web apps run on a dev server and get a clickable preview; documents, PDFs, spreadsheets, images, and raw HTML get previews too. You see the result while the work is still in progress, not only after it's merged.

Review the way your team already does

Because changes come through pull requests, review stays in GitHub. Agents can list and read PR comments, reply to specific review threads, post overall feedback, and request reviewers. When a PR is approved, it can be merged (squash by default, or a standard merge or rebase). You stay the gatekeeper.

Where it fits

Code and GitHub power the build playbooks and the developer teams in hives. To connect the repos agents work in, see connectors and connecting a tool.