Who it is forA research lead who runs several factor searches and needs to share results and reuse strong features across projects.
The problemFactor ideas and their results get lost across runs, which makes it hard to reuse what worked or explain past decisions.
The outcomeA searchable factor library and an exported research report that together document the features, fitted-model settings, review decisions, and development results.
What you need first
- Python 3.11 to 3.13 on macOS, Linux, or Windows through WSL2
- The uv package manager
- A daily OHLCV CSV with columns date, symbol, open, high, low, close, volume, covering 3 to 100 assets and at least 468 common trading days for default research settings
- An authenticated Codex CLI, or an API key and model ID for a DeepSeek, Gemini, Ollama, or custom compatible endpoint
Steps
- Run
uv sync --lockedand thenuv run alphaos servein the repository folder. - Complete one or more research runs from the workbench on an imported dataset.
- Open the factor library and search for features by name or by the research run that produced them.
- Save the features you want to keep so they stay available for later runs.
- Export the complete research report for the run and store it with the dataset and model settings used.
Prompt for your agent
In the AlphaResearchOS workbench, search the factor library for features from <research-run-name> and export the full research report for that run. Return a summary of the kept features with their development scores. Verify that the exported report includes the fitted-model settings and review decisions.
Caveat. The README says the library is searchable and exportable but does not describe its file format or how features move between separate installations.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, 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