Code delivery

Keep GitHub delivery tied to the request that started it

Launch coding work from a card and return the branch, checks, and pull request to its review and acceptance path.

Join the waitlist See the GitHub example

GitHub with Aestus

Keep the tool. Change what the team can see.

An administrator installs the GitHub App and selects repositories. The agent does not need a broad personal token. When a card points to an installed repository, Aestus keeps the branch, commit, checks, and pull request with the original requirement.

Delivery is not acceptance. A bot-authored pull request can arrive while the card remains in review, and merge can require another actor. Aestus records the coding run once. GitHub supplies the code artifact and check state.

Good first workflows

Open a coding-agent pull request
Use the installed app to create the branch, commit, and bot-authored pull request.
Keep checks with acceptance
Return check state to the requesting card before a reviewer makes the final decision.
Limit repository reach
Let an administrator choose the repositories instead of distributing broad personal tokens.

A complete GitHub example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What delivery looks like in GitHub

The repository-scoped app opens the branch and pull request, then sends checks and review state back to the card.

aestus / import-servicePull request

Reject malformed currency separators #184

Open aestus-code wants to merge 3 commits into main

Aestus Code commented now

Implements AES-482. Adds three malformed fixtures and keeps the valid EU import matrix unchanged.

All checks have passed

●Import suite · 19 passed
●Typecheck · passed
●Policy gate · satisfied

Merge pull request

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Deliver a governed change through a repository-scoped GitHub App

A coding task targets one installed repository. Aestus Code creates the branch and returns a bot-authored pull request for review.

TriggerAES-544 starts against aestus/import-service

1
Organization admin
Limits the GitHub App to the import-service repository
Repository access comes from the installation, not an agent’s broad personal token.
1 repository authorized
2
Aestus coding agent
Creates a task branch and commits the patch
The repository, branch, and commit are bound to the task that requested them.
aestus/AES-544 · 4d8b1ac
3
Aestus Code
Opens the pull request and reports checks
Delivery arrives on the card while acceptance remains pending.
PR #226 · 11/11 checks
4
Lena · Reviewer
Approves the pull request and accepts the card
Review, merge, and task acceptance remain named decisions instead of one implicit state.
reviewed · merged · accepted

Example — fictional team and data. Not a live run or customer result.

Deterministic product example — not a production run

Open the governed import pull request

Example run		Runtime	Outcome
EXAMPLE-GH-01	Aestus coding agent	aestus	Completed	$0.01	42.0s

Tokens in / out: 14,000 / 300
Failure code: —
Agent: coding-agent

Example source: lib/marketing/integration-run-examples.ts

Example run cost

$0.0126 in the deterministic product example

The complete checked-in example defines the run cost and 14,000 input tokens. GitHub is the delivery surface, not a second model charge.

Set it up in four steps.

Follow the real GitHub connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Open the organization integration
An organization admin opens Settings, Integrations, then GitHub in Aestus.
Aestus contract: docs/github-app-setup.md
02
Install Aestus Code
Choose Install Aestus Code and select only the GitHub repositories the organization needs.
Aestus contract: docs/github-app-setup.md
03
Link a repository to the task
Select the installed repository for the Aestus card before the coding run starts.
Aestus contract: docs/github-app-setup.md
04
Launch and review the pull request
Move the coding task into progress; the GitHub App creates the branch and returns its bot-authored pull request.
Aestus contract: docs/github-app-setup.md

The boundary stays visible while the work moves.

See what GitHub can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Installation is administrator-owned

Aestus never asks a coding agent to grant repository access.

Repository scope stays explicit

GitHub App installation selection limits which repositories Aestus can reach.

Delivery gates remain separate

Opening a pull request, reviewing it, and merging it can be distinct governed steps with named actors.

What Aestus records

Source and result

Repository, branch, commit, pull request URL, and check state remain attached to the card.

Run economics

The coding run records tokens, latency, and cost; GitHub delivery is an artifact of that run.

Failure evidence

No changes, failed checks, sandbox authorization, and review rejection receive stable failure codes.

Questions teams ask

Which GitHub permissions does Aestus get?

The GitHub App receives only its declared permissions and only for repositories selected during installation.

Who opens the pull request?

The installed Aestus Code GitHub App opens the bot-authored pull request for the launched coding task.

Does Aestus merge automatically?

Only if the workflow policy and approval assignment allow it. Pull request review and merge can remain human steps.

See all integrations See the security controls

Start with one GitHub run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Deliver a governed change through a repository-scoped GitHub App

A coding task targets one installed repository. Aestus Code creates the branch and returns a bot-authored pull request for review.

TriggerAES-544 starts against aestus/import-service

1
Organization admin
Limits the GitHub App to the import-service repository
Repository access comes from the installation, not an agent’s broad personal token.
1 repository authorized
2
Aestus coding agent
Creates a task branch and commits the patch
The repository, branch, and commit are bound to the task that requested them.
aestus/AES-544 · 4d8b1ac
3
Aestus Code
Opens the pull request and reports checks
Delivery arrives on the card while acceptance remains pending.
PR #226 · 11/11 checks
4
Lena · Reviewer
Approves the pull request and accepts the card
Review, merge, and task acceptance remain named decisions instead of one implicit state.
reviewed · merged · accepted

Example run

Runtime

Outcome

EXAMPLE-GH-01

Aestus coding agent

aestus

Completed

$0.01

42.0s

Questions teams ask

Which GitHub permissions does Aestus get?

The GitHub App receives only its declared permissions and only for repositories selected during installation.

Who opens the pull request?

The installed Aestus Code GitHub App opens the bot-authored pull request for the launched coding task.

Does Aestus merge automatically?

Only if the workflow policy and approval assignment allow it. Pull request review and merge can remain human steps.

Keep GitHub delivery tied to the request that started it