Mark Bissell: evaluation

Transcript context

…You have the steering demos lined up. So we were just kind of see what you got. I don’t, I don’t actually know if this is like the latest, latest or like alpha thing. No, this is a pretty hacky demo from from a presentation that someone else on the team recently gave. So this will give a sense for, for technology. So you can see the steering and action. Honestly, I think the biggest thing that this highlights is that as we’ve been growing as a company and taking on kind of more and more ambitious versions of interpretability related problems, a lot of that comes to scaling up in various different forms. And so here you’re going to see steering on a 1 trillion parameter model. This is Kimi K2. And so it’s sort of fun that in addition to the research challenges, there are engineering challenges that we’re now tackling. Cause for any of this to be sort of useful in production, you need to be thinking about what it looks like when you’re using these methods on frontier models as opposed to sort of like toy kind of model organisms. So yeah, this was thrown together hastily, pretty fragile behind the scenes, but I think it’s quite a fun demo. So screen sharing is on. So I’ve got two terminal sessions pulled up here. On the left is a forked version that we have of the Kimi CLI that we’ve got running to point at our custom hosted Kimi model. And then on the right is a set up that will allow us to steer on certain concepts. So I should be able to chat with Kimi over here. Tell it hello. This is running locally. So the CLI is running locally, but the Kimi server is running back to the office. Well, hopefully should be, um, that’s too much to run on that Mac. Yeah. I think it’s, uh, it takes a full, like each 100 node. I think it’s like, you can. You can run it on eight GPUs, eight 100. So, so yeah, Kimi’s running. We can ask it a prompt. It’s got a forked version of our, uh, of the SG line code base that we’ve been working on. So I’m going to tell it, Hey, this SG line code base is slow. I think there’s a bug. Can you try to figure it out? There’s a big code base, so it’ll, it’ll spend some time doing this. And then on the right here, I’m going to initialize in real time. Some steering. Let’s see here. searching for any. Bugs. Feature ID 43205. Yeah.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.