GATE's AI coding agents work the way a careful developer does: your agent turns a request into a GitHub issue, a coding session builds it in its own copy of the repository on its own branch, and the work comes back as a pull request that is reviewed before it is merged. A site hosted on GATE deploys on every merge. On GATE, a certificate platform with 239 active sites has anything reported triaged in under a minute.
Every change takes the review path a careful developer would use.
Tell your agent what you want built or fixed. It writes the request up as a GitHub issue, so the intent is on record before any code changes.
The session works in its own copy of the repository on its own branch. You can watch it live in the chat's code session window and stop it at any time.
The work comes back as a pull request on your repository. The session reviews its own diff before your agent merges, and your repository's own branch rules still apply.
A site hosted on GATE deploys every push to its deploy branch, merges included, and runs database migrations before it starts. Undo is a git revert.
A one-line fix goes straight onto the main branch only when you explicitly say inline, and never for database changes, sign-in, billing or anything touching more than a couple of files.
Not by default. There are two paths, and the pull request is the default.
Pull request unless you say otherwise.
Pull requests are the default for everything. Inline, straight onto the main branch, needs your explicit word and never covers database changes, sign-in or billing.
Built into how GATE runs code work.
Coding is one job. The tools around it are GATE's own.
From a sentence to an issue, a branch and a pull request, on your repositories connected to GATE.
A GATE Site runs your app with its database, cache and storage, deploys every push to the deploy branch and restarts a service that stops answering.
Every file, class, function and import, grouped into areas with plain summaries and tours, and a coding session in a mapped repository is told the map exists.
Point at an element on your real page, your agent edits it while you watch, and building turns it into a pull request for a site on GATE.
A security agent tests your own application inside the scope you set, verifies each finding before reporting it and retests after your fix.
One board your team and your agent share, where tasks are created, claimed and completed and can be attached to the chat they came from.
Three ways a small company gets code written, side by side.
| What you compare | Hiring a developer | A code assistant in the editor | GATE's AI coding agents |
|---|---|---|---|
| Who writes the code | The developer | You, with suggestions as you type | A coding session, from a request in plain language |
| Where the work lands | Their branch and pull request | Your editor, then wherever you commit | An issue, its own branch and a pull request |
| Review | A colleague, if you have one | You, line by line | A self-review pass before merge, plus your branch rules |
| Deploy | Your own pipeline | Your own pipeline | A GATE Site deploys on merge; undo is a revert |
| What it knows about your code | What the developer remembers | The files you have open | A map of your codebase, if you build one |
| How you start | Weeks to hire | Install it in your editor | An invite and your repository connected to GATE |
| What it does not do | Anything outside the role | Run or deploy the code | Preview environments per pull request, autoscaling or backups |
A certificate platform with 239 active sites runs on GATE: anything reported anywhere is triaged in under a minute. A Swedish business marketplace ships product end to end with no project manager in the loop.
See the customersAI coding agents are AI agents that write and change code themselves instead of only suggesting lines. In GATE, your agent turns a request into a GitHub issue, starts a coding session that builds it in its own copy of the repository on its own branch, and the work comes back as a pull request that is reviewed before it is merged.
Not by default. GATE's coding sessions always work on their own branch and open a pull request. A small fix goes straight onto the main branch only when you explicitly say inline, and GATE's rules keep database changes, sign-in, billing and anything touching more than a couple of files on the pull request path.
The coding session reviews its own diff first. Your GATE agent then merges, and only once the required checks pass: a failed check stops the merge, and checks still running hold it for up to 6 hours. GitHub's branch rules apply to the account GATE merges as, and admins skip classic branch protection unless you turn that off. You can watch any session live and stop it, and a revert undoes a merge.
Yes, if your app runs as a GATE Site. GATE deploys every push to the deploy branch, merges included, runs database migrations before the app starts, restarts a service that stops answering and logs every deploy with its trigger, commit and duration. GATE has no rollback button: a git revert is the undo.
Yes, in three ways. GATE's agent can run and save an SEO audit of your site with GATE's own analytics tool, map your codebase with eight snag rules such as long functions and unused files, and run a security test of your own application inside the scope you set. The fixes then take the normal path: an issue, a branch and a pull request.
It can start from a map. GATE builds a codebase map of every file, class, function and import, grouped into areas with plain-language summaries and guided tours, and a coding session started in a mapped repository is told the map exists and how to read it. Without a map, the session reads the code it needs as it works.
Not to write the code. You describe the change in plain language, and GATE's agent files the issue, runs the coding session and explains the pull request. Someone still decides what ships: your agent merges only after review and green checks, and a GitHub rule that requires a person's approval, and also binds admins, keeps that decision with you.
GATE's coding agents do not give you preview environments per pull request, autoscaling or backups, and GATE has no one-press rollback: a revert is the undo. Coding sessions work on repositories connected to GATE, and GATE does not run continuous integration for your repositories, so your existing tests and checks stay where they are.
GATE is invite only right now while it onboards a small number of businesses. Once you are in, an owner of your organization approves the GATE GitHub App once, your repository is connected as a site, and you ask your agent for the first change in plain language.
Invite only while we onboard a small number of businesses.