A FACTORY THAT WORKS YOUR WAY

Your process.
Less machinery to maintain.

Ask your coding agent to write the workflow YAML. Weft runs the process and keeps the work records. Start with the included development flow and change it as you go.

Get launch updatesSee a first task →

Complete local OSS. Free under Apache 2.0. No subscription or Weft Cloud account required. Bring your own model access.

START WITH A FLOW / MAKE IT YOURS
01 / START WITH SDLC
  1. Design
  2. Implement
  3. Verify
02 / ADAPT YOUR PROCESS
  1. Design
  2. Implement
  3. Your review
  4. Verify
The same Weft engine.Your stages. Your checks. A reusable process.

Illustrative flow · customize stages and checks in your project.

Run the next task with your revised process and the same engine.

WHEN THE PROCESS BECOMES ANOTHER PROJECT

Keep the parts that make it yours.

Fewer handoffs to rebuild.

Save the steps in a workflow file. Let the engine move the work between them.

A new session loses the thread.

Keep tasks, progress, and project decisions outside the chat. Give the next agent a record to continue from.

Checks that fit your work.

Choose which checks are required. A failed check holds the affected task for a fix.

START WITH ONE TASK

Start with the task you already have.

At launch, connect your coding agent and use the included development workflow for a small change. See it run before deciding what to change.

Use Weft’s included workflow for this task. Run our repository checks and show me the result. Record any project decision we will need again.

Follow a first task →

Already have a factory?

Pick one handoff you keep repairing. Let Weft track that task through your existing checks. Inspect the outcome before moving more work over.

What work stays with me?

You own the workflow, the checks that define acceptance, and your custom integrations. Weft supplies the common execution machinery. Keeping a custom check useful still takes work.

What about my agents and models?

Your existing agent can use Weft through its CLI or MCP tools. Keep your model access and provider accounts. For managed work, choose the execution engines supported by your workflow.

CHANGE THE DEFINITION

AI writable.
Human readable.

Describe the process you want. Your coding agent can write the YAML. You can read the stages, see what must pass, and review the change before using it.

Save it with your code. Use the same definition for the next task, then improve it from the results.

Open the workflow file →
THE RULE / THE HANDOFF IT CONTROLS
.weft/process.yaml · excerpt
gate_bindings:
  - transition: {from: in_progress, to: completed}
    gate: verification
    auto: true
  1. 01 / AGENTImplement
  2. 02 / REQUIRED GATEBuild + testverification
  3. 03 / AFTER IT PASSESCompleted

The binding names an included executable check. The workflow file says where it must pass.

Complete the task only after the check passes.

A GENERIC ENGINE / A USEFUL STARTING POINT

A workflow file is enough to begin.

Software development tools and a working flow come included. Ask your coding agent to edit the YAML or write a workflow for a different process.

Weft runs the steps and keeps the work moving through your checks. You can build your own plugin when you need tools the included set doesn’t supply.

See how stages and gates work →
YOUR DEFINITION / REUSABLE MACHINERY
YOU DEFINEHow the work should happenStages · transitions · acceptance checks
INCLUDED TOOLSSoftware developmentTasks · decisions · tools · stock workflow
WEFT CORERun the processWorkflow execution · workers · tools

Architecture illustration · software development is one use for the engine.

Complete OSS on your machine.

Task records, project memory, workers, workflows, and gates run locally. Free and open source under Apache 2.0. No Weft Cloud subscription is required.

The optional Cloud plugin adds hosted state shared across people and machines, plus AI review. See the service boundary →