Skip to main content
FactoryOS

Run approved work on your machine

Use the customer-hosted runner or connect a coding client through MCP. FactoryOS keeps the approved scope, records the work and reviews its pull requests. Humans approve and merge.

Customer-hosted runner

The runner packages a pinned harness with its dependencies. Version 0.3.0-rc.1 is a preview with background pickup. The previous package completed native Codex subscription execution on macOS ARM64. See the release notes for this version’s qualification.

Install Node 22+, Bash 4+, Python 3.11+, Git, GitHub CLI and Codex CLI. Use an unlocked native credential store and a repository with runnable test, lint and verification commands.

  1. Download the runner archive, installer and their SHA-256 checksums. Verify both files before running the installer.
  2. Install and activate the package, then add its bin directory to PATH.
  3. Sign in to Codex and GitHub using your own accounts. Configure the repository with factoryos-runner init, or review the proposed configuration from configure for an existing harness. Commit the reviewed configuration.
  4. Sign in to FactoryOS with factoryos-runner login --server https://agentfactoryos.com.au/mcp. Choose your workspace and consent to its requested engineering scopes.
  5. Commit a trusted verification script that runs your repository's tests and lint. Enroll the repository with watch-configure, selecting approved paths and that script. Start its background service with watch-start --yes.
  6. Approve the specification and record customer execution in FactoryOS. Once its contract is ready, click Run on my runner. Your connected runner picks it up, runs coding, tests, review and QA, then opens and registers a PR.
python3 install.py factoryos-runner-0.3.0-rc.1.tar.gz   --sha256 6f837104e3bf0026af3e66de746a37c51c8f1bf5ae539b8aec4c901248918ca9   --prefix "$HOME/.local/lib/factoryos-runner" --activate
export PATH="$HOME/.local/lib/factoryos-runner/bin:$PATH"
factoryos-runner doctor --repo /path/to/repository
factoryos-runner watch-configure --server https://agentfactoryos.com.au/mcp --repo /path/to/repository --path src/ --path tests/ --verification-file /path/to/repository/scripts/runner-verify.sh --yes
factoryos-runner watch-start --server https://agentfactoryos.com.au/mcp --repo /path/to/repository --yes

The browser queues work; your installed service picks it up while your machine is awake and connected. Offline requests wait. Use watch-status to inspect it andwatch-stop to pause new pickup after current work drains. An explicit --pickup approved enrollment can pick up eligible approved work without a ticket click. Pause it before using another MCP client for the same work.

Archive SHA-256: 6f837104e3bf0026af3e66de746a37c51c8f1bf5ae539b8aec4c901248918ca9

Follow the bundled background setup instructions and the release notes for qualification and availability.

MCP coding client

Connect a client that supports remote streamable HTTP MCP and OAuth/PKCE to https://agentfactoryos.com.au/mcp. Sign in, choose your workspace and consent. Your client reads approved work and its contract, claims a work session, executes locally, registers the resulting PR and reads independent verification.

This route uses your client's own execution loop. Compatibility depends on the client's supported protocol and tools; a client name alone does not establish qualification. The installed runner uses the packaged harness for that loop.