VibeHard Agent Edition — Changelog

2.0.3 — October 16, 2026

• Your agent is told what to do. A connected agent now receives VibeHard’s working rules when it connects, and three ready-made prompts (vibehard-build, vibehard-status, vibehard-next) in agents that list MCP prompts.
• Every step says what comes next. vibehard_progress returns next_action: the current step (for example “PRD, step 2 of 8”), one plain sentence, the exact tool to call, and whether VibeHard is waiting on the agent or on you.
• Research is labelled honestly. vibehard_build_start accepts research_evidence, an agent’s own research, shown to the interview and the PRD as not REA. REA findings stay for apps that can actually be run or inspected, and a build that mentions replacing or rebuilding an app asks for the exact location and your rights to analyze it.
• Rules travel with the project. Folders VibeHard creates now contain AGENTS.md and a CLAUDE.md that points at it. VibeHard never touches your own global files.
• Capabilities are reported. vibehard_session_open and vibehard_install_info list what this install supports, and the first connection after an install carries a one-time welcome.
• Installer finish screen. A short “You’re ready” block says what to tell your agent first, links the first-build walkthrough and names vibehard-agent doctor. Installer prerequisite checks (part 2) are included.
• Honest install info. vibehard_install_info reports the absolute path of the installed binary, matching what the installer registers.
• Verified. 2.0.3 passed our official acceptance run (one run, no retries, frozen spec): the job completed, 0 of 44 gates blocked (12 passed; 32 did not apply to that command-line project), and all three output fixtures matched byte for byte. A separate reviewer re-checked the evidence and confirmed it. In that run the plan approvals came from the test harness, not a person, and a test agent drove the build; the run verifies the factory code; it does not certify the downloadable build, which is built and signed separately.

Upgrading from 2.0.2, 2.0.1, 2.0.0 or 1.7.1: automatic within 30 minutes, or run vibehard-agent update. Intel Macs: stay on 2.0.0 for now. 2.0.3 has no Intel Mac build.

2.0.2 — October 16, 2026

• Planning asks before it builds. Disputed high-severity planning findings now wait for a person’s ruling instead of being decided silently.
• Repairs follow the whole chain. The repair loop handles blocked inputs and command-line contract findings the way the core loop does, so fewer builds stop on a finding the factory can fix itself.
• More work at once. The daemon runs four build runners by default, and a build waiting on a person no longer holds a runner.
• Rust builds get through the supply-chain gate. Rust projects the factory creates now declare a licence, so the gate no longer stops them on their own crate. The vendored crate registry was also fixed.
• Proprietary by default. Apps the factory builds are marked all rights reserved to the client unless the client asks for an open-source licence: LicenseRef-Proprietary with publish = false for Cargo, UNLICENSED with private: true for npm, and a LICENSE file. Nothing is open-sourced on your behalf.
• Redesign epochs. A redesign request now starts a clean epoch of the plan.
• Safer tests. The factory’s own tests no longer touch your real ~/.vibehard or service manager.
• Help text. vibehard-agent --help now says 44-gate, matching the documentation.
• Verified. 2.0.2 passed our official acceptance run (one run, no retries, frozen spec): the job completed, 0 of 44 gates blocked (12 passed; 32 did not apply to that command-line project), the build audit accepted it, and all three output fixtures matched byte for byte. A separate reviewer re-checked the evidence and confirmed it. In that run the plan approvals came from the test harness, not a person, and a test agent drove the build; the run verifies the factory code; it does not certify the downloadable build, which is built and signed separately.

Upgrading from 2.0.1, 2.0.0 or 1.7.1: automatic within 30 minutes, or run vibehard-agent update. Intel Macs: stay on 2.0.0 for now. 2.0.2 has no Intel Mac build. If automatic updates are on, the 2.0.0 updater on an Intel Mac picks the Apple Silicon package, so about every 6 hours it downloads the 2.0.2 Apple Silicon package, fails its pre-install check, and stays on 2.0.0. To stop these attempts, set "auto_update": "off" in ~/.vibehard-agent/config.json.

2.0.1 — October 16, 2026

• Gate failures show the whole story. When a gate or the command-line smoke check fails, the message now includes both standard output and standard error, so your agent can see the real cause instead of guessing.
• Dependency setup no longer drops dev tools. An inherited NODE_ENV=production is no longer passed to the tools the factory runs, and dependency preparation installs development dependencies explicitly. Before, test runners and type checkers could silently go missing.
• Snapshots stay clean. Installed packages and build output are excluded from snapshots in a way that fixes the snapshot error some projects hit during repair.
• Stricter command-line contract. Generated command-line tools must answer both --help and --version, and the factory can find a tool’s entry point from a command-line style start script.
• Scaffold fixes. The TypeScript scaffold writes a .gitignore and creates its output folder first.
• Verified. 2.0.1 passed our official acceptance run (one run, no retries, frozen spec): the job completed, 0 of 44 gates blocked (12 passed; 32 did not apply to that command-line project), the build audit accepted it, and all three output fixtures matched byte for byte. A separate reviewer re-checked the evidence and confirmed it. In that run the plan approvals came from the test harness, not a person, and a test agent drove the build; the run verifies the factory code; it does not certify the downloadable build, which is built and signed separately.

