Machine learning is where Primus got started. Describe something you’re curious about in one sentence, and Primus scopes the question, reads the literature, runs experiments on GPUs, and writes the paper.

Your prompt is a direction, not a spec. You don’t need a dataset lined up, a model picked out, or a clear idea of which experiment to run. Vague is fine: Primus asks follow-up questions and sharpens the project with you before the work starts.
You don’t need to be an ML engineer either. If you are one, think of it as a team of interns: it does the literature reviews, sets up the experiments and babysits the clusters.
Turns your idea into a well-posed question, and checks it with you.
Studies what’s already known, and pins the papers that matter to your project.
Designs them, runs them on GPUs, and iterates on what it learns.
Methods, results, code and citations, including when the hunch doesn’t hold up.
Each of these shapes has produced a finished project. The one habit worth having: aim narrow, not for the moon. Name a specific weakness and improve it without breaking everything else.
“Does the RL clipping mechanism control how diverse the generated outputs are?”
“A vendor says their model wins on this metric. Does the win survive a better metric?”
“Does post-training move a model’s representations toward or away from how brains process language?”
“Beat directed evolution at proposing high-fitness protein variants at the same query budget.”
“There’s no trusted automatic score for 3D-mesh quality, so build one and show it tracks human judgment.”
“Use preference optimization to fix the word-skip and repeat failures TTS models are known for.”
“Replatform this model onto architecture X and verify it holds up across the key benchmarks.”
“Find the best quantization of model X, judged on X and Y, without losing accuracy on Z.”
“Maybe injecting a self-reflection token reduces hallucination, so let’s design something to test it.”
Experiments run on GPUs Primus provisions for you. By default it runs in Full Self-Driving, making its own routine sign-offs while you do something else, and you can chat with it at any point to steer: “focus on the smaller model first,” “stop tuning and write it up.” It emails you when it needs you, which is in three situations:
Something it can’t get past on its own.
You approve a compute cap with the research plan. A run that would go past it stops and asks.
When it wants to change what the project is about.
A finished paperMethods, results and citations.
A model cardWhat was trained, on what, and how it behaves.
A reproducibility packageRaw logs, code and data: enough to re-run the work and check every claim.
Models and artifactsCheckpoints, datasets and code, with a record of how each was made.
Negative results, tooIf the hunch doesn’t hold up, the paper says so and shows why.
Sign in, write your prompt, and start the project. Primus works over hours or days and keeps you posted as it goes.