Repository navigation
On PAR Dev's Software Factory v0.9.2
On PAR Dev's Software Factory 0.9.2: a public-repo cleanup, factory feedback filing in your own repo, and first-run reliability fixes. All seven @on-par packages are at 0.9.2 in lockstep.
On PAR Dev's Software Factory is a local CLI that takes a GitHub issue through plan, build and check with AI agents, then opens a PR for you to review. You decide what merges.
Install or update (Node 24 or newer):
npm install -g @on-par/factory-cli
factory --version
factory doctor
(Already on 0.9.1? Run npm install -g @on-par/factory-cli@latest.)
Changed
factory feedbackfiles its issue in your own repo:--repo owner/name, then the newfiling.repoconfig key, then the checkout'soriginremote. It no longer falls back to on-par/software-factory; with no repo it stops with a clear error (#2398).- The feedback issue leaves out your host name and local design and log paths unless you pass
--include-local-paths(#2398). - Upstream factory reports have no built-in target repo either. Without an explicit repo they are skipped with reason
no-target-repo(#2398). - Public-repo cleanup: internal operations notes and research removed from the docs, and broken doc links fixed (#2398).
- The CLI refuses to start on Node below 24 with a clear message, before it loads
node:sqlite(#2390). factory doctorruns outside a repo, checks your git identity, and warns when no sandbox runtime is available (#2391).- Readiness keeps the original issue body when enriching it and adds an opt-out (#2395).
Added
- factoryd checks for updates every 30 minutes, drains, self-updates and restarts via launchd, and skips versions that failed (#2375).
Fixed
- The model router skips Ollama models when Ollama is unreachable, and triage logs the model it actually runs (#2394).
factory shipdetects a repo with no CI checks early and logs CI wait progress (#2396).
Full changelog: v0.9.1...v0.9.2