Skip to content

Factory 0.4.0 — self-hosted models for cloud lite workers

Choose a tag to compare

@flujo-app flujo-app released this 03 Nov 20:43
83cf503

Cloud lite workers can now run on a self-hosted, OpenAI-compatible model instead of the subscription login. Install without npm registry credentials:

npm install https://github.com/flujo-app/FACTORY/releases/download/v0.4.0/flujo-factory-0.4.0.tgz

New in 0.4.0. All of it is optional; existing plans behave as before, except that streaming deltas are no longer traced:

  • plan.modelProvider with deploy(plan, { providerKey }): Codex workers use your model through the Responses API, with its real context window and compaction point. The key stays inside the Codex process.
  • deploy(plan, { deployKey }): a read-only SSH clone with GitHub's host key pinned, instead of a GitHub token.
  • plan.prepare: a per-machine hook that prepares each agent's folder.
  • plan.supervision: 'operator', plan.sandbox, plan.boardTools: false: operator-driven jobs in a narrower sandbox.
  • Less trace volume: streaming deltas are not recorded (plan.traceDeltas: true restores them); plan.monitorIntervalMs sets how often machines read operator commands.
  • Transitive dependencies are refreshed for current security advisories; the production audit reports none.

PUBLIC_SDK.md has a short guide with Qwen3.8-27B (H100) and Nemotron 3.5 Super VL NVFP4 (B300) examples, plus numbers from a 190-agent coding run on one B300. SHA256SUMS.txt binds the downloadable tarball, which was packed from a clean export of the release commit. This release is distributed through GitHub Releases; it is not an npm registry publication.

Local release preflight on commit 83cf503 (same tree as the tested PR head): Windows Node 22.17.0 / 24.22.2 and Linux Node 22.17.0 / 24.22.2. Each run did a clean dependency install and the production high-severity audit gate (0 vulnerabilities). It passed 185 focused SDK/workflow tests per platform and runtime, the fresh tarball consumer, CLI help, installed MCP stdio and the evidence regressions. The release tarball itself was installed fresh and verified on Linux (Node 22.17.0) and Windows (Node 24.22.2).

No fresh model or cloud execution was performed for this release. The self-hosted provider path was exercised earlier on real Fly fleets. Offline checks do not establish live cloud execution or provider billing.