Develop at Idea Velocity - Jeffrey Lee-Chan, Snapchat

Workshop setup, so, um, there are some people who kind of have, like, never installed OpenClaw, and I want to kind of get them set up. And then the other people, like, want to try an experimental thing, which I haven't even fully gotten working, but I think for more advanced people that'll be cool.

Um, to get, like, a sort of staging environment and run to OpenClaw. So I think if I'm not, you know, too busy helping new people set up, then I'll try to help people, like, finish debugging the last part, or maybe someone else will get it.

Then I think, uh, 10 minutes Q&A, 10 minutes some more advanced topics, and then just more Q&A. And, uh, probably after every 5 minutes or so, we can do a bit of, uh, a few minutes of discussion. So I'll just set some timers to make sure I don't go off track.

Allright, let me start.

Allright. Can everyone see this presentation?

Yes.

Allright, cool.

Yep.

So

this kind of describes, like, my setup. Um, I'll just keep it really high level for this part where, when everything works, you know, maybe like 70% of the time, you describe your task. And then what's nice is OpenClaw will have, like, context and memory about what you're talking about.

So, for example, like, let's say I'm like, "Allright, fix this thing." It's a very brief Slack message, but OpenClaw can remember, like, what I've asked it to do before. So, for example, I'm working on this thing I'm calling a skeptic agent, and it's a custom code review thing.

But if I'm like, "Allright, fix the skeptic agent," or whatever,right, it kind of knows what that is, which is nice. You don't have to re-explain a lot. Um, I use multiple agents with work trees. That's very key for parallelization.

Uh, CI.

Under integration. But you can kind of see you can talk to it and be pretty brief and then, you know, usually get reasonable outcomes, but sometimes you'll have to debug it. So then it's like, allright, there's some timeout thing, I'm like, give it a longer timeout,right.

And then I asked it here, like, uh, you know, what are the priorities and what we're working on. And I'm reading it here. And then it might have just said, like,

I just made code for it,right. So another interesting thing about this is you can kind of see from, like, um, the types of responses I give, they're not that, like, um, special. As in, I actually think an agent could replace me.

So that's kind of what I'm working onright now to, like, get things even more autonomous. You know, and you'll see this with LLMs, like, you're working with them and they'll be like, "Hey, I've got this thing ready." And I'm like, "Okay, well, run the test,"right.

Allright, so I'll show the next slide now. Oops.

Okay. We'll go into some conceptsright now. Like, what is OpenClaw? So I think what's cool about OpenClaw is it's not just about a particular repo or the code, but more of the concept. So, you know, I've got this cool super diagram, but first concept is frictionless communication.

So I know we have other things like Claude cowork or whatever, but I think they still have a similar concept where it's like, can you, like, easily talk to your AI versus like, you've got a, um, remote desktop into your computer or you have to go sit down.

So that kind of enables, uh, certain really higher level of velocity. Um, then I think the central axis is very important. So, you know, there's a spectrum. Like, I kind of go, like, a little more cowboy and I give it access.

OpenClaw has these Agent Orchestrator Managers that manage your workers for you. Uh, or sometimes when I want more personal control, I use CMUX terminals. So CMUX is like a terminal program, but it's pretty good for parallelization and, um, AI development.

Then I use the open source framework that I forked Agent Orchestrator to do the workers. And then once it gets to here, this part is, like, not really controlled by me as much anymore. Um, so I'm calling them managed agents, but basically, like, you have a worker that runs Claude code, and Claude code itself can run agents, and those can have sub-agents.

So once you get to this Claude code part,right, this part is not exactly my stack, just stuff I use, but this part of the stack I'm changing a lot more. Um, I'll, I'll pause here to see if anyone has any questions or thoughts.

Um, can you hear me? So I, I have a question. So.

Go ahead, yeah.

The, the real question is, you know, why, why use OpenClaw versus directly use Claude?

So yeah, that's, that's definitely a good question. Um, the reason I use OpenClaw is specialization. So when OpenClaw makes a decision, I want that context to be more about, like, the spec or the goals or, like, the history of what I want in the task, rather than the code.

And you can just imagine this,right? As soon as you open up Claude, it reads Claude MDs, it reads skills, it reads, um, MCPs. A lot of those things are sort of independent of, like, the actual task. It's more about how to do the task.

Um, so imagine, like, 25% of your context already taken up by implementation. Versus, like, when you think about OpenClaw, you're like, okay, I want to think about exactly what I want to do and how it relates to all the other Slacks Jeffrey has sent me in the last two weeks and put it all together and give me, like, a reasonable spec.

Does every single thing a player does, but it does it without a browser,right. So you could use MCP, which usually is JSON or whatever, or HTTP. Doesn't really matter, actually. And then the final thing is the browser test.

So some things like are visual. I mean, maybe you could even have CSS tests or JS tests,right, and that kind of goes here. But then the final thing is visual. So I would recommend you, like, try, um, similar approaches to this and be like, okay, like, which problems truly needed that human or not.

Um, and I think what's kind of cool is, like, every quarter or maybe even every month, like, it improves. So before, like, I had to really manually test a lot because, like, you know, this worked fine,right, but these things didn't work that well with agents, like last year, like a year ago, even six months ago.

But now, like, um, agents are pretty good at, like, nailing down a lot of browser tests for me. Versus, like, when I started, my agent would have a lot of problems, you know, finding a pop-up and entering a password.

Now, no problem. Um, that was a little long, but does that kind of address the theme of your question?

Yeah, I think this is good, good. Thank you.

Okay. Just, just remind me for all these Slash commands. I'll put, um, links here instead. Allright, cool. Anyone have any other questions related to some of that stuff?

Allright. If not, I will go here.

Allright, so here's, uh, two websites that I've built.

While that loads, I'll show this one. So this is like an AI RPG. Um, what's cool about this is you can I've got a default campaign, for example. Um, I can pick some options. I've got an avatar. And, uh, what's cool about this is it builds a custom world for you that reacts to you.

So you can, like, kind of say whatever you want, do whatever you want. You'll get a story back. Um, the main difference between playing this versus, like, um, you know, you could just always go into Gemini chat or, or ChatGPT or whatever is that, um, I have, like, a D&D system.

So if you play your own, like, games or novels, like, you kind of just win too much. Versus, like, with this, you'll actually do, like, dice rolls and be like, you know, did the person actually, um, did you actually succeed in your action or not.

Allright, so while this is going, I'll also, um, show this thing. Yeah, so this is funny. Um, this website is like a multi-AI analysis website. Um, so what I found was, like, whenever I was doing research or, or whatever, I would go to multiple models and I would be like, what's the answer?

Then I copy and paste them all. I put them into one model. Um, so pretty simple concept, but this does it for you. So usually I like these answers better than, like, asking one model and I'm like, okay, how do I do this workshop?

So I can be like, okay, what's the status?

Um, the latest PR now. And, um, what I like about this is it has that sort of vertical tab type of thing. Because when you go horizontal, it's really easy to lose track of your tabs. Um, but we've got notifications too.

So when this thing is finished or this is finished and I need to look, it'll give me a notification. And I can just focus on clearing the notifications. So here, um, the way I'm using these terminals, usually it's more like a manager rather than a coder.

Um, and it's kind of interesting, but it gives you a certain benefit where I feel, I feel like the worker is not biased anymore. So when I, when I code with these directly, um, I usually feel like there's a bias where it wants to say things are really working or whatever,right.

Versus, like, you know, um, and I'll show this. One sec. If this had been working in PR 294 by itself, I think it would have been like, this PR is amazing. Like, we got to merge it,right. But then this one was like, no, like, there's another PR that should supersede it and probably we should just close this PR,right.

So that's kind of the benefit you get where the manager has a different context, um, than the workers.

Uh, let's see. Allright, so this is compacting whatever. So it'll take some time to complete. Don't want to wait for it, but when it completes, you see these notifications and I think my efficiency has improved a lot with CMUX.

Um, I think is Austin or someone from CMUX here?

Yeah, I'm here. What's up?

Cool. Yeah, so Austin is, uh, one of the guys behind CMUX. Um, you know, big fan of it. And I'm not, I'm not paid to say this or anything, but big fan of CMUX. Uh, I've been using it a lot.

I don't know, you can spend a minute if you want to talk about anything cool about CMUX.

Yeah, so, yeah, I'm one of the creators of CMUX. Uh, really happy to have Jeff as one of our power users. Um, and also, like, kind of endorsing it for free. Um, but yeah, lots of, uh, yeah, lots of things that we're shipping.

We shipped, uh, Claude Code Teams integration. So if anyone is using Claude Code Teams and wants to actually see what the sub-agents are doing, it'll automatically spawn terminals for that. Um, we also shipped, uh, CMUX SSH. So if you do any SSH work, um, you can use our native CMUX SSH to, you know, do your Tailscale, et cetera.

Um, to other computers, you can even use it to run your own OpenClaw, um, in your Mac minis. Um, but yeah, just, uh, one of the creators. Please feel free to email me if you have anything that you think is a bug or any feedback, feature request.

Um, I'm always available. And yeah, I just love seeing people using CMUX and always want to take as much feedback as I can to, like, get them as, get them.

Okay, so just download that.

Yeah. They actually have an app too, so the app might be nice.

Yeah. Okay. And then use that to help me get back in and set, set up.

Yeah, exactly. Yeah.

Okay. Okay, cool. Thanks.

Allright. Just using the sandbox. It should not. Where would you, um, have you, have you run into any troubles, Aaron, about sandbox token usage?

Uh, no. I'm just, I'm not technical at all.

Oh, yeah, yeah, yeah.

I have OpenClaw installed, so I'm just.

Okay.

Very newbie questions.

No, no, no.

But I appreciate you being friendly.

No bad questions. All good. Um, yeah. Uh, no, the sandbox wouldn't do that. Um, I think if, if everything's working well for you, you know, keep using the sandbox. For me, I just, you know, don't use the sandbox and so, so far nothing bad has happened.

But I think if I had an external bot, then I would use the sandbox too.

Changing the model, testing a new model, like, it'll go down and then I have to figure out how to get it back up again. So I think I want to set up the sandbox because.

Oh, sorry, sorry. Um, okay, wait. There's two kinds of things. Okay. The sandbox that most people talk about means, like, they run it in Docker or they, like, have it running in an isolated part of their system. But the other one was the one where I made the staging instructions where I was like, oh.

Yeah.

Okay. So.

That's what I'm referring to.

That could double your token usage if you send the same work to both of them. If you have two of them,right. Um, but I think the way I would use it is not like that. Like, I think I would do local development and then I would run integration tests on the, um, sandbox or staging one,right.

So I have two of them. And then once, like, everything's good, then I would merge the code and deploy to the production one. Um.

I see.

So it wouldn't double your usage, but it would definitely increase it. But then the benefit is you might have some more reliability. So.

Yeah.

I, I made some instructions and I was kind of in the middle of setting it up, but then, you know, it's like competing with the other one. So I got to debug it.

Yeah.

But I think, you know, it's, it's worth trying out though. So I add that for more advanced people to give it a, uh, give it a try.

Cool. Thanks. What are.

Or even if you're not as advanced, if you want it, you know, you can try it.

Yeah, I'm definitely going to play around. But what, uh, what model do you use? Like, do you have a something that, like, a default orchestrator model and then use, like.

Yeah, so.

Say for this model.

I mostly use Codex 5.3. Um, I found, I found, uh, GPT 5.4 to just use more tokens. Um, and even 5.3, like, like, I, I just get destroyed all the time,right. So I might have to adjust.

Yeah.

Um, so basically I use this until, like, this is getting low and then I just switch to Minimax, which is not as good, but it kind of gets the job done. And then.

Yeah.

This is more about money than, like, preference, but some, some work I can still kind of just do, um, here. So I don't always have to.