Grok Factory
A standalone Grok Bot pack that routes software, equity research, and general-purpose work through a single Firstmate and delivers results as pull requests.
At a Glance
The repository is publicly accessible without payment. No license is specified; Grok Bot, Cursor cloud and other execution services have separate access requirements and costs. No free hosted factory service is established.
Engagement
Available On
Listed Nov 2026
About Grok Factory
Grok Factory is a standalone Grok Bot pack published on GitHub by jaredtrichard. It installs onto the shared Grok Bot computer and gives the user a single point of contact, called Firstmate, for software, research, and general-purpose tasks. Work comes back as pull requests that the user merges.
What It Is
Grok Factory combines a software factory and an equity-research workflow under one Firstmate. A software task, called a ship, becomes a pull request. Research tasks either scan for an investment idea or put a named company under coverage, and the results are written to an equity-research GitHub repo. Other work is filed as scout or ship under a reserved default project.
According to the README, bots never execute on the captain's computer. They run on the shared Grok Bot computer, where Cursor cloud handles software work and heavy research such as gathering and model building, while Grok bots synthesize and write.
How the research workflow works
A scanning bot runs quantitative screens and a thematic sweep on Cursor cloud, and Firstmate pitches only a winner, and only when it is strong. The user can also name a company by ticker to skip the pitch and begin coverage directly.
Each covered name gets its own researcher. If a discontinued name returns, the same researcher resumes it. Initiation produces a research file, a segment three-statement model, a valuation, and a thesis in one pull request, with no captain checkpoint between gates. Coverage then continues on an ongoing basis.
Software path and storage
The software side uses scout versus ship modes, per-project crewmates, adversarial review before any software pull request, and a local sqlite backlog. Software state lives in factory.db, while research routing lives in book.db. Both databases and reports are stored under a grok-factory data directory on the shared computer. Research and models are stored in the equity-research repo under per-name models and memory folders.
Setup path
Installation works by telling any Grok Bot to follow the GROK_FACTORY.md file in the repository. After that, the user talks only to Firstmate, for example to scan for an idea, take it under coverage, cover a named ticker, or fix a bug in a project.
Access and requirements
This is a third-party instruction pack for an existing Grok Bot environment, not a standalone application or public API. The repository does not specify a license or supported operating systems. Its investment-research workflow describes generated research artifacts, not independently verified investment outcomes.
Community Discussions
Be the first to start a conversation about Grok Factory
Share your experience with Grok Factory, ask questions, or help others learn from your insights.
Pricing
Public pack access
The repository is publicly accessible without payment. No license is specified; Grok Bot, Cursor cloud and other execution services have separate access requirements and costs. No free hosted factory service is established.
- Public Grok Bot instruction pack
Capabilities
Key Features
- Single Firstmate interface for software, research, and general-purpose work
- Quantitative screens and thematic sweep scanning with a single pitch
- Coverage of named companies by ticker
- One dedicated researcher per covered name
- Initiation PR with research file, three-statement model, valuation, and thesis
- Equity-research GitHub repo as durable store
- book.db and factory.db routing and backlog
- Adversarial review before software pull requests
- Per-project crewmates with scout and ship modes
- Default project for non-software, non-research work