Building the GitHub for RL Environments: Prime Intellect's Will Brown & Johannes Hagemann

If data is the bottleneck, if having the real expertise is the bottleneck, would you rather have the smartest person in history work at your company or someone who's been there for 30 years? Sometimes you really want the person who's been there for 30 years. There's a lot of expertise that comes from really understanding a problem deeply and interact with it over a long time. And this is really what happens in training that is almost impossible to replicate in a short prompt. You really want the ability for institutional knowledge to compound over time, for best practices to compound over time. And this is how institutions and companies grow to be really powerful and successful is they stand on the shoulders of what they've done before rather than kind of resetting every day. And we want to have this be accessible to any company that wants to do this. And I think that's how we've thought about approaching it. Especially as software becomes easier for people to manipulate, as the barrier to entry for coding becomes easier, we see the same happening for AI research.

Will and Johannes work at Prime Intellect, which is one of the coolest neolabs in AI right now. Your mission is to make Frontier Lab training accessible to everyone, which I think is a very noble mission. You have really, really strong taste and just developer feel and just understanding how to you know that intuition for what developers care about and then what you all launched with the Reinforcement Learning environments hub was like really, really differentiated and people were very excited about and so I'm excited to chat about many topics with you all today. Post training Reinforcement Learning Agent harnesses your platform, the RL Hub and then big picture questions on what's coming next in post training in rl. Does that work?

Sounds great.

Absolutely.

Maybe to get started. You are one of the leading research labs enabling customers to post train their agents. Can can you tell me about what is that? What does that mean?

Yeah, for sure. Happy to take that one and give a bit of a higher level overview of what our platform does as well as our research at Prime Intellect. As you already mentioned at the beginning, we try to make Frontier infrastructure available to any startup enterprise and Neolab as well. And basically the infrastructure that is currently locked behind the walls of the big labs where nobody really has access to them. And yeah, we really start from the compute layer and the compute orchestration layer and go all the way up then to the entire full post training stack. So everything from the training frameworks that are needed to do large scale reinforcement learning to the environments with a bit of a more community approach with our environment hub to Other pieces that actually needed to do this, like sandboxes for secure code execution and evaluations as part of our environment hub as well. And yeah, to offer this as an end to end product in a sense.

And what's the intuition for why pursue that mission statement of making all that infrastructure available to everyone?

Yeah, there's a lot of reasons. I think one is, and I think something that we are very passionate about is just like open science as a way that humanity moves forward where a lot of the big scientific discoveries historically have been things that we talk about and as a world we can kind of build on top of, but kind of more practically speaking as well, there's a lot of value in model customization where we are like the winning applications are using AI for a specific thing, for some agent, for some workflow, where you also want to be able to deliver this at scale and with cost effective performance. And so really the way to kind of really optimize these systems end to end is to be able to have access to the model weights directly where you can then craft the model to be the best model for your problem, rather than some model off the shelf where the crafting happens just in a prompt. And so it's, it's really just allowing a deeper layer of customization than what you can do at the prompt level.

And then is your vision for the future then that every company will be pre training their own models, post training their own models, fine tuning their. What do you think the future holds?

We definitely think that every company will be an AI company and we think most AI companies will want to have an AI research lab. And research can look like many different things. It can look like pre training, especially if you're in a domain where you maybe don't just want text in, text out. If you want something more bespoke, in a lot of cases it will be like post training, agentic or otherwise kind of focused models for specific tasks and workflows. And I think that's getting to the point where it's productionizable and cost effective, where you can actually make this very practical for people to do at scale, for kind of the right shape problems that people want to solve.

Awesome. And then can you say at high level what your platform does?

Yeah. So we have a full stack research platform called Lab. And Lab is about giving everybody the ability to do the things that a frontier research lab can do internally. But for anyone in the world who wants to do this kind of research and a big focus of Lab is the notion of an environment and So I think a lot of people have heard the term environment in the context of reinforcement learning, and that's a big focus of it for us, which is that an RL environment is encapsulating the things you need to do to do reinforcement learning, where you can have a model improve via trial and error. But it's also more general beyond just reinforcement learning. And I think if you haven't heard of an environment before, it's essentially the same thing as the evals that get reported when people talk about new model releases. So Swebench and Amy and terminalbench, these are all examples of environments where there's a data set of tasks, there's a harness for the model to be in, and there's something called a rubric or reward function which is responsible for grading the quality of the outputs. And so the same thing you'd use as an eval offline as your kind of your test set, you can use this in reinforcement learning as your train set. And this is a way to improve model performance interactively. And so our platform is really enabling people to use environments in their workflows for post training, for evaluation, for synthetic data, for reinforcement learning. And it's also very much focused as a community platform in the same way as things like GitHub are, where this stuff is new, it's complicated and we want people to have lots of building blocks they can draw from and lots of examples and for it to be collaborative and for people to have reasons to kind of show off ways of using models or different tools in workflows as environments, to allow other people to post train models in those environments, to kind of have this way of sharing the ability to improve performance across different tasks.

I think the general idea is to give more companies the actual ability and advantage that currently only the big labs have in a sense of this product model optimization loop where they can optimize their models for their specific product, in a sense. And we see it as a thing where, yeah, that's the kind of reason why a ChatGPT was created by OpenAI or a Claude code was created by Anthropic. They actually have the capabilities to optimize models for their specific scaffolds, in a sense, and have their models work way better in their products. And the more popular those kind of products also become, in a sense like a cloud code becoming extremely popular right now. The big labs have naturally less an incentive to actually make it work better for other coding startups, in a sense. Right. And the idea there is to give them the tools to have their own model product optimization loop. And I think there are early adopters on that front. I think one great example always in this case that I always give is for example, that realized that in my opinion quite early on they built their own composer one model where they did large scale post training in a sense and really optimized a model where the environment was actually cursor itself. So yeah, give them all the tools that you have in cursor in a sense as well and optimize a model inside of cursor. And we believe there's a lot of more startups that will go this direction to on the one side, optimize their current products in a sense, but also, yeah, build completely new products that are really not possible right now without having this product model optimization loop.

Awesome. And can we say a word on. You said something interesting. You said environments are just evals. Can we dissect that statement? In my head, an environment is state. It's a description of world state through which you observe what actions you take, you observe how world state changes and therefore you update your world model. That to me is distinct from an eval, which is like you should have gotten this answer on this set of questions. And so can you help me merge those two realities?

Sure, yeah. So I think there's a version of eval that's kind of where we were maybe a year or two ago, where a lot of people were like question and answer and it's like this big bank of questions. And then maybe there's other notions of environment that people think about when they talk about like an old school RL with like Atari that is much more about like this kind of long running state interaction loop. And I think where we are now is it's both in the same thing where especially the environments that you want to do large scale training on, they do have this complex state. They maybe are simulating a web app. It's a full fledged kind of coding platform where you have an agent doing these things. But in the original RL games there's always a reward, there's a goal. And so the notion of there being a goal of this problem where it's not just running through some system and a human's going to kind of vibe check it, there actually is something that can measure progress and performance. And that's kind of what I mean by it's uneval in that there is a system that it starts at some state, it interacts with the system, the environment, the harness, the agent, whatever you want to call it, but there is some goal and there's a way to measure whether it's doing well or not.

Okay, got it. And then is there a difference between you mentioned kind of cursor as a great example of somebody doing really great frontier work and reinforcement learning? Is there a good way to think about when should you be kind of constructing RL environments versus when should your actual application and your application states be the environment, so to speak?

Yeah, I think there's definitely reasons where you want both, especially like, let's say you're training a model to be a really good rust coding model here. You might want it to be good for lots of different applications where you'd have different environments that are focused on some like domain task. Maybe you're a company that wants a model that's going to be really good at calling your tools or using your specific domain language that then you can provide as a service to people who are building around that. Then there's also ones where the product very much is like a user interface for an end user, where the user's interacting with an agent, in which case it might make the most sense for the product to very directly become the environment where I think the companies who might want to be doing this are the same who care about whether they're using Claude or GPT5 or Gemini or the ability to choose models and have internal systems to evaluate whether a certain system prompt is good or whether changing out a model endpoint is good, or whether using the mini version of a model is a better cost performance. Trade off. The infrastructure to do that that a lot of people have already been building at these kind of advanced agent companies is the same infrastructure you use to do reinforcement learning. And so I think that's kind of this kind of convenient world we ended up in where the training paradigm that makes the most sense for improving model capabilities is the same sort of thing that a lot of people have been building up the muscle for just without doing the training piece. And so that's kind of where we see RL being a very useful tool for people to then have this as an option in their toolkit for system optimization.

Got it. Okay. I want to talk about agent harnesses as they apply rl. I feel like harnesses is like the theme of the moment, especially with you mentioned CLAUDE code getting so much love. I think one of the things that they do exceptional engineering around is the harness. Harness and RL are those things orthogonal, mutually exclusive? Like, how do they relate?

They definitely relate. I think of a harness as like A piece of the environment. And so for any eval or environment task, there's some input, a bunch of stuff is going to happen. Then there's some output state which is then going to be graded. And so this whole intermediate piece, whether it's interacting with some simulator or interacting with another agent or physical world simulation, this is the environment. And the harness is very much a piece of that where it couples how the model interacts with any other pieces of the system. And I think depending on the application area, I think for coding agents we have a pretty clear definition of what's the. You could say the harness is the CLI coding agent and the terminal is the environment. But this isn't necessarily going to be universal across all different types of agents. In some cases it's a system prompt and some tools is the harness. In some cases it's something that is going to be spawning subagents. And those subagents also have their own harnesses. And so there's a lot of complexity. And I think the way we've thought about it is harnesses are going to keep evolving. There's going to be this Cambrian explosion of ways people want to use models. And we want to take a pretty general approach in defining what you could do with a harness. And so what we are really thinking about and why we use the term environment as the abstraction is like agent is too narrow, harness is kind of too narrow. And you can do all of these things within an environment. But the environment as an abstraction on the whole allows this. Any sort of system model interaction is in scope.

And then do you think, then do you think all companies should be post training their models with environments? Are there specific kind of, you know, where the bullseye, like you absolutely need to be using environments versus like you could be post training with a different method versus you should just be prompting your thing.

I mean, I think environments are tools you can use to do all of these things. And so I think that's when I talk about kind of environments beyond rl. I think part of the reason why it's a useful abstraction is because it doesn't tie you to rl. Let's say I want to have a small model and I want it to be distilled from a big model. The way you can do this is you take the big model, you plug it in your environment, you let it run a bunch of times. Now you have all this data that comes from the same interaction protocol. You can use the same grader at the end to filter for the best examples. And then Do SFT fine tuning on that. You could do prompt optimization with an environment. You could a b test different models with an environment just as you would with an eval. And so we really. I think the idea is that every AI company should be optimizing their AI systems. I think that's a less, like, controversial take.

Okay. And maybe there's another way to frame it. Like the eval is almost how your agent performs in the set of environments that you expect your customers to face.

Yeah, I think it's. It depends on what you want to call in traditional machine learning terms. You don't want to overfit to the test set. And so in some ways, we kind of are already accepting that we're going to be using the test set or the eval to measure, to have that kind of filter back into the model. And so I think it's a little tricky to distinguish even like, what is the eval, what is the environment? We kind of think of them as one and the same, and we use the environment term very generically. Where an eval is a type of environment that's used for measuring performance but not training on. And that's kind of how we see a lot of people thinking about when they're doing evals. What they really mean they're doing is they have some way of measuring current performance and they're iterating on it. And in some ways, RL is this iteration applied at scale, where you're automatizing the process of changing the model a little bit, changing the prompt a little bit, and having this be the way that you can kind of hill climb on some goal.

Maybe another question. Do you see reinforcement learning as synonymous functionally with post training? Meaning if you're post training model, are you doing reinforcement learning or are you doing other things?

There's definitely a lot of things. I think reinforcement learning is the big thing now where it's like in many cases, practically speaking, if you're doing a large scale model, RL will be where you spend the most of your time and focus and compute. But it's not the only thing you want to do. There's a lot of things involved in the pull process of going from some initial model to the system you want to deploy. This can be prompt tuning, this can be sft, this can be online distillation. There's a number of algorithms that all kind of are under this umbrella where RL is like the big one in the middle, but there's a lot of stuff around it. And really, I think exposing this toolkit to people and letting them have all these knobs they can play with is the way to unlock the best.

And are you finding that it's the really smart AI researchers that actually know how to make this stuff happen in practice? Is it towards your goal of democratizing AI development for all? Does your average Fortune 500 know how to use the platform and get value out of it?

I think most companies have people who can. I think any Fortune 500 company will likely have a team of AI engineers who are capable at following the latest tools, who are good at using cloud code, who have a lot of opinions about models and prompting and those people certainly can do this. That's kind of the audience where we see as the target customer for this.

Especially if you give them the right tools to actually do it. Maybe some of those large companies don't really have anybody in there who can debug your GPU cluster in a sense to actually kick off such a run or other components that are needed in there to actually just make it easier in a sense to do large scale magentic reinforcement learning with tool use, with code execution and pieces like this to just abstract away the entire infrastructure for them.

Yeah, got it. Awesome. Actually, on that note, do you guys have any favorite customer stories that you want to share?

Yeah, one of our favorite customers that I would like to point out in a sense is RCAI A neolab working on Frontier open models have been working with us on the entire stack in a sense. Right. We've been talking a lot about reinforcement learning. Right. But yeah, we've been also doing large scale pre training in the past. That's basically where our history is coming from in a sense as well. Right. So yeah, I've been training with them some of the largest mixture of expert models and actually able to open source them as well and as well on the post training side with them as well. Maybe. Will, do you want to share some more?

Sure, yeah. So they're a very close collaborator of ours that we've. I think we've all been friends for a long time but also like we've been. I think they've been way where we've had to. They've had a lot of things that they want infra for and it's. That's been a way that we've been able to kind of force us to build out a lot of the pieces both from compute orchestration to post training to pre training to inference around kind of just making the everything that is needed to kind of be a frontier lab and I think they're very aligned with us in the kind of the openness mission and I think. But I think they're kind of focused, they are more targeted at like enterprises and the end user where they are kind of going to work more directly with customers in terms of like end to end kind of delivery of a certain artifact. Where I think where we come in is we are, we are really focused on the developer experience at the Infra layer and the ways that we can make put these tools into more people's hands where the process of going from idea to deployable model can become as seamless and kind of quick as possible and efficient as possible.

Awesome. And then any other favorite customer stories maybe on people that are using the environments product specifically?

Yeah, so we are definitely really focused on like the research community and like some of this is like a lot of grad students use it. A lot of like students and people who are getting early in like their career learning how to do this stuff or using it. But also a lot of labs who are focused on a very specific domain where let's say you're starting a medical AI lab. We work closely with a number of groups in the medical AI space where they want to create more both benchmarks to understand how good are models at medical abilities both in terms of diagnosis or patient interactions or question answer about medical literature or agentic search over certain medical tasks. And so like sofont openmed being two that we work closely with where the focus there is to they really care about like earning trust from the medical professionals. And so for them they really want to focus on the domain and not as much on kind of the generic medical the LLM infra that is kind of like a headache for a lot of people. And so for them like being able to kind of have this platform for creating evaluations, for showing them off, for being able to use them to then improve model capabilities that could then be deployed locally in a hospital or deployed locally for some end user where the ability to have this customization and have this kind of end to end trust and understanding of the data provenance for tasks at hand or the ability to kind of customize models very directly is very key.

Do you have any customers that are using you for more of like what you call the old school kind of Atari style learning from your environment type?

Do you mean like. So when I think of Atari I think of like non LLMs. And so we definitely are focused on LLMs and foundation models that look like LLMs. There's definitely a lot of Researchers who use our platform for these things that are more like. There's some examples we have on the platform that are much more like games. So I mean kind of one fun one that I use as like a demo a lot is the game Wordle from the New York Times where this kind of ended up just being the like a great hello world environment for people. Because it's. The infra is really simple, but it's very expressive where you can kind of get a feel for it and you get this aha moment of seeing a model learn to think about the game as you give it rewards for doing better. And you can have. You can do it with a really tiny model too. Like it's. It's in this sweet spot of difficulty where you can do these runs on a couple GPUs in an hour and see a model actually learn how to get better at the game.

I would say the more toyish game examples, usually the ones that people are going for for actually learning how to build those reinforcement learning environments. And yeah, that's also what people are heavily using the environment hub for in a sense just because we have all this infrastructure built around it to be able to actually test your environments. And yeah, that's usually how they start out and then go to actually building more complex environments later on. Another group I would love to give a shout out to in a sense that have been building some of the more complex environments on the hub. Are people. Part of our reinforcement learning residency where we have a group, we initially started out with eight to 10 people. I think 14 to 16 are now in the group. You have people grad students as well as people working full time that yeah, part time building reinforcement learning environments as well as doing novel research on top of the environment hub. And those folks have built amazing environments in all kinds of verticals in a sense. Everything from verifiable software engineering in lean to medical physics environment to some cybersecurity environments. And then yeah, also we give them the tools obviously now to actually do the training and those as well.

Yeah. Awesome. Can you help demystify for me? I've heard that some of the foundation model companies are spending millions of dollars each on some of these environments.

Yeah.

And so like you mentioned cybersecurity at the end, like what goes into constructing a cybersecurity environment.

Yeah, so there's. There's someone in our residency program who actually does a lot of this stuff. And so like there actually is a lot of like tooling in the cybersecurity world around like These capture the flag games where there's, there's some system that has some hidden bug in it. And this is like a challenge that originally these are built for programmers, or programmers will have like a little hackathon where they try to go find the bug in some system. But you can adopt these challenges to LLMs as well, where it then is a full software environment where it's a terminal, where the agent lives in the terminal and has access to tools for doing bash commands. Maybe it's using CLAUDE code or some other wrapper for an agent harness, but it's in a terminal full of files and can interact with these files. And then at some point it marks that it's finished with the rollout. And then you can grade the state of the environment using other pieces of software, other code that executes. But we do like, we actually have a lot of people we work with who are in the data and environment space where we've found that there's a lot of interest in using reinforcement learning as a way to evaluate data quality, where the ability to measure what happens when you train a model on a set of tasks, set of rubrics, set of environments, allows you to understand bugs in the environments. Because there are issues that come up in reinforcement learning where maybe if your environment has a backdoor, a model can exploit this and kind of game the system. And so I think there's a lot of interest in people using RL to like in the pipeline from like idea to environment that ends up in some frontier labs like foundational training run for the next GPT or CLAUDE model, there's a lot of vetting that goes into this. And doing these like smaller or like medium scale runs in like, let's say one environment allows you to really poke and see where the problems might be.

Okay, super interesting. And if we take the cybersecurity environment example one step further, by the way, I have no particular affection for cybersecurity, but it's something that like I love having a specific example in my head. I could see how you could construct a toy example, right? These capture fly examples, I would imagine they're toy examples. I would imagine they look nothing like the actual kind of corporate network environment of a real company with all of its cybersecurity products. And so I guess how do you construct an actual, you know, does, does what people can construct, does it actually scale up towards imitating and reflecting the complexities of the real world? Almost like the, you know, the robotics real gap?

Yeah.

Is there a sims a real gap in crafting these environments and is solution just to like, train on, like, real kind of corporate security environments.

Yeah. So I would say there's less of a barrier in terms of the actual complexity. Like the. In principle, these can be as complex as you want. It's anything that could be on a computer. So just think of anything that's on a computer or network of computers as potentially an environment. What really kind of becomes the bottleneck in many ways is like, cost of the simulator, where I think there's a lot of focus on identifying clever ways to kind of mock the right piece of the system. Where let's say you have an agent that you want to like, let's say the Internet. Like, let's say you want to have an agent that like, does a lot of like, web search. In some cases you actually want to do the real web search. In some cases, you want to find ways where you can design tasks where you actually don't need the full thing. It's like this kind of, I don't know, I think of like the map games where there's this world you want to explore where there might be this whole map. And like, some of it's like, dark, but as you walk around, like the light shines, then you now see this part of it. And so if you know which pieces of this map might actually be explored on a given task, then then this kind of allows you to decide which pieces are important or not. And so, like one example, like, there's some benchmark. There's a benchmark called TAO2 bench that is very popular in the eval world where it's about customer service agents involving a database. And so the database is something where, like, in a real system, you might need the full database, but if you know that the agent is only going to ask certain types of questions for a task, you don't need a full database with millions of records or thousands or billions of, like, different examples. You can have kind of a mock database that is a cheaper to run, maybe in memory piece of software that only has the things that are expected by the agent or expected in the scope for a given task. And so identifying like, the pieces of the system that. Where the complexity is kind of overkill is part of this task design process to enable efficiency.

And does your platform help with that? Like, that almost seems like, you know, if creating environments is the bottleneck to training these systems, then, like, being able to efficiently create these environments where, you know, you're lighting up the part of the map that has to be lit up is like a core kind of almost platform competency. Do you guys assist with that?

Yeah, I mean, it's definitely a way that we think about the design of everything and we kind of go down a lot of these different like rabbit holes as we have to focus on different tasks when working with different people. And so like coding agents maybe is one example where like there's a lot of complexity that comes up when working with like sandboxes and terminal states and ensuring that you have like good snapshotting and all of these things and protocols to interact with different agent harnesses. And so we've built a lot around that. But it's also the sort of thing that we kind of know that the space of complexity is going to grow arbitrarily over time as people start getting more deep into these different domains. And I think we've tried to design everything in a way where we, we keep a lot of doors open where like we have room to build features that kind of like there's, there's base layers of like generic environments. Then you can go, I want a coding agent environment, I want a coding agent environment with a sandbox that's global across the run, or I want one per rollout, or there's lots of these different branches you can go down. And so we kind of have anticipated like there will be a lot of these branches. There's some that we've built for, there's some that I think we're kind of ready to build for when we need to. And we also like, think a lot about how do you make a good developer experience where let's say, think about just documentation or skill files for agents. People are going to be using coding agents when they're building these. And so there's a lot of institutional knowledge that gets built up when you're doing this kind of research, both for like a specific project or as a research team doing large scale training runs and being able to surface this information. Some of it is directly in the product, some of it is in the way we design the libraries. Some of it is in documentation or skill files that get shown to agents. And this is the sort of thing where we, we've designed it to be something that can evolve over time as the research literature evolves, as the best practices for different types of complex agents become more clear.

I assume you guys read Sutton's Learning from what is Age of experience.

Yeah.

Scale, AI era, data labeling. Do you think that constructing environments is sort of the natural successor to that?

Yeah, I mean, it very much seems like it kind of already is where it does seem like a lot of the focus from the major labs has shifted to they're still using a lot of human data. And so human data doesn't seem to be going away because creating these environments kind of by definition is for things that models aren't good enough at yet, which means the humans are better than the models in some capacity. And so identifying which pieces of information the human can most uniquely assist the model in improving its skill on I think is really the key to target, which is how do you create this information flow from the human who really has the expert knowledge on how to do some sort of thing, what does a job well done look like and get it into the model? And it does seem to be that RL is the most effective way to do this right now, where having tasks with prompts to grade with an LLM judge a rubric for what success looks like on a task is kind of the paradigm that's emerging for a lot of these cases where a human, sometimes it's the reward model, but kind of the most direct, visceral version of it is there's a set of questions about yes, no, was this done in the LLM's answer and that turns into the reward score. And so that requires a lot of human data.

Okay, awesome. Why create a hub for environments?

Yeah, I think the hub idea started by seeing a lot of different open source repos out there that had overflowing implementations of all those environments in a sense. And yeah, and in general we already or will already created a nice Verify Us framework before we even started the environment hub, where you had different examples for environments in there. And it was very much an approach to standardize the whole process even more. And beyond that, beyond just sharing those environments and having an open source platform for it, it's also about having a place where you can build a lot of infrastructure around them, which you can't really do if you just upload them to a GitHub repo or something like this. So yeah, having proper evaluations integrated with your environment so you can immediately test them across all frontier models is one of the features People are heavily using the environment hub then for you make it extremely easy to install one of those environments inside of a different trainer. So we obviously have our own large scale trainer with Primal, which we've been heavily optimizing for this. But yeah, we are very open there on the open source side to integrate with a bunch of different trainers because people have different needs on the trainer side as well. And that's how the whole idea of the environment hub and what has the community behavior been?

Do you see people forking, modifying these environments? Do you see them putting something 80, 20 out into the public domain? And then we're going to keep our secrets for ourself and, you know, not share that back? Like, what's the community behavior?

Yeah, I mean, there's definitely a lot of people we work with who want to keep their environments private, as you understand. But the value for them of it being a hub is that they can do ablations on ones that are kind of known to be. They can compare their private one versus some public one that might be on a similar type of task or for evals. There's a lot of value in having kind of mix and uniform implementations of popular benchmarks in a way that if you're doing a training run, you can plug in some. Some known eval as a way to monitor the progress of your own. And so maybe you're doing well in your environment. You can see. Does your environment also generalize to other tasks? And so having all these other tasks available is a really helpful way for people to be able to understand not just their own tasks, but other things they might want the model to be good at as well.

Yeah. Awesome. What are the most popular environments on the Hub today?

