What you can build.
Today VibeHard reliably builds small, single-purpose programs. Here is what the evidence supports, and what is not ready.
Reliable today
- Small command-line tools that read a file or arguments and print a result, with no server and no database. Proven in Go (a fresh-install end-to-end test on release 2.0.6, and 10 of 10 in our smoke test on the 2.0.6 candidate) and in TypeScript (official run, release 2.0.6).
- Small libraries with a command-line wrapper, as in the invoice sample (TypeScript, official run).
- Every build runs the same 44-gate verification chain (48 with a paid license), a build audit and a handoff report, and is snapshotted so you can roll back.
Supported but not yet proven end to end on 2.0.6: Python and Rust projects, and services that listen on a port or store data. They may work, and the factory has backends for them, but we have not shown a clean run, so we do not promise them.
Example prompts
Give your agent a prompt of this shape. The first two are samples we ran; the others are the same kind of program and have not been run individually. Name the language you want (Go is the proven one for a first build).
| Status | Prompt (the build request) | Notes |
|---|---|---|
| Proven sample (Go) | 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 | The /first-build sample. Completed from a fresh install of 2.0.6 in our end-to-end test, and 10 of 10 times in our smoke test on the 2.0.6 candidate. |
| Proven in the official run (TypeScript) | invoice-total CLI: reads a CSV of line items, outputs totals with tax; JSON output; no network; no storage beyond stdout | Passed the official acceptance run on 2.0.6 under the strictest setting with an approval policy pre-installed. Invoices count as financial data, so on a fresh install expect human-only questions and a plan approval that needs a signed policy: not a good first build. |
| Same shape, not run individually | csv-stats CLI: reads a CSV file and prints the count, sum, minimum, maximum and average of a named numeric column as JSON; no network; no storage beyond stdout | A small file-in, JSON-out tool, like the word-frequency sample. Ask for Go. |
| Same shape, not run individually | log-filter CLI: reads a log file and prints only the lines at or above a chosen level, with an option to count lines per level; no network; no storage beyond stdout | A small text-processing tool. Ask for Go. |
| Same shape, not run individually | unit-convert CLI: converts a number between metric and imperial length, weight and temperature units; prints JSON; no network; no storage | A small calculator-style tool. Ask for Go. |
| Same shape, not run individually | slugify CLI: turns titles into URL slugs, handles accents and repeated separators, includes tests; no network; no storage | A small text tool. Ask for Go. |
To use one, adapt the first-build prompt: replace the request line and keep the rest.
Coming soon
- Hosted workflows that run for you, with approvals on money, books, outbound and delete steps: not built yet.
- Larger applications (several modules, a data store, background jobs): not proven yet.
- Apps with a user interface: the design stage is not released, so we do not build interface-heavy apps yet.
- Hosted factory runs and hosted app connections: coming soon.
Evidence
Command-line tools. Go: the word-frequency sample completed from a fresh install of release 2.0.6 in our end-to-end test (checkpoints answered by a test agent), and 10 of 10 times in the earlier smoke test on the 2.0.6 candidate. TypeScript: the invoice-total sample passed the official acceptance run on 2.0.6. Not yet shown end to end on 2.0.6: Python, Rust, services and data stores. We list only what a run supports.