I built Code Factory after losing time to AI-generated tests that passed but failed in real use. The front door is now deliberately simple: run `factory first-proof --root .` and see a safe demonstration of whether a test can actually reject a known failure. It stays local and does not change your project.
For a solo developer or vibe coder, that is the whole starting value. For a team, `factory wrap` records the exact file delta from an admitted agent run, runs the validators the team declared, and leaves a reviewable receipt without retaining prompts or raw model output. Platform and assurance teams can evaluate the deeper policy and evidence controls in a pilot, but this beta does not claim an SLA, certification, customer references, or procurement readiness.
Version 0.44.3 also compares declared and observed product journeys, preserves the failed step in a bounded evidence capsule, checks state and cleanup, and audits the repairing agent separately. Human approval, apply, merge, release, credentials, and deployment remain outside Code Factory's authority.
Try it: https://pypi.org/project/factory...
A plugin integration for IntelliJ or VS Code would be huge, letting devs trigger the spec-to-ship pipeline right from the editor without context switching. Maybe even surface the receipt inline.
@yusuf363917 Yusuf — this is exactly the right instinct. The receipt is most useful at the diff, in the editor, at the moment you're deciding whether a change is safe — not in a separate report you read after the fact. Surfacing HOLLOW_TEST / HOLLOW_POLICY inline, right where you'd act on it, is precisely where this should go.
To be straight about where it is today: the CLI runs now — pip install factoryline-code-factory, then factory verify-tests (or verify-policy) on any real repo. The editor integration you're describing is the natural next layer on top of that, not built yet — but you've just articulated the cleanest version of it, so it's going on the roadmap with your name on the thread.
Two things I'd genuinely value: which editor are you in — VS Code or JetBrains? The recent upgrade covers both VS code and Jetbrains all 8 adapters
Release update: the editor layer is now shipped. Code Factory 0.13.3 includes the JetBrains adapter and VS Code extension, attached to the public release. ForgeLine 0.10.6 adds portable JS/TS validation and safer existing-source adoption.
We also changed factory doctor so installation, executable workflow checks, and provenance are separate facts: no false green. Verified in clean environments: 77 ForgeLine tests, 121 FactoryLine tests, builds, artifact checks, clean-wheel smoke, and a five-brick strict source-train doctor pass.
Releases: https://github.com/zrk222/code-factory/releases/tag/v0.13.3
ForgeLine: https://github.com/zrk222/code-factory-2-forge/releases/tag/v0.10.6
I have seriously updated the Code-Factory to be more robust, produce higher quality outputs, will save time, tokens, and now designed to work with enterprise teams