Fractal
  1. 01The problem
  2. 02What a software factory is
  3. 03Building blocks
  4. 04How it works
  5. 05Get started
  6. 06Real numbers
  7. 07Community

Research previewEarly research results, not a finished product. Expect rough edges and breaking changes.

Build your own software factory

A batteries-included framework to build your own software factory

Focus on what matters. The factory does the rest.

Copies a setup prompt for Claude Code, Codex, OpenCode or any coding agent.

Understand FractalJoin Discord

The problem

You’re still babysitting your agents

Coding agents got good. Running many of them still means starting and steering every one, reading their chats all day and being the bottleneck for work getting done.

  • Babysitting agents

    Starting, steering and context switching between agents is draining. Your attention is the bottleneck.

  • Noisy questions

    Constant inconsequential questions, or work built on wrong assumptions.

  • Stops when you stop

    Close the laptop and the work stops with it.

  • Waits for prompts

    Agents only act when you prompt them.

  • Sessions die

    Sessions die and lose their progress.

  • Invisible work

    You can’t see what your agents are actually doing.

Thirty-nine open terminals isn’t a factory. It’s you, doing the factory’s job.

What a software factory is

A system that produces software to meet a set of goals

For most of your career, you’ve been the software factory: you set the intent, did the work and read the feedback. In an agentic software factory, agents take over the work and the feedback. You stay at intent.

  1. IntentYou define the goals.
  2. WorkAgents do the work.
  3. FeedbackResults flow back and inform the next round.

The loop closes: feedback goes back to intent, and the factory runs it autonomously.

Fractal is a software factory framework

Think Legos for agents: small building blocks that snap together into your own factory. Open source, running on your machines with your accounts, and agnostic to harness, model and vendor. You don’t work in the factory. You own it.

Building blocks

Small pieces that snap together

Agent sessions, transcripts and turns don’t compose into long-running plans. Fractal gives agent work composable boundaries.

  • agent

    Agents

    Durable agents on your own machines, each bound to its harness (Claude Code, Codex, OpenCode) and model. Declared once, restarted when they die.

  • mission

    Missions

    Structured, executable plans: a goal, constraints and steps whose dependencies form a DAG. Long-horizon work without a 5,000-line PLAN.md.

  • gate

    Gates

    Every step says how you know it’s done: tests pass, it renders, platforms stay in parity. Human gates where it matters.

  • attention

    Attention

    A structured attention system. Only what needs you reaches you, so signal beats noise even with dozens of agents.

  • client

    Clients

    Web and mobile clients, the harnesses you already use, chat and platforms like Slack or GitHub, or your own via the client API and MCP.

How it works

Everything is a declaration or an observation

Your factory is code. Fractal keeps what you want and what actually happens in one store, and reconciles the two.

  1. 01

    Declarations

    Agents and missions, written in KDL or typed TypeScript. fractal apply puts them into the store.

    factory.kdl
    agent "maintainer" {
  workspace "/work/app"
  harness "codex" {}
  restart "always"
}

mission "update-deps" state="ready" {
  goal "Dependencies up to date"
  step "update" timeout="1h" {
    assigned-to "agent/maintainer"
    goal "Pull request with updates, CI green"
  }
}

  2. 02

    Replicated store

    A SQLite store replicated across your machines: laptop, dev server, cloud VM. fractal up on each machine reconciles declarations into running agents.

  3. 03

    Observations

    What actually happens flows back into the same store: agent sessions and transcripts, mission progress, pull requests and CI, and whatever plugins observe.

Clients read the normalized store through the client API or MCP.

Get started

Adopt it incrementally

Pick the path that fits where you are today.

  • Run your first mission

    Adopt Fractal for a single mission on the setup you already have. Your agent can do the setup.

  • Improve your agent setup

    Make your current agent development environment better: durable agents on your machines, any harness, usable from any device.

  • Build your full factory

    Declare agents and missions, wire up gates, attention and clients, and extend it all with plugins.

Not ready to adopt yet? Join the Discord and roll up your sleeves with us.

Real numbers

What our own factory does

We build Fractal with Fractal. These numbers come from our own factory once they’re measured and verified.

Merged pull requests per night
TODO
Declared agents
TODO
Machines in the factory
TODO
Missions completed
TODO

Community

Everyone is still figuring out software factories. So are we.

Fractal is open research and an invitation to learn and build together, not a product pitch.

  • Discord

    discord.com/invite/7PbaSUxcy

    Questions, feedback and what you’re building.

  • GitHub

    github.com/compoundingtech/fractal

    Source, issues and pull requests.

  • X

    x.com/compoundingtech

    Updates and research notes.

  1. Use it
  2. Share feedback
  3. File issues
  4. Send fixes
  5. Build plugins
  6. Improve the clients with us