Skip to content

About

Scoped agent proposals, independent verification, and rootless Workcell execution

Topics

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

Kujo Software Factory

Version License built with Kujo Verification

Give a team of agents a software mission. Inspect what they built, what reviewers rejected, and which tests actually passed.

software-factory-demo.mp4

Software Factory coordinates scoped proposals through Kujo Dispatch, runs generated code inside rootless Workcell containers, and approves a local candidate only after independent checks. The Factory Floor lets you follow and replay the evidence.

Standalone, local, early release. Give your agent an idea and the software-pack guide. It can define the product contract and tests without rewriting the controller. Packs support Node APIs, SQLite when needed, and static browser interfaces. The issue tracker remains the default; converter and notes packs show other products. Agent City is not required.

Start here

Requirements: Git, Node 26.12.1 or later 26.x, a Codex account, and a local rootless Docker engine with seccomp. npm installs the pinned Kujo and Codex CLIs locally. No global Kujo installation or sibling repositories are needed.

git clone https://github.com/kujolang/software-factory.git
cd software-factory
npm ci
npm run setup
npm run login

Select a rootless engine following Engine setup, then:

npm run image:build
npm run doctor
npm run verify
npm run smoke
npm start

In another terminal in the checkout:

npm run factory -- run factory/mission.txt

Open http://127.0.0.1:4380. Each mission gets its own directory under .runtime/runs/. build/ appears only after successful local release verification. Model calls consume your provider allowance; setup, tests and smoke do not call a model.

Already signed in to Codex? npm run login -- --reuse-existing imports only the existing auth.json into a private, gitignored factory home. It never imports personal configuration, hooks, tools or instructions. Alternatively use interactive login above.

Let your agent install it

Give your agent this instruction and the repository URL:

Clone kujolang/software-factory and follow docs/AGENT-SETUP.md. Set up the pinned tools and rootless engine, then turn my software idea into a reviewed contract and tests using docs/PACKS.md. Validate and seal the pack before construction. Keep generated code inside Workcell. Help me complete sign-in when needed, and report any unsupported requirements. Run paid missions only when I authorize them.

The agent guide includes exact steps, success criteria and failure handling. The installation guide explains supported environments and prerequisites.

Build a different product

Your agent fills a pack from your idea, reviews its expected results and seals it. Run the idea against that pack:

npm run factory -- run idea.txt --pack packs/my-app.json

See the pack guide for the full workflow. Test the shipped converter and notes fixtures with npm run test:packs; this makes no model calls. Packs define tests as data. They cannot change the sandbox, run shell commands or approve their own output.

What happens in a run

  1. A commander interprets the mission and an architect defines scoped work.
  2. Backend and frontend proposal workers run concurrently.
  3. The controller admits only their allowed files.
  4. Independent review, API checks and browser checks gate bounded corrections.
  5. A separate release review and repeated checks bind approval to the exact source hash.

Workers propose text and files; they cannot run commands. Generated applications execute only inside Workcell. The observer is read-only. Model statements are never substituted for test results.

Operate and adapt

Scope

This is a local, single-operator factory. Workcell limits network, filesystem, process, memory and runtime access. These controls do not prove protection against kernel or runtime exploits. Hosted multi-tenant service, unattended crash recovery and public application deployment are not qualified. Windows users need Linux/WSL2; native Windows is unsupported. Platform qualification is recorded separately from intended compatibility.

MIT licensed. Kujo dependencies retain their own licenses. The included Departure Mono font retains its license.

About

Scoped agent proposals, independent verification, and rootless Workcell execution

Topics

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages