Engineering agents, and the coding agents you already use
Ready-made agents on OrchKernel, the operating system for the AI-native company. They open incident records, give every pull request a first review, watch dependencies and brief whoever is on call. Outside coding agents act through the same gate.
Hours go to toil around the code, and coding agents act unchecked
Pages start from zero
Pull requests wait
Coding agents hold real keys
Four agents, plus the ones you bring
The Engineering module comes with playbooks, tools, rules and a scorecard per agent. Outside agents get their own identity and act only through the gate.
Engineering
Incidents, pull requests and dependencies for an engineering team.
Incident Responder
Turns a page into an incident record with impact, correlated errors and suspect changes.
- Starts
- When a page arrives or errors spike.
- Waits for
- The mitigation decision stays with the on-call engineer.
PR Reviewer
Gives every pull request a first review, rates its risk and drafts the comment.
- Starts
- When a pull request opens, plus a morning sweep.
- Waits for
- Its comment reaches GitHub only after the reviewing engineer approves the exact text.
Dependency Auditor
Keeps the dependency picture current across repositories and raises the advisories that matter to each owner.
- Starts
- Daily.
- Waits for
- Nothing to approve. It reports to owners.
On-call Summariser
Writes the one-page handover briefing for the engineer coming on call.
- Starts
- At each on-call handover.
- Waits for
- Nothing to approve. It writes the briefing.
Agents you already use
Claude, Cursor or your own code, governed like any other agent.
Outside coding agents
Get their own identity and act through the governed actions API, its TypeScript and Python clients, or the MCP gateway.
- Starts
- When they ask the gate to act.
- Waits for
- Whatever your rules say. The answer is allowed, needs approval or denied, with the reason.
Every agent acts for someone and earns its trust
A review comment reaches GitHub only after the engineer approves the exact text.
Review comments need the reviewer
The module ships with a rule: an agent's review comment reaches GitHub only after the reviewing engineer approves the exact text.
Outside agents never hold your keys
OrchKernel runs each approved action with its own credentials, sealed at rest.
Trust is earned
Trust is earned: sandboxed, standard, trusted. Riskier actions need more trust. The Engineering module's agents start at standard.
Outbound calls are checked
Every outbound request is checked against your list of allowed hosts.
Agent changes go through review and a canary
Changes to an agent go through review and a canary that rolls back automatically. Every action lands in a tamper-evident log.
Engineering questions
Start with one engineering workflow
Bring one real workflow, such as PR review or incident intake. We help you run it on your own systems.