Who it is forAn engineer or lab member working on a remote machine who wants to manage research projects from the command line or from an automated script.
The problemA Web browser is not available on the compute host, and the research state needs to be controlled from scripts.
The outcomeA running headless FOREST service with a project initialized from the CLI and a status report showing its current state.
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
- Install without Node.js or the Web build with
python3.11 scripts/install.py --headless. - Start the API and worker with
.venv/bin/forest serve --headless --data-dir ./varand keep that terminal running. - In a second terminal, create a project with
.venv/bin/forest init --name "My research" --goal "Your research question". - Check progress with
.venv/bin/forest statusand list commands with.venv/bin/forest --help.
Prompt for your agent
In the FOREST repository at <repo path>, run the headless install, start the service with a data directory of <data dir>, and initialize a project with the goal <research goal>. Report the output of the status command. Verify that the project name in the status output matches the name you passed to init.
Caveat. The CLI guide and the numerical experiment example are linked from the README, and the example runs without model calls, so use it to check the setup before adding a provider.
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