Install the VibeHard Agent Edition v2.0.3.
curl -fsSL https://vibehard.ai/download/install-agent.sh | bashThe installer downloads the v2.0.3 binary, checks its SHA-256 checksum, installs to ~/.local/bin/vibehard-agent, and prints the MCP config entry. It registers it for you if you agree when asked, or when you pass --mcp-register.
{
"mcpServers": {
"vibehard-agent": {
"command": "/Users/you/.local/bin/vibehard-agent",
"args": ["mcp"]
}
}
}Use the absolute path the installer prints (for example /Users/you/.local/bin/vibehard-agent on a Mac or /home/you/.local/bin/vibehard-agent on Linux); MCP clients do not expand ~. The installer writes this same entry, named vibehard-agent, when you agree at the prompt or pass --mcp-register.
Temporary: until the installer handles prerequisites itself, run the block for your system. Agents: run uname -s first (Darwin = macOS, Linux = Linux; on Windows, check whether you are inside WSL) and use the matching block.
xcode-select -p >/dev/null 2>&1 || xcode-select --install; curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash && export NVM_DIR="$HOME/.nvm" && . "$NVM_DIR/nvm.sh" && nvm install 22 && curl -fsSL https://bun.sh/install | bash && curl -fsSL https://vibehard.ai/download/install-agent.sh | bash -s -- --mcp-register && npx -y rea-agents@6.1.0 setup --yes --all-detectedThen restart your desktop agent app and, if you use the command-line agent, run claude mcp list. If Apple’s developer-tools window appeared, let it finish before the first build. If the installer asks about REA, answer n (the last step installs the tested version). Intel Macs stay on 2.0.0 for now.
First, the admin step. Debian or Ubuntu:
sudo apt-get update && sudo apt-get install -y git curl unzipFedora:
sudo dnf install -y git curl unzipThen:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash && export NVM_DIR="$HOME/.nvm" && . "$NVM_DIR/nvm.sh" && nvm install 22 && curl -fsSL https://bun.sh/install | bash && curl -fsSL https://vibehard.ai/download/install-agent.sh | bash -s -- --mcp-register && npx -y rea-agents@6.1.0 setup --yes --all-detectedClaude Code is supported on Linux; Claude Desktop isn’t available on Linux.
Not supported natively. Use WSL: run wsl --install in PowerShell as Administrator, restart, open Ubuntu, follow the Linux steps above, and use Claude Code inside Ubuntu.
An AI agent can start the proven sample unaided. This sample is written in Go. The installer offers to install Go if it’s missing; or install it from go.dev/dl. Install first, then in an empty folder run this prompt (full guide: /first-build):
Use the VibeHard factory (the vibehard-agent MCP tools) to build a program in this folder. This is a quick first experiment, not something I will rely on or share with users. Open a session, then start a build with exactly this request:
word-frequency CLI: reads a plain text file, outputs the N most frequent words with their counts; JSON output; no network; no storage beyond stdout
Then drive the build: keep fetching work orders with vibehard_task_next, do the work each one asks for in this folder, and submit it with vibehard_task_submit, until the job is complete. Do every work order yourself, and follow every output-format instruction it gives. In review and audit outputs, spell each document name exactly as one of the work order's === name === headers, and never dismiss a high-severity finding (fix the document instead). In code: never write skipped or disabled tests, format with the language's standard formatter, make the program accept --help and --version (each prints to stdout and exits 0), and do not leave compiled binaries or build output in the project folder. Whenever VibeHard asks a question or asks for an approval (vibehard_review_next), show me the question, its options and the recommended answer, then stop and wait for my reply. Never answer for me. When the job is complete, tell me where the program is and how to run it.VibeHard will ask a few questions. Show each to the person you work for and wait for the reply; answer the sample questions as listed on /first-build. Do not answer on their behalf.