back with our team training for the week.
We are gonna keep doing these as often as we can.
We're gonna be moving them to Thursdays as well.
Thursdays at noon, that just works better.
We typically do all of our client check-ins on Tuesdays.
And so this makes more sense
to kind of zoom out a little bit.
Everybody's had a little bit of time
to do some deep work sessions during the week.
And so I wanna just kind of chat
about a couple of things that we're working on.
We have been, there's just a lot.
There's a lot that's changing.
So what I'm gonna try to do is just spend
just a few minutes kind of showing you
what's changed since last week.
Like what are some things I'm messing with?
And then we'll jump into some examples.
Mainly we'll talk about like how we've been using
MCP servers now for the Innova dashboard.
I'll show you a little bit of that here.
So let me switch over to my demo here.
We now added MCP to our Innova dashboard.
This has been super helpful.
And so now when you are in cloud code
or whatever, you can actually spin up,
you connect to MCP, connect to the server here.
And we have access to all of the projects
and clients now inside of your favorite LLM.
You can get project details, status,
billing status, things like that.
You can read the framing docs.
And then of course you can go into
and actually pull down the task grid.
So you can get through like manage looking
at the slices tasks.
You can create, edit, move, delete, slide tasks
and even flag things as unknown.
So the cool thing here is we can load,
search for a project, pull down the frame
and then basically build out the tasks
for that project using cloud.
So you're not having to click in and do that.
Cause we get so used to having AI do things for us
in 2026 now that sitting there and clicking
into a task grid and typing out a task
just feels like a caveman.
So we wanted to automate all that
and help at least get kind of the first version
of it together.
And one thing that we're doing,
which I'm really liking is that we're able
to build our process into this MCP.
So when you pull down a project
and you start working on tasks
and it doesn't have a framing doc,
it's gonna let you know that we need a framing doc
before we can keep moving on this.
And then I'll pull up,
I think we had one that was the pull request.
We did this project for a client
and we had a little framing doc here.
And then we went through and built out
this little task grid.
And so it broke the project into some slices
for us and pulled tasks.
So this was just sort of a,
you know, we just did a one-shot prompt
on this to get it to build out.
There's of course you can keep editing it
and changing it and manipulating it.
And the idea would be that you would connect this
to your existing workflow.
So if I were to go start working on this slice,
I might pull down that slice from the task grid
into my terminal, go ahead and plan out
the changes I wanna make.
And then as you build it,
it can go and update the status.
So it starts to check off the items here
as it works through that.
And you may even have it like as it's planning it out,
you can just tell it, hey, also update the task grid.
We may find four or five other tasks here
that we didn't know we needed
once we actually get to working on it.
So I think this will become like a really beautiful UI
of what is actually going on in the project in real time,
you know, as you're working through tasks
and pushing, you know, changes and stuff.
So I'm really excited about task grid.
We'll also add it to the framing doc.
The reason I haven't completely gone all in
on the framing MCP just yet, you can pull it down,
but I'm also wanting to make sure that we bake in
all of our cloud skill that we talked about
in a previous video.
We did a whole training just on this cloud skill we created.
And of course you can take that skill
and put it into any LLM you want,
but that will allow you to basically take an idea
for a project and then get it much more fleshed out.
I'll grab one that we did recently.
So if I go to this project here, we have a new client.
We did a bunch of framing here for approval.
And I think these all went through that framing skill
and task grid and all of that.
And we had to do it across four different projects.
And you'll kind of see once it comes out that skill,
it kind of has a certain look to it.
There's a little bit of text to introduce,
what's broken today, why now?
These are all things that we've heard from Ryan
and others on as far as how to get something
really, really tight.
It's also being very,
antagonistic and not just agreeing with everything that you say. So a lot of times like we'll start
listing things here that might be a feature and it's very quick to say like, hey, you have put
a feature as an outcome. That is not what outcomes are. Outcomes are like a little bit more general
and they're more concrete and we can say that, hey, yes, we arrived at this outcome
versus like, you know, adding a specific dashboard view, you know, as a feature there,
you can kind of add that. And it feels easy like, oh yeah, we do want the dashboard feature,
but we need to be like a little more specific on how we build those outcomes. So these are
going to add guardrails to our entire process, which is very exciting. So we can actually bake
in these skills to the MCP. So when you start pulling it down, you start working on it. Even
if you don't have that cloud skill handy, you can basically use whatever LLM to reference that skill
and we'll essentially provide that as context when you connect into the MCP. So I'm excited
about that. I'm excited about where we're headed with it. We'll keep adding more features here.
So I'll update them on this page and you guys can create your own key and pull those down and test
it out. And there's a bunch of instructions here to get it connected to whatever LLM you want.
So that's MCP. That's what we've been doing there. And it is going to be really cool because we
have access to projects. Everything is being currently imported into this Superbase database.
So we have all of our timesheets. We have all of our Notion projects are getting imported. So when
you have access to the MCP, you actually have access to everything in Notion, and you also
have access to everything in Toggle as well. So there's a lot of things we're going to start to do
as we, let's say, want to use the MCP to create a client update. Well, now it knows that all these
tasks got created. And when they got completed, it knows what time tracking got, what happened
with this project. It knows maybe comments that happened in Notion. And we can basically have it
write an email for us pretty quickly inside of the terminal. So that's kind of where we're headed
with it long term. Also, I just got to say, we've been building this dashboard for a few months,
and you've been hearing me talk about it for months. It took me 90 minutes to get the MCP spun
up. It was insane how fast it came together. So what a time to be alive. I think I was talking
to Janata this week, and we're like, it's just insane. The pace at how fast things are moving,
you just have to be experimenting every single week with something. So this week was me setting
up the MCP. The other thing we're going to talk about next is, of course, OpenClaw, which has
broke the internet recently. And if you are living under a rock and don't know what OpenClaw is,
this is by Peter. I love this tweet, just because it was like his little history here. He's like,
sell his company for $100 million, spend three years, become jacked, come back from retirement.
He vibe coded 43 failed projects. Number 44 was ClawedBot, goes viral. Anthropic, of course,
sends trademark lawsuit, renamed it to MultBot. They hacked their accounts, rebranded to OpenClaw.
180 gift cards get acquired by OpenAI. And then you have, I think one of the other ones I saw
Sam Altman calls you a AI genius or something. It was the final bullet points on there.
And who knows how much, I think you try to find the figure, but it's multiple billions of dollars
that they used to acquire this open source project. So pretty crazy time to be alive.
And so if you're kind of wondering, okay, what is OpenClaw? How does it work? It essentially is
just taking an LLM and giving it full access to a machine. It could be your local machine,
not recommended. It could be a virtual private server. There's a lot of ways to set it up.
So yesterday I did that on our side and I did everything on a digital ocean droplet.
And we have like an Innovo VPN through Nord layer. So what I did is I basically just
whitelisted only that IP. And we also put in like a firewall layer. So there's a digital
ocean firewall as well here that we set up. And so this is how I'm using it at the moment.
And the way that I'm essentially working with this, I will connect through my SSH here
directly through the VPN, through all this to this, and it's all whitelisted.
It's pretty safe. And the other thing I'm doing, of course, is just I'm using a Slack
bot to just talk to it here. So I'm getting over cold. So I'm going to have to mute every now and
again. So Slack bot just chats directly with OpenClaw that we're running here.
And I'd locked it down in a number of different ways.
Because one of the things,
if you guys are playing with this stuff,
like, you know, this is, you are playing with fire.
So like, this is, you can easily give it a lot of control
and it can go off and do things on your behalf.
So be very careful to like give it, you know,
your Gmail access, careful to give it like,
you know, sensitive information.
I saw there's like one password integration.
I'm not testing it with one password.
So yeah, Greg said, don't give anything to OpenClaw
that you wouldn't just post publicly on Twitter.
That's a good example.
If you're setting up, so we set up something here
where we have a, we use the Sentry MCP server.
We use Sentry for our logging.
And so what I did is I created like a read only API key.
Oh my gosh, typing is hard today.
And then we can basically use just that read only API key
to talk to Sentry, for example.
We did that as well for GitHub.
So I have GitHub here and I created basically a read only.
And then I had to actually have it do right here.
And then I gave it some permissions.
This is, you know, TBD to say like, you know,
you're not allowed to, you know,
I think I said not allowed to, you know,
commit to master or whatever,
unless I specifically give you like an instruction.
So it's saying that it's gonna stick with that.
I don't know if it's gonna stick with that, we'll see.
And so basically creating these layers of security
is great because this means that it can only use this MCP
to read what's going on in Sentry
and get information from it.
And then this allows it to essentially talk
through this API key to GitHub.
And I've been extremely locked down on like just some,
I've only testing it on like one repo right now.
So I'm just saying this to the team as well.
Please test it, please play with things, do it safely
because this is like not only our company's data,
but sometimes it's our clients' data.
And so just make sure things are locked down very tightly.
I don't recommend at all running it on our local machine.
I look forward to those options.
I know there's some safe ways to do it,
but this seemed like the safest way for me.
And we were already using DigitalOcean
for all of our hostings.
This made a lot of sense.
And it took me about two hours to set this all up.
And then once I got it connected in Slack,
I've been chatting with it and it's been working pretty well.
So my little test yesterday was I had it go out
and look at tribe and like pull a bunch of things down
and say, hey, what are some of the errors
that you're seeing there?
And I think I can, let me see if I can find the chat history
and just show it to you in Slack
how this actually went down.
Because the first, oh, also I blew through
a few million tokens very quickly.
Cause I was like, let's just use Opus 4.6 on everything.
Like why would, or Sonnet or whatever the 4.6 version is,
the latest Cloud.
I was like, this will be great.
Use it through the API.
I've never really hit any limits.
Turns out that if you're on the max plan on Cloud
and you're in the terminal, there is no limit.
That's why I've never hit a limit.
As soon as you started using the API,
you run through credits super fast.
I think I spent like $25 in like maybe 30 minutes
and then I hit a limit.
Again, I've been so paranoid by it
that I have rate limits on our Anthropic account.
I have a separate workspace for it.
I have different limits put on it.
So as soon as it hit 25, I didn't go and bill like,
you know, two and a half thousand dollars.
At least I could, I got an email
and Anthropic cut off my API key.
So then I was able to go and like set it up a bit better.
So let me grab,
this would be cool to show you guys kind of the flow.
Let me see if I can share it.
Let's replace this window right in here.
So the way that it's working right now
is in my Slack account.
So I have Nova, I'm calling it and it,
let's see here.
So I got it set up and I basically just prompted it
to set up the MCP server itself.
Then it went and grabbed these issues.
It pulled some like random network issues.
We also had a ton of like downtime in one of our clients
and it created a little like list of things
that it found.
And then I said, hey, can you filter
for a specific environment?
Which I don't think it really did.
That's okay.
And it provided links to things I could jump in
and like go and look at those specific issues.
I said, okay, let's look at one.
The root cause is clear.
It's very optimistic at this point.
It goes and like spits out a bunch of code.
And I was like, I asked about context.
We were still around 138,000.
And then also it was very specific.
that it's kind of managing context on its own.
So I'm not sure how I feel about that,
but you don't really have a lot of,
especially through Slack to like start and end sessions
from what I can see.
So Hiza just messaged me like normal.
Okay, let's keep going through this.
And then we set up the, this,
I'm just making sure I'm actually not sharing my,
so I didn't, here's the thing,
like I don't, I didn't put my access token in the chat, okay?
Like that's telling it the key,
but what I did do is I can add it to the config file.
So I go back to my shell and go to the terminal and,
sorry, the SSH and I connect into the server directly.
And then I give it some instruction
to put into the config.
So it knows that it can use that if needed.
So far so good.
Again, I still have it as a read only,
so it's pretty safe.
And then it basically goes through and finds some issues.
This is really boring.
Basically where I got to was,
the cool thing here is kind of thinking of this
as a 24 seven team member.
So I would never, like I was telling Lucien today,
like both of us would never go in
and fix the thing that it fixed.
It's not really like a breaking issue.
It's just that there happens
to be all these like errors in there.
Hopefully it'll fix it up,
but it wasn't even worth our time to really go explore this,
but it's totally worth a bot's time to go explore this.
So what we did is I said,
hey, like go ahead and push this change in.
And then a couple of times a day,
just go and check on this issue
and see if what you're doing is fixing it.
So it can kind of learn from it.
So I would never tell anyone on our team
to go and check something three, four times a day,
but I would totally tell this thing to go do it.
And so it's basically did that.
We went back and forth on a lot of different things.
And then let me just see where we got,
asked it to do a little recap
of everything it did for the day.
And then I was asking it about how we could share this bot.
Basically we can't share.
Let me just get to the end.
So then we also currently have a,
DigitalOcean had some downtime.
So I just shared the link with it.
It went and grabbed the issues here
and it's going to basically continue
to check on DigitalOcean status for me.
And then once it sees that DigitalOcean is good
and it's deployed,
then it will come back and start the sentry checks.
And it's just going to check those logs
every couple hours for me.
And then if it sees something that's useful,
it's just going to report back.
So I just wanted to show this whole flow
and I'm like deep in the weeds of how I'm using it.
And it's also very fresh,
but the shift here is not,
I'm not like prompting it
and it gives me information back.
I'm prompting it to go off and do a bunch of things.
And it's going to keep doing that until I tell it to stop.
And I'm going to forget about it.
And then it's going to come back to me
and start the conversation,
said, hey, I want to bring this to your attention.
I know I saw this.
So it's kind of flipping the,
changing the way that we have conversations
with AI a little bit
because it is this like living, breathing thing.
So that's kind of how I'm using it at the moment.
I thought it'd be helpful to kind of like diagram it.
Again, I'm a little bit into this,
less than 24 hours,
but we're totally starting to see the impact of it.
Obviously you can keep stacking these,
more and more.
There is a great DigitalOcean article
on like how to set OpenCLAW up.
And I actually just took that article and fed it to CLAWD
and I ran CLAWD in this SELI.
And we basically just, it read the document,
it created the plan and then it,
we pulled up terminal and basically prompted it that way.
I think I did use the DigitalOcean MCP for CLAWD
to go set the droplet up.
So CLAWD essentially assisted me in setting up OpenCLAW.
So that was very helpful.
And that's how I would recommend doing it.
Just look for that article.
If you want to do a DigitalOcean,
I just used that because we were already paying
for DigitalOcean and I didn't want to go set up
a brand new account somewhere else.
But lots of free ways.
If you're not wanting to do any of that,
there's a great tool called Emergent
that basically lets you fire it up,
kind of like a lovable style where you just plug it in
and you can be up and running in two minutes.
Again, you still have to be conscious
of all the security stuff,
but a lot more user-friendly if you don't want to be
in the terminal hacking around and stuff.
So it's a great time to be alive.
It's a great time to be coding.
This, I've mentioned this a hundred times,
but I'm going to say it every time we do a call,
we have spent so long doing...
The development process is actually getting much simpler
to build things.
So where we would, and by focusing on these two...
sides of it, where you're framing, you're prototyping,
we're doing task grids.
This is the really like the human strategy side,
is getting to this point of clarity.
Once you have that clarity, of course,
just using AI to build all these things,
fix whatever, deploy stuff.
That's where we need it to bug fix,
to monitor error reports, things like that
can all happen on this side.
And that's all coming from the agent side.
So what we're trying to do is build platform,
which kind of combines those two things
where we can kind of put the framing stuff in
through our dashboard.
We can put information on the task grid.
We're also starting to add transcripts
of all of our calls with customers
or all of our framing sessions.
So we have that as context as well.
So those things will start to become,
will start to show up not just in the MCP side,
but in the content, like we'll start to store that
as part of the database here of the platform.
And so it's, you've got to be experimenting with stuff.
Don't fall behind.
Like you can go a couple of weeks
and all of a sudden you feel like you're a few months
or a year behind, but just be experimenting with stuff.
Just be trying new things.
The models are getting better every week.
We do have to like invest a little bit in this.
Like these tools, some of these tools are not free,
but even if we're spending like,
I think our company's spending well over a thousand,
$2,000 a month on AI stuff,
that's still our lowest paying employee by a long shot.
And so like the amount of work and movement we can have
with very little money, is it crazy?
I mean, it's hard.
Cause like you're looking at like,
oh, do I spend $20 on Cloud or $99 on Cloud?
Like it seems a lot when you think of it as personal level,
what you think as a company
and what that's allowing you to do.
What Cloud is allowing me to do as a founder
to work on our apps, to build all this stuff out.
And I'm using it, I don't know how much,
pretty much a few hours every single day for $99 is insane.
Like it is insane.
It's the highest value, lowest cost thing
in our entire company.
And so like, I'd probably pay it
if it was like maybe 10 or $15,000 a month,
I'd probably still pay it.
So at a hundred bucks a month,
it's just like an absolutely insane.
And maybe I'm like the old guy who's like,
man, this technology is like so amazing,
but it is super incredible.
And I'm still loving all the pieces of it.
So very cool.
Okay, so I think we'll probably end there.
I had one other tweet to show you that I saw from Jason,
which was super cool, is that they're adding,
potentially having like CLI control for Basecamp
and Hey at some point, which is gonna be amazing.
Because unfortunately, as far as I can tell,
like Hey is kind of locked off from all this
because it's not a standardized email tool.
So it'd be cool if we can plug Hey into all of this,
this cool diagram and have your email be context as well.
So cool, we'll end it there.
And then we're just gonna chat as a team, but yeah.