Integration · GitHub
AI agents that work inside your GitHub repository
Phloem does not host your code or ask your team to review inside a new tool. Agent work arrives as branches, pull requests and checks in the repository you already use.
- 01
Connect the repository
Phloem reads and writes through the GitHub provider adapter. Your repository stays the single source of truth; Phloem never becomes a second one and never edits protected branches.
- 02
One ticket, one branch
Each executable ticket gets a namespaced feature branch (phloem/ticket-…). Work is isolated, revertable, and readable as an ordinary diff by anyone on the team.
- 03
A normal pull request
The agent opens a pull request with the acceptance criteria, the change summary and the run that produced it. Your CODEOWNERS, required reviewers and branch protection rules apply unchanged.
- 04
Evidence bound to the head commit
GitHub Actions results, tests, dependency and secret scans, repository audit output and the preview deployment are attached to the commit SHA under review. If the head moves, the approval is stale and Phloem says so.
- 05
Human approval and merge
Agents can argue for a change; the merge button and the budget release stay with a person. Every approval records who, on which SHA, against which criteria.
What Phloem touches
- Branches
- namespaced, one per ticket
- Pull requests
- created, updated, commented
- Checks
- GitHub Actions normalized to one status model
- Commits
- evidence pinned to head SHA
- Protected branches
- read-only for agents
- GitLab
- same model via merge requests
Reviewing what the agents open
Two short guides cover the review checklist for agent-authored pull requests and the contribution policy that backs it.