Upgrading from 1.7.1 or 2.0.0: automatic within 30 minutes, or run vibehard-agent update.

Intel Macs: stay on 2.0.0 for now. 2.0.1 has no Intel Mac build. If automatic updates are on, the 2.0.0 updater on an Intel Mac picks the Apple Silicon package, so about every 6 hours it downloads the 2.0.1 Apple Silicon package, fails its pre-install check, and stays on 2.0.0. To stop these attempts, set "auto_update": "off" in ~/.vibehard-agent/config.json.

2.0.0 — October 14, 2026

• Software factory and the groundwork for agentic workflows (v2.0.0). Downloads for macOS (Apple Silicon) and Linux (x86_64 and ARM64).

Upgrading from 1.7.1+: automatic background update or run vibehard-agent update.

1.7.2 — October 10, 2026

• Go and Elixir are now supported build languages. Both passed the full gate chain on real projects — a Go service and an Elixir OTP application, end to end — and the language router offers them from this release. They join TypeScript, Rust, and Python.
• Jobs now survive a daemon restart. A job suspended when the daemon stopped could be marked as reviewed without its review findings ever being recorded, and then fail when it resumed. Review findings are now recorded before a job's state advances, and jobs left suspended by the old behavior re-enter and heal under 1.7.2 (a job that already failed still needs one rerun).
• Rollback targets are validated canonically. The update path canonicalizes paths on both sides of its containment check, closing an escape where a rollback target spelled through a symlinked directory could land outside the install directory.
• The build sandbox is isolated by construction. Sandboxed code previously ran with the whole host filesystem mounted read-only behind two masks — effectively the same reach as the process that launched it. On Linux, the sandbox now starts from an empty root with an explicit allow-list of what a build may see. (On macOS the sandbox blocks network access and limits writes, but does not yet isolate reads.)
• Security scanning covers compiled artifacts in full. The secrets and static-analysis gates now read large compiled artifacts (including Elixir escripts) end to end, on the host and in the gate container, instead of skipping the largest file in the project. Dependency-vulnerability scanning also provisions its scanner from a completely cold start — no manual container setup.

Upgrading from 1.7.1: nothing to do — 1.7.1 checks for updates every 30 minutes and applies this release automatically. To move now, run vibehard-agent update.

Upgrading from 1.7.0: run vibehard-agent update once (manual update works in 1.7.0; its automatic engine is the defect fixed in 1.7.1). After that, updates are automatic.

Upgrading from 1.6.0: do not use the one-line installer or 1.6.0's built-in update command — the installer hands the upgrade to 1.6.0's own update command, which rolls itself back. Follow the one-time manual swap instead: Upgrading from v1.6.0. From 1.7.1 onward, updates are automatic.

1.7.1 — October 9, 2026

• Automatic updates now work end to end. The background update check introduced in 1.7.0 could not reach its update engine in the shipped binary; 1.7.1 fixes that. A 1.7.1 install checks every 30 minutes, verifies the release signature, and applies updates on its own — no manual steps.
• Fixed a race in supervised rollback (update --rollback) and a containment check in rollback path validation.
• macOS: the daemon start-identity check now works on Mac (it previously relied on a Linux-only mechanism and was silently inert).
• The packaged binary is now smoke-tested as a compiled artifact before release, covering the class of defect behind the 1.7.0 update issue.

Upgrading from 1.6.0: do not use the one-line installer or 1.6.0's built-in update command — the installer hands the upgrade to 1.6.0's own update command, which rolls itself back. Follow the one-time manual swap instead: Upgrading from v1.6.0. From 1.7.1 onward, updates are automatic.

Upgrading from 1.7.0: run vibehard-agent update once (manual update works in 1.7.0; its automatic engine is the defect fixed in this release). After that, updates are automatic.

1.7.0 — October 8, 2026

• Automatic-update machinery introduced: a timer checks for new releases every 30 minutes. (In this build the timer installs and reports healthy, but its update checks do not complete — fixed in 1.7.1. Manual vibehard-agent update works.)
• Fixed the download packaging: the embedded database files are now included in the shipped binary, so a fresh install boots cleanly.
• Socket diagnosability improvements for the daemon.

Upgrading from 1.6.0: use the manual swap procedure in the 1.6.0 → 1.7.0 upgrade note (do not use 1.6.0's built-in update on Mac — its health check races the restart and rolls back), then run vibehard-agent update to continue to 1.7.1.