DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to try both recursion modes locally with no credentials with Harness2

Run the bundled demo to see parallel and sequential harness refinement before spending any API budget.

Who it is forA developer or researcher evaluating Harness² who wants to see how the two recursion modes behave before configuring any model access.

The problemSetting up model-backed benchmarks takes time and costs money, so it is hard to judge the framework before committing.

The outcomeA completed local demo run under runs/demo that shows both recursion modes using deterministic editors and real Python executions.

What you need first

  • Linux, Python 3.12, and uv
  • For the local demo: nothing else, since it needs no model credentials
  • For model-backed runs: Node.js 20+, the Google Cloud CLI, a Vertex AI project with model IDs, and API budget
  • For LAB: Pandoc and Poppler. For WorkBuddy-Bench: Docker

Steps

  1. Create the environment with uv venv --python 3.12 .venv
  2. Activate it with source .venv/bin/activate
  3. Install the package with uv pip install -e '.[render]'
  4. Run the demo with harness2-demo --output runs/demo --k 2
  5. Review the results saved under runs/demo and compare the two recursion modes

Prompt for your agent

In the google-research/harness2 repo on Linux with Python 3.12 and uv, create the environment, install with uv pip install -e '.[render]', and run harness2-demo --output runs/demo --k 2. Report the files written under runs/demo and summarize what each recursion mode produced. Verify that the run finished without model credentials being configured.

Caveat. The demo uses deterministic editors, so its output shows how the modes run, not how well they perform on real benchmarks.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page