# Inside Kikimora: We Built a Dark Software Factory

## Executive summary

The video details the concept of a 'Dark Factory'—an autonomous software development model where processes run without continuous human supervision. The shift was catalyzed by coding agents (like Claude Code) accelerating development speed, which exposed bottlenecks in traditional workflows. This led to building internal orchestrators (e.g., Kikimora, Night Shift) that automate tasks from issue creation (Linear) through code generation and PR management (GitHub), fundamentally changing the role of the engineer from primary coder to system architect and trust validator.

## Key takeaways

- The Dark Factory Concept: A dark factory is an autonomous software building process where no humans are required for supervision. The core workflow involves creating a Linear issue, which is then picked up by an autonomous agent that solves it and opens/manages a GitHub PR until merge.
- The Bottleneck Effect: As coding agents increased development speed (starting around November), existing processes designed for slower software began to break down, forcing the company to adopt a fundamentally different, highly autonomous model.
- Shift in Engineering Value: The value of an engineer shifts from writing code (which agents can do better) to understanding complex system constraints, business logic, and the overall interlocking technical architecture. Trust in the automated results becomes the critical skill.

## Technical details

- Autonomous Orchestration: The factory operates by taking a Linear issue, having an autonomous agent solve it, and then 'babysitting' the resulting GitHub PR—making necessary changes in response to comments until the PR is merged.
- Internal Orchestrators: Early internal attempts included Night Shift (an orchestrator built for side projects with the rule 'don't look at the code at all') and Kikimora, which was an autonomous system that improved itself over time.
- Tessl Agent: The Tessl agent is designed to help companies build their own factories. Its purpose is not just writing code, but identifying and extracting workflows from existing silos, formatting them for agents, and uploading them to a skills registry.

## Practical implications

- The factory model allows non-development teams (GTM, People team) to utilize automated processes for tasks beyond coding.
- Adoption requires a cultural shift in engineering, moving from relying on individual coding ability to trusting and validating the results of autonomous systems.
- The process can dramatically accelerate development, with reports showing 90%+ of work being delegated to the cloud and increasing velocity by roughly 30% every two weeks.

## Topics

AI Automation, Software Factory, DevOps, Build Engineering, Workflow Orchestration, Tessl Agent

Source: https://www.youtube.com/watch?v=blDr-RLYuFI