State that survives the next turn
A persistent IPython kernel keeps variables, imports, functions, and working-directory state available across ordinary calls and context compaction.
Explore the runtimeIndependent guide to Prime Intellect's open-source agent
Learn what makes Prime Agent different, complete a safe first run, and inspect the evidence behind its persistent Python runtime, recursive subagents, and long-running sessions.
Unofficial and independent · reviewed against v0.7.1 · no endorsement implied

Why it is different
A persistent IPython kernel keeps variables, imports, functions, and working-directory state available across ordinary calls and context compaction.
Explore the runtimeRecursive subagents receive their own context, history, and kernel, then report results through scoped messages or durable files.
Understand subagentsDaemon-backed workers, append-only session trees, and recovery artifacts support longer tasks without pretending that failures cannot happen.
See daemon behaviorSee the system
Prime Agent's agent view distinguishes running, idle, and inactive sessions and shows which children are still making progress. The parent remains responsible for reconciling their output.
How agents coordinate →
How it works
The model, IPython kernel, skills, tools, recursive agents, and continual harness have different responsibilities. Keeping those boundaries visible makes the capabilities—and the risks—easier to evaluate.

Choose your path
The important warning
The persistent kernel, workers, skills, extensions, and model-generated commands run with the permissions of the local Prime Agent process. Use a disposable or externally restricted environment for untrusted code.
Read the full trust model →First-party announcement, documentation, release, or installer. Browse all sources.