---
title: Inkitt deploys event-driven orchestrator for automated pull request creation
url: https://www.elseif.net/inkitt-deploys-event-driven-orchestrator-for-automated-pull-request-creation
published: 2026-11-16T19:05:39+00:00
language: en
section: Agents
source: https://www.infoq.cn/article/YRXscVHsTh0g6CVCJJ0D?utm_source=rss&utm_medium=article
organizations: Inkitt, Webhook
publisher: elseif
---

# Inkitt deploys event-driven orchestrator for automated pull request creation

Inkitt has implemented a one-shot pull request creator that automatically handles small, low-risk software changes. The system executes tasks from initiation to the generation of a draft pull request ready for testing and review. This workflow is triggered via Slack, Linear, or API calls from other agents and runs on remote infrastructure to reduce the need for local configuration and supervision by developers. The company reports that the system is currently used daily to deliver code.

The architecture functions as an event-driven orchestrator that coordinates short-lived agent containers rather than relying on fixed pipelines. Distinct stages manage requirement specification, implementation, verification, continuous integration failure repair, and merge conflict resolution. The orchestrator persists the state of each run to a database, allowing the execution process to resume from a recorded state if interrupted. This design separates decision logic from side effects, with a core state transition function determining the next action based on the current run state and incoming events without directly accessing databases, networks, or language models.

Security measures are central to the implementation. The orchestrator holds credentials for external systems, while agent containers only receive short-lived code repository tokens and model credentials. Agents cannot directly access Slack or Linear credentials, cloud identities, or establish arbitrary network connections. An independent check inspects the actual Git diff to ensure changes do not touch restricted paths. The system rejects tasks involving database migrations, schema or shared contract changes, continuous integration and container build configurations, authentication, payment code, or package additions and updates.

To handle reliability challenges, the system applies idempotency principles to workflows that may receive duplicate webhook events. It uses deduplication and conditional database writes to manage these repetitions. Verification, continuous integration repair, and merge conflict resolution are limited to a maximum of two attempts each. When determining if continuous integration is complete, the orchestrator queries GitHub to confirm that all relevant tasks have finished, rather than treating every task event as a signal of overall workflow completion.

Human approval remains a mandatory part of the process. The system creates draft pull requests and cannot bypass branch protection or merge changes independently. Once continuous integration passes and changes enter the pre-release environment, the system notifies the task initiator. A human must then mark the pull request as ready for review and manage reviewer requests and approvals. For larger tasks, Inkitt maintains a local version that keeps humans continuously involved in the development process. The design shares some safeguards with other coding agents, such as restricted permissions and mandatory human review before merging, but emphasizes persistent workflow state, limited retries, and centralized control over external operations.
