Skip to main content
RUSTGRID
Launch RustGrid

GitHub-native execution

GitHub holds the code. RustGrid holds the mission.

Connect a verified GitHub App installation, bind a repository to a RustGrid project, and move engineering intent through agent execution, required workflows, pull request review, and a human decision.

Connect a repository Visit the GitHub organization

RustGrid’s core repositories are currently private. This page describes product integration, not an open-source core platform.

Repository binding

One verified path from project to pull request.

RustGrid binds the repository identity once, snapshots execution policy for the run, and follows repository events without treating webhook payload fields as tenant authority.

Repository / Example mission
Installation verified Run active
Repository bindingGitHub App
Repository
acme/payments
Project
PAYMENTS
Mission
Prevent duplicate settlement callbacks
Branch
rg/pay-142-callback-idempotency
Review action
Human-confirmed
mission
run
branch
pull request
Required validationPR #418
✓Local quality gatespassed
✓Required GitHub workflowspassed
·Human reviewwaiting
Prevent duplicate settlement callbacks +126 −34 · 4 files · ready for review

Illustrative product UI using a fictional repository and mission. It demonstrates the current integration model, not a customer claim.

A deliberate boundary

Keep each system authoritative for what it does best.

GitHub ownsCode source of truth
  • Repository identity and accessible inventory
  • Branches, commits, and pull requests
  • Checks, Actions workflows, and review events
  • The final repository state after merge or closure
RustGrid ownsMission source of truth
  • Mission requirements, constraints, and context
  • Worker assignment, lease, and execution policy
  • Run events, logs, gates, and refinement history
  • Human review state and the operational timeline

The live path

Connect once. Execute with bounded context. Reconcile every durable event.

The integration is more than a “Create PR” button. Installation ownership, repository access, run credentials, webhook identity, workflow state, and review all have explicit boundaries.

01 / VERIFYInstall the GitHub AppA tenant administrator starts setup; the callback binds the exact installation before user authorization verifies access.
02 / BINDSelect a repositoryRustGrid verifies App inventory and binds the repository to the intended project boundary.
03 / EXECUTEIssue run accessAn active leased run can receive a repository-consistent GitHub installation token through the worker boundary.
04 / VALIDATEObserve checksLocal gates and configured required GitHub workflows remain visible in the run history.
05 / REVIEWHuman decidesThe pull request is ready for review; an authorized human can accept or discard the result.

Product truth

Implemented integration, explicit deployment requirements.

“Available” means the current RustGrid contracts implement the behavior. It does not mean every deployment or GitHub organization is already configured for it.

Installation verification

Tenant-bound setup, one-time state, PKCE user authorization, exact installation verification, and accessible repository inventory.

Available
Repository bindings

Create, update, list, and remove project-aware repository bindings through the GitHub integration API.

Available
Webhook processing

Signature checks, delivery audit records, idempotent processing, and pull request or workflow reconciliation.

Available
Run-scoped access

The active worker/run boundary can request a token for the repository bound to that execution.

Available
GitHub App configuration

App credentials, callback URLs, HTTPS webhook URL, subscribed events, and repository permissions must be configured correctly.

Deployment required
Required workflows

The repository must expose the configured workflows and grant the App the permissions required to read their state.

Repository required
Agent execution

A compatible RustGrid worker and its configured execution environment must be online before a mission can change code.

Deployment required

Installation trust

Repository access is verified, not inferred.

RustGrid does not treat a callback parameter or old database row as proof that a tenant controls an installation. Setup binds the installation, verifies the initiating user’s access, and confirms the App’s current repository inventory.

Read the security model →
Tenant setup
single-use stateinstallation_id
User verification
OAuth + PKCE S256access check
App verification
installation activerepository inventory
RustGrid binding
tenantprojectrepository

The honest GitHub story

The organization is public. The core platform is not currently open source.

RustGrid’s core repositories are private today. The organization page is the source of truth for repositories intentionally made public. A public profile or integration with GitHub should not be read as a claim that the core control plane is open source.

Explore @RustGrid Ask about developer involvement

Integration questions

A control plane around GitHub, not a replacement for it.

Source of truth

Does RustGrid replace GitHub?

No. GitHub remains the code and pull request system. RustGrid adds durable mission context, execution state, policy, observability, and review coordination around it.

Credential boundary

Does RustGrid store user OAuth tokens?

The current installation flow uses user OAuth to verify access. OAuth access and refresh tokens are not persisted by that flow.

Configuration

Will any repository work immediately?

No. The GitHub App must have access and required permissions, the repository must be bound to a project, and a compatible worker must be available.

From intent to review

Give agents real repository work. Keep the merge decision human.

Connect a verified repository and make every run, check, pull request, and refinement part of one mission history.

Launch RustGrid See the full lifecycle