DEDUPEDRemote script. Repository code you clone may be executed by the worker under the worker account's permissions, so review the repository before running experiments from it.
Who it is forA researcher whose experiments depend on an existing public GitHub codebase and who needs a traceable source commit for each run.
The problemIt is unclear which commit of a research codebase produced a result, and failed runs are hard to diagnose.
The outcomeA repository input in the selected project with a run ID, its recorded source commit, and execution diagnostics.
What you need first
- Python 3.11 or newer
- Node.js 22 or newer for the Web workspace
- Git installed on the worker machine
- A model provider configured in Settings or through the API
- An explicit spending budget and execution limits set before unattended runs
- tectonic or pdflatex if you want PDF compilation
Steps
- Make sure Git is installed on the worker, and that OpenSSH is available if you use SSH.
- Clone the repository into the selected project with
.venv/bin/forest repo clone https://github.com/OWNER/REPOSITORY.git --wait. - Note the returned run ID and inspect its source commit with
.venv/bin/forest repo inspect RUN_ID. - Review execution diagnostics with
.venv/bin/forest run diagnostics RUN_ID.
Prompt for your agent
Using the FOREST CLI in <repo path>, clone the public repository <repository URL> into the selected project and wait for it to finish. Then run the inspect and diagnostics commands on the returned run ID and report the source commit. Verify that the commit reported by inspect matches the commit you expected from the repository.
Caveat. Private repositories need worker-side HTTPS or SSH credential profiles, and the README does not describe how those profiles are created, so check the repository authentication guide first.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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