Yeah, I think it tends to be the ones that are these kind of. One is the ones that we use as the examples in the documentation that naturally in software tends to be the most popular ones. So the wordle stuff, the wordles one's popular, but I think one that we see a lot of interest around and one where I think there has been the most degree of people kind of branching and forking and turning it into different versions is one that we call WikiSearch, which is doing search over Wikipedia pages. But it's designed to be this template you could use for Agentix search more broadly. So there's a lot of applications where people want agents that know how to search over their internal documents or documents for a specific type of information. And having this kind of template for if you just, you just have to swap out the documents and. And now you have this environment ready to go where the rest of it is already kind of set up. That tends to be the sort of thing where we see a lot of value in people being able to bring other types of documents that they'd want to do agenda search over.

Yeah, got it. Okay, awesome. I want to maybe shift towards future research, you know, big blue sky questions, maybe the first one, Andre, I think, is one of your angels as well. He kind of has that infamous quote of RL is amazing, but it's quite inefficient and it's like sucking bits from a straw, I guess. Do you agree with that and what do you think is going to happen in the research side to make RL more efficient?

Yeah, I mean, I think it's definitely true that RL is using a lot of compute to get a pretty kind of small signal in terms of pure information, but I think in some ways that's part of the value of it as well. And I think one of the reasons that a lot of the labs have really focused on it is that one of the bottlenecks that's hard to scale is human data, especially high quality human data. And RL allows you to kind of trade off compute for data in a sense where you can get a lot of value out of a smaller amount of data by using more compute. And so the supervision coming from this data is small, but you can get a lot out of it, more so than you can via pre training or supervised fine tuning alone, as well as it's useful in cases where you don't necessarily have golden examples. So if you have a bigger model to distill from, that's great. But if you're already at the biggest model size that you have access to, then you kind of need to go into uncharted territory. And exploration is really the heart of rl. It's how do you explore and try out different things and maybe there are ways to do exploration that are more efficient than RL that people will discover. But this is kind of currently the the frontier of using compute to explore and improve capabilities. And so that's what we got for now for sure.

And I think I can't speak for Andrej obviously, but yeah, I would be curious to hear his views like two months later after the latest Druckish podcast. In a sense on his views, especially on the coding side for large scale reinforcement learning and how it actually helps there. If we look at something like Claude code, which definitely was already popular before, but definitely popped up more over the last one month, I would say then his views might change in a sense on the specific piece of how useful reinforcement learning can be in the coding domain generally we don't think that's going to be the end in a sense. Right. We generally think we want to be always at the frontier of what comes next in terms of paradigms. There is definitely lots of low hanging fruits still on the like pushing Agentica capabilities even further. But yeah, we also know the limitations in a sense. Right. Like some of the pieces we've been working on, where we definitely see limitations is on the context side. So yeah, I think there we just have a hard limit right now of how much tokens we can fit into a context. And you have been thinking there about ways on how to actually improve that in a sense.

Yeah.

Awesome. Switching gears a little bit. Open source, open weight models.

What do.

You see the role open weight models play? Does your infrastructure kind of work only on or work optimally on open weight models? Could you kind of help people do post training around closed weight models? How does that all work?

Yeah, so in many ways, like the trainer itself is going to require having access to the weights. And so if anyone who has closed weight models wants to use it, we're happy to chat. But more broadly, the idea of the environment is general across different types of optimization. And so we can do using the same infrastructure at the environment level for doing evals on closed models, for doing prompt tuning on closed models, for doing model selection, for evaluating agent harnesses. There's a lot of research that can be done around closed models just by having a way to do this experimentation. And so whether using open or closed models, you can create data that some platforms might let you upload, some examples that maybe you're distilling from a particular model into another where you use the environment as this data engine. So there's a lot of different ways you can use the tools to optimize models.

And do you need the weights? Like for example, can you kind of. Laura?

Yeah, so I mean the Lora I would consider still part of the fine tuning process. And that's what we recommend a lot of people do for RL anyways. And so like you don't need this necessarily the full weights, but like you can't. I can't upload my own Lora for GPT5, but I could bring an environment to the platform potentially. And so I think there's a lot of different ways you can do partial customization. And I would imagine that in many cases the degree of like how many do you need a loradaptor do you need full fine tuning is going to depend on the training recipe as well as the goal of your optimization.

What about can you do reinforcement learning on like the agent harness around a closed model?

Yeah, so I would definitely consider this in the domain of like. Like there's a world of prompt optimization that some people have been exploring in the research world that is in some ways kind of an analog of rl, but in prompt space where you've got like the spy. Yes, exactly. And so the GEPA algorithm got a lot of attention like late last year as kind of what seemed to be a better way of doing this. And so we have support for that as well with our environments where you can do this around different pieces of the harness, where this might be. What's the prompt used for a certain tool? What's the agent skill? What's the system prompt? There's a lot of these things that you can apply different types of optimization to.

Awesome. While we're on the topic of dspy, I think the DSPY authors also I have this new thing that is the current thing. Was it recursive language models? What do you guys think?

Yeah, we are definitely very interested in that. As I already said earlier, in a sense we are very interested in longer horizon agents and so on and actually solving things for those type of use cases. And yeah, I've been internally thinking for a long time about how can we have models learn how to manage their own context. So right now people are building a lot of scaffolds for context management and we believe something that is a bit more bitter lesson built in a sense is to have the model learn how to manage its own context. And yeah, I've been searching for different research in this kind of domain for a pretty long time and the recursive language model research direction is one of the most promising ones in our opinion. We've been, yeah, since Alex Sang, who's the original author of the RLM work, published it, we've been very interested in this kind of work, have been exploring it as part of our research as well. And a blog post out a couple of weeks ago that basically showed using this RM harness where you pretty much give a language model access to a variable in a persistent Python repl. So it can not have this whole context or the whole data as input in a sense, but it has it in this variable that it can then retrieve, it can transform it and manage its current context with that, and then also call other sub LLMs where the recursive part comes from to actually manage it. And yeah, that's the whole idea behind the recursive language model. We've been doing some exploration there on this front to actually just give current frontier language model access to this specific RLM harness. So not necessarily training in this harness, but just giving it access to the specific way of dealing with its own context. And yeah, that's been all been shown to improve benchmarks on very long horizon reasoning quite a bit. And yeah, we are very excited as like a new frontier in a sense to actually train in this as well, to let the model train or train the model to actually use this harness. And yeah, that's what we're going to work on over the next couple of months.

Super exciting. What else in the research domain? You guys have great research taste. What do you think is on the horizon?

I'm really excited about synthetic data research and it feels like there's a lot of stuff that feels like we should be able to do it, but you haven't really seen it emerge in the open in terms of creative ways of doing kind of self reflection. And I think people talk a lot about continual learning as this kind of idea that we're going to have to get better at models kind of learning things on their own. And I think the idea of using other tricks that we already know in conjunction in different ways, things like prompt optimization, things like distillation in conjunction with synthetic data, it feels like there's a lot of. I don't want to kind of go too deep into different directions, but it seems like there's a lot of room for exploration around having models curate their own training data, maybe curate their own environments and understanding which versions of this are most effective for like lifelong learning.

Love it. Okay, we're going to close on an optimistic note. If everything goes right, what does the world look like and what is the role that Prime Intellect serves in that world?

Yeah, great question. How to answer that on a high level overview? In a sense, I would say we don't want to have a world where all the future value of AI and all kinds of verticals is just owned by the big labs. We have something where we empower entrepreneurs and enterprises and so on to actually not get steamrolled in a sense and optimize their products better than they have the tools for doing so right now and just enabling this. And a lot more cloud code moments, a lot more cursor for X type moments that will be enabled through this.

Every company is a neolab.

Got it.

In some ways, I mean, if data is the bottleneck, if having the real expertise is the bottleneck, would you rather have the smartest person in history work at your company or someone who's been there for 30 years? And in some ways sometimes you really want the person who's been there for 30 years. There's a lot of expertise that comes from really understanding a problem deeply and interact with it over a long time and this is really what happens in training that is almost impossible to replicate in a short prompt. Where you really want the ability for institutional knowledge to compound over time for best practices to compound over time and this is how institutions and companies grow to be really powerful and successful is they stand on the shoulders of what they've done before rather than kind of resetting every day and we want to have this be accessible to any company that wants to do this and I think that's how we've thought about approaching it. Especially as software becomes easier for people to manipulate as the barrier to entry for coding becomes easier we see the same happening for AI research.

It's a really inspiring vision for the world. Thank you guys so much for joining today. You've really paved the way on environments and your environment hub and thank you for taking the time to demystify what an environment is and share your vision for the future.

Thanks.

Thank you.