Add Forge to GitHub. Ship from issues.
Install the GitHub App on a repo, mention Forge on an issue, review the plan, then approve execution. Forge inspects the code in E2B, pushes a branch, and opens a pull request for you to review.
Install Forge
Choose the repositories Forge can access.
Create an issue
Add the `forge` label or comment `/forge plan`.
Revise or approve
Use `/forge feedback ...` or `/forge approve`.
Review the PR
Branch, checks, risks, and PR link stay in GitHub.
What Forge does
The production system is built around GitHub, E2B, approval, and PR review.
GitHub App Workflow
Users install Forge on repos and work entirely from GitHub issues and pull requests.
E2B Execution
Repository inspection, implementation, and validation run in isolated E2B environments.
Approval-first Plans
Forge posts a readable engineering plan and waits for `/forge approve` before editing.
Pipeline Skills
Issue intake, inspection, planning, implementation, validation, review, and PR handoff are separate agent skills.
Repo-level SKILL.md
Projects can teach Forge their setup, test commands, boundaries, and review rules.
Pull Request Handoff
Forge pushes `forge/issue-{N}`, opens a PR, and reports checks, changed files, and risks.
How it works
A GitHub-native pipeline with human approval before Forge changes code.
- 1GitHub sends Forge the issue event
- 2Forge starts an E2B sandbox for repository inspection
- 3The planning pipeline reads code, config, and repo SKILL.md guidance
- 4Forge posts a maintainer-readable plan in the issue thread
- 5The user gives feedback or approves with /forge approve
- 6The implementation pipeline edits, validates, and reviews the diff
- 7Forge pushes forge/issue-{N} and opens a pull request
- 8Maintainers review checks, risks, and the PR before merging
Connect once. Work from GitHub issues.
Users do not need to clone Forge, configure E2B, or run a terminal. Your production deployment handles the agent runtime. They only install the GitHub App and use issue comments.
Add Forge to a repositoryRepo-level guidance
Add SKILL.md, .forge/SKILL.md, or .github/forge/SKILL.md when a repo needs custom setup, validation, or review rules.
Install the GitHub App
Choose your account or organization, then select the repositories Forge is allowed to work on.
Tag an issue for Forge
Add the `forge` label or comment `/forge plan`. Forge inspects the repo in E2B and replies with a plan.
Approve before changes
Comment `/forge feedback ...` to revise the plan, or `/forge approve` when it looks right. Forge then edits, validates, pushes a branch, and opens a PR.
Review and merge
The PR includes changed files, validation output, and risk notes so maintainers stay in control.
Commands users need
/forge plan/forge feedback use X instead/forge approve/forge review