Fix: Group all research outputs into unique per-session folders to improve organization and prevent lost files
Problem
Currently, OpenManus saves output files (guides, code, data) in various locations inside the output/ directory. This causes:
- Research outputs from a single session to be scattered across multiple folders.
- Difficulty in tracking which files belong to which research task.
- Risk of overwriting or losing files.
- A cluttered output directory over time.
Solution
I implemented a fix that:
- Generates a unique output folder at the start of each research session, named with a timestamp and optional topic slug, e.g.:
- Prefixes all output filenames with this folder path before saving.
- Creates necessary subfolders (e.g.,
guides/, code/, data/) inside the session folder.
- Saves all related files from a single research task inside this dedicated folder.
Benefits
- Keeps outputs organized and traceable per research session.
- Prevents clutter in the
output/ directory.
- Avoids lost or overwritten files.
- Simplifies review, sharing, and cleanup of research outputs.
- Improves reproducibility by grouping all related files together.
Recommendation
Please consider integrating this approach into OpenManus by:
- Generating a unique session folder at the start of each research task.
- Saving all outputs inside that folder.
- Optionally, including metadata or summaries per session.
This will greatly improve output management and user experience.
Fix: Group all research outputs into unique per-session folders to improve organization and prevent lost files
Problem
Currently, OpenManus saves output files (guides, code, data) in various locations inside the
output/directory. This causes:Solution
I implemented a fix that:
guides/,code/,data/) inside the session folder.Benefits
output/directory.Recommendation
Please consider integrating this approach into OpenManus by:
This will greatly improve output management and user experience.