As reported on November 14, 2026, Inkitt had built a “one-shot” pull request (PR) creator for small, low-risk software changes. According to an Inkitt Tech article, the system was already being used daily to deliver code. A task can arrive through Slack, Linear or an API call from another agent; the remote workflow then produces a draft PR for testing and review, without requiring a developer to set up and supervise a coding agent locally.
Inkitt principal engineer Agi Letkiewicz Tanner described the system as an event-driven orchestrator coordinating short-lived agent containers rather than a fixed pipeline. Separate stages handle requirements, implementation, validation, CI failure repair and merge-conflict resolution. The orchestrator saves each run’s state in a database so work can resume from a recorded point.
The design separates decisions from external actions: its core state-transition function determines what should happen next without directly accessing a database, network or language model. The orchestrator holds credentials for external services, while agent containers receive only short-lived repository tokens and model credentials. Agents cannot directly access Slack or Linear credentials or cloud identities, and cannot make arbitrary network connections. A separate check examines the actual Git diff for changes to restricted paths.
Inkitt rejects tasks involving database migrations; schema or shared-contract changes; CI or container-build configuration; authentication or payments code; and package additions or updates. Validation, CI repair and merge-conflict resolution are each limited to two attempts. To handle duplicate webhook deliveries, the workflow uses deduplication and conditional database writes. It also queries GitHub to confirm that all relevant CI jobs have finished rather than treating an individual job event as completion of the whole workflow.
Tanner wrote that, among the implementation challenges of idempotency, locks, retry budgets and permissions, “the model is the easiest part.” Human approval remains required: the system creates a draft PR, cannot bypass branch protections and cannot merge its own changes. Once CI passes and the change reaches staging, it notifies the requester. A person must then mark the PR ready for review and manage reviewer requests and approvals. For larger tasks, Inkitt also maintains a local version that keeps a person involved throughout development.



