M
mikamikasuki/forest
FOREST is a research agent for long-horizon science, where evidence gets lost, errors compound, and goals…
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 354 ★ · mikamikasuki/forest · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-21 · last seen 2026-11-14 · seen 28× · listed by 2 sources
- Score
- score 204 · 354 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mikamikasuki/forest;first catalogued 2026-10-21;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# FOREST
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Give it a research question. Turn it into ideas, real experiments, evidence, and a complete paper.
FOREST is an end-to-end research agent framework for carrying a scientific project from an early question to a finished manuscript.
It can explore and compare research directions, search the literature, turn promising ideas into testable hypotheses, design experiments, run real code on your compute, analyze the results, and decide what to try next. As the project develops, FOREST can revise its plan, abandon weak directions, branch into alternatives, and build the figures, tables, and manuscript around the evidence that survives.
Instead of keeping the research process inside a long chat history, FOREST represents it as an editable research graph. Ideas, hypotheses, experiments, results, decisions, and paper sections remain connected. You can inspect the graph, change a plan, replace a hypothesis, branch from an earlier point, or redirect the research without starting over.
Idea discovery → literature review → hypothesis formation → experiment design → real execution → result analysis → research-path revision → baselines & ablations → figures & tables → full-paper generation
## What FOREST does
Finds research directions.
Start with a broad question or an unfinished idea. FOREST explores possible directions, compares them, checks the surrounding literature, and turns the strongest candidates into concrete research paths.
Turns ideas into experiments.
Hypotheses are converted into executable plans with baselines, controls, metrics, ablations, and explicit conditions for success or failure.
Runs real experiments.
FOREST writes and executes research code, launches training and evaluation jobs, collects logs and metrics, and keeps experimental artifacts attached to the research path that produced them.
Analyzes the evidence and changes course.
Results are not treated as the end of a task. FOREST interprets them, compares competing explanations, identifies what failed, and decides whether to extend, revise, or drop a direction.
Keeps the research path editable.
Researchers can intervene at any point: edit a node, change an experiment, revisit an earlier assumption, or branch the graph to investigate an alternative approach without losing the existing work.
Continues across execution rounds.
Agents save durable checkpoints at bounded work-round boundaries and automatically continue the same research run. Cumulative turns and planning cycles do not determine scientific lifetime. Recovery uses the retained goal, graph, evidence and action receipts; all rounds and branches share resource accounting. Actual spending, compute limits, permissions and unresolved blockers still govern execution. See research execution and recovery.
Builds scientific figures and tables.
Experimental results can be turned into publication-ready visualizations and tables while remaining tied to their underlying runs and observations.
Writes the paper.
FOREST carries the surviving evidence into a full manuscript, including related work, methods, experiments, results, figures, tables, and discussion. Metrics, figures, and scientific claims remain traceable to the evidence used to produce them.
FOREST is an end-to-end research agent framework for carrying a scientific project from an early question to a finished manuscript.
It can explore and compare research directions, search the literature, turn promising ideas into testable hypotheses, design experiments, run real code on your compute, analyze the results, and decide what to try next. As the project develops, FOREST can revise its plan, abandon weak directions, branch into alternatives, and build the figures, tables, and manuscript around the evidence that survives.
Instead of keeping the research process inside a long chat history, FOREST represents it as an editable research graph. Ideas, hypotheses, experiments, results, decisions, and paper sections remain connected. You can inspect the graph, change a plan, replace a hypothesis, branch from an earlier point, or redirect the research without starting over.
Idea discovery → literature review → hypothesis formation → experiment design → real execution → result analysis → research-path revision → baselines & ablations → figures & tables → full-paper generation
## What FOREST does
Finds research directions.
Start with a broad question or an unfinished idea. FOREST explores possible directions, compares them, checks the surrounding literature, and turns the strongest candidates into concrete research paths.
Turns ideas into experiments.
Hypotheses are converted into executable plans with baselines, controls, metrics, ablations, and explicit conditions for success or failure.
Runs real experiments.
FOREST writes and executes research code, launches training and evaluation jobs, collects logs and metrics, and keeps experimental artifacts attached to the research path that produced them.
Analyzes the evidence and changes course.
Results are not treated as the end of a task. FOREST interprets them, compares competing explanations, identifies what failed, and decides whether to extend, revise, or drop a direction.
Keeps the research path editable.
Researchers can intervene at any point: edit a node, change an experiment, revisit an earlier assumption, or branch the graph to investigate an alternative approach without losing the existing work.
Continues across execution rounds.
Agents save durable checkpoints at bounded work-round boundaries and automatically continue the same research run. Cumulative turns and planning cycles do not determine scientific lifetime. Recovery uses the retained goal, graph, evidence and action receipts; all rounds and branches share resource accounting. Actual spending, compute limits, permissions and unresolved blockers still govern execution. See research execution and recovery.
Builds scientific figures and tables.
Experimental results can be turned into publication-ready visualizations and tables while remaining tied to their underlying runs and observations.
Writes the paper.
FOREST carries the surviving evidence into a full manuscript, including related work, methods, experiments, results, figures, tables, and discussion. Metrics, figures, and scientific claims remain traceable to the evidence used to produce them.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mikamikasuki-forest/)
- Source
- github · https://github.com/mikamikasuki/forest
- Browse by field
- Open source
- Traction
- 354 ★
- Listed by
- 2 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.