Merkava + GitHub
ship fixes as PRs, sync repo signals. The AI executive team reads and writes GitHub directly — no Zapier, no glue code.
Beacon, Webster, Redline
The Drives that do the actual reps.
Connect GitHub. Hire the team.
Run a free audit on your domain to see what would ship in the first week.
Run auditCommon questions.
What does Merkava do with GitHub?
ship fixes as PRs, sync repo signals. Specifically, Beacon, Webster, Redline read from and write to GitHub as part of their normal motions — no glue code, no Zaps, just direct integration via the Platform Contract.
Do I need a paid GitHub plan?
If GitHub requires a paid plan for API access, yes — Merkava connects through your existing GitHub account and respects whatever tier you're on. We don't proxy or resell GitHub.
What writes happen automatically?
By default, Merkava operates in "review-each" mode for any GitHub write — every action waits for your approval. As trust builds, the trust ladder lets you auto-approve low-impact writes. You can pin any action class to manual permanently.
What happens if I disconnect GitHub?
Drives that depend on GitHub pause cleanly. No data is deleted from your GitHub account. You can reconnect anytime from /settings/integrations.