Agentic Engineering in Grok Bot — Transcript
Full transcript
- 0:00Hi, captains. I'm back with another
- 0:02video. This time showing you how I use
- 0:04my Grokbot setup to get work done. I'm
- 0:07just going to dive into my real setup
- 0:09here. So things may be a little bit
- 0:11messy, but I still think it's more
- 0:13useful to show you the real stuff
- 0:15instead of demos. Let's get into it.
- 0:17This is my Grokbot. I mainly use Grokbot
- 0:20for maintaining my open source projects.
- 0:23Um so if you haven't come across my open
- 0:25source projects yet, uh I have a bunch
- 0:28of open source projects. They are mostly
- 0:30agentic tools
- 0:31um and a lot of them got quite some
- 0:33popularity. So uh if you go into it,
- 0:35there's a lot of issues and PRs coming
- 0:37in.
- 0:38Uh maintaining these projects is not an
- 0:40easy effort. And Grokbot helped me so
- 0:42much with this. So we can see here I
- 0:46actually just asked Grokbot how much it
- 0:48helped me over the last month. It helped
- 0:51me process over 2,000 items
- 0:53split between issues and PRs. Um that is
- 0:56a lot of work. The only reason I could
- 0:59have kept those projects moving was
- 1:01because of my Grokbot setup here. So I'm
- 1:03going to walk you through how that
- 1:05works. Um I can probably show you a real
- 1:07example of how the automation works.
- 1:10Uh let me go to a smaller repo so it's
- 1:12less scary.
- 1:14Um we can see here in this repo there
- 1:16were issues and there were PRs, right?
- 1:19Uh if we go into a random PR here, um we
- 1:22can see this PR was raised by a
- 1:24contributor last week. If we scroll to
- 1:26the bottom here, we can see there is a
- 1:29comment from me
- 1:30speaking as Kuhn's first mate. Thanks.
- 1:33This is tidy change. And then there were
- 1:35a bunch of
- 1:37comments made, right? Like feedback on
- 1:39what the PR is supposed to do before
- 1:42it's safe to merge. Everything here came
- 1:45from my Grokbot, not myself directly.
- 1:47And pretty much every issue and PR in my
- 1:49open source repos gets a comment like
- 1:52this. And these comments guide the
- 1:54contributors through the process of
- 1:56getting their changes merged and getting
- 1:57their ideas implemented. If the PR is
- 2:00ready, it will give comments like this
- 2:02and uh tell the contributor what changes
- 2:04have to be made. And if the change is
- 2:06good and aligns with all the rules that
- 2:08I set for the repo, then FirstMate will
- 2:10merge the PR automatically. If the PR
- 2:12needs a decision from me, for example,
- 2:14it's a ambiguous product decision uh
- 2:16that's changing how things work, uh then
- 2:19it will escalate to me in Grok Bot. And
- 2:21I'll go back to Grok Bot now to show you
- 2:23how that works. Um so in Grok Bot, you
- 2:25can see on the left hand we have all
- 2:27these bots, right? Um I have one bot per
- 2:30open source repo. Uh so if I go to
- 2:32Treehouse, this is a bot that is
- 2:35specifically for triaging issues and PRs
- 2:38in my Treehouse repo. Basically, what
- 2:40this bot does is that uh it has a bunch
- 2:42of routines. There's a daily triage,
- 2:45there's a release process, and the
- 2:46cadence, uh how frequently this routine
- 2:49runs actually depends on how popular the
- 2:51repo is. So Treehouse is not a very high
- 2:54traffic repo, so a daily triage is
- 2:56enough. Uh for example, my FirstMate
- 2:59repo is a bit more busy, uh so it
- 3:02triages every 4 hours. So every bot is
- 3:05different here. Um and this triage will
- 3:08basically look at the open issues and
- 3:10PRs that haven't been triaged or have
- 3:12been updated since, and it will look
- 3:14into what's the right next step and make
- 3:16the comments I showed earlier uh or take
- 3:19actions to merge the PRs or close the
- 3:21issues. This is one example of an
- 3:23individual bot for one repo. I actually
- 3:25never come into this chat uh of this
- 3:28individual uh bot. I only talk to them
- 3:31through my FirstMate. FirstMate is the
- 3:33orchestrator agent that manages all
- 3:35these other agents for me, and it does a
- 3:37lot more than that actually. Uh I will
- 3:38show you in a bit, but I only talk to
- 3:40FirstMate. Uh you can see uh it's the
- 3:42only agent I talk to. I pretty much just
- 3:45close this uh all the time. And
- 3:47FirstMate uh will bring issues to me,
- 3:50bring things that needs my attention.
- 3:51For example, uh here it brought me uh
- 3:54captain FirstMate CI is hitting this
- 3:56limit. Okay, that's not good. Uh so that
- 3:59means uh the CI pipeline is probably
- 4:01failing on the first mate repo right
- 4:03now.
- 4:04Splits the slow jobs. Yeah. So it's
- 4:07suggested some potential solutions. I
- 4:10actually want to come back to this cuz I
- 4:11think this has repeated a few times. I
- 4:13want to solve this for good, not just
- 4:16keep patching this. But for now, I think
- 4:18you can get the idea that every
- 4:20individual bot's work is communicated
- 4:23through the first mate to me, and I only
- 4:25deal with first mate here. So problems
- 4:27from all these repos will surface in
- 4:29this single chat. I can just easily deal
- 4:32with them here. Many people actually
- 4:33already have a chief of staff kind of
- 4:35bot, right? But first mate is actually a
- 4:38little bit different. The first mate
- 4:39Grok bot started from the foundation of
- 4:41my open source project first mate here,
- 4:44which has been battle tested by a lot of
- 4:45users for many, many months now. And I
- 4:48think it's probably fair to say it's one
- 4:50of the projects that pushed the furthest
- 4:52on the chief of staff paradigm. It's got
- 4:54thousands of forks and a lot of active
- 4:56contributors. The first mate bot
- 4:58borrowed a lot of key learnings from
- 5:00this project on how to be an effective
- 5:02orchestrator. Here, let me show you some
- 5:04examples.
- 5:05I can go into the instructions of the
- 5:08first mate bot here. And if we go into
- 5:11context, memory, skills. Yeah, a lot of
- 5:14the instructions are in these skills.
- 5:16And one thing I want to show you is I
- 5:19think it's in the project management
- 5:21part. The first mate bot here actually
- 5:23uses a local SQL Lite database to manage
- 5:26the tasks. The benefit of this database
- 5:28is that first it's strongly persisted.
- 5:31So if the agents get reset or runs
- 5:33compaction, it doesn't lose anything.
- 5:35It's kind of like giving the bots a
- 5:37linear or Jira to work on complex
- 5:40projects.
- 5:42And the other thing that may be
- 5:43interesting to look at is in first mate
- 5:46charter.
- 5:47So there's a lot of instructions on how
- 5:49first mate manages the crew mates.
- 5:52One thing that may be interesting to
- 5:53point out is that when first mate
- 5:56notices that the crew mates are making
- 5:58mistakes
- 5:59or working inefficiently, it will update
- 6:02the behavior of those crew mates so that
- 6:04the crew don' make the same mistakes
- 6:06next time. This has been super
- 6:08beneficial uh and I can show you one
- 6:10example uh that I collected a while ago.
- 6:12This was from the First Mate bot
- 6:14summarizing what kind of improvements
- 6:16have been made to the other bots in the
- 6:18last two months and there's a lot of
- 6:20very concrete improvements on
- 6:22inefficiencies and noise. These
- 6:24improvements were made as the crewmates
- 6:26do their work and First Mate as the
- 6:28orchestrator and supervisor will just
- 6:31observe and make these tweaks so that
- 6:33the crew works more and more efficiently
- 6:35over time. First Mate also has uh a
- 6:38bunch of built-in uh engineering
- 6:40workflows uh like adversarial review uh
- 6:43lavish for planning. So basically when
- 6:45you import this uh First Mate uh bot
- 6:48into your Grok bot you get a whole stack
- 6:50not just a prompt. Maybe I can show you
- 6:52how I use First Mate to create this uh
- 6:54individual crewmates so I can just say
- 6:57create another triage crewmate uh for my
- 7:00new open source repo called headless.
- 7:05Yeah, that's it. If you're curious uh
- 7:08what I was using for voice input I use
- 7:10this tool called Handy. Uh I'm not
- 7:12affiliated with them or anything. Uh
- 7:14this is a free open source tool. I like
- 7:16to use an independent voice
- 7:18transcription tool instead of those
- 7:20voice inputs inside each app because
- 7:22then I can set a uh consistent key bind.
- 7:25I can have a consistent dictionary as
- 7:27well. Uh if you look at my Handy uh I
- 7:30think
- 7:31uh
- 7:32going to settings here.
- 7:33Uh yeah, it's really cool. You can just
- 7:35choose your own model like whichever
- 7:37model that works best for you. Um and I
- 7:40have this uh
- 7:43where is it? Advanced.
- 7:45Um yeah, I have this custom words set.
- 7:48These words are like really easy to mess
- 7:50up. Uh so when I add them here I can use
- 7:52them consistently everywhere uh which is
- 7:54great. Yeah, and now First Mate is
- 7:56creating another bot uh just like these
- 7:59ones. It said founded captain this is
- 8:01the repo. It has 20 open items uh from
- 8:04outside contributors. Uh yep, this is a
- 8:07new repo um which is really quite new.
- 8:09It's a It's an agent skill for setting
- 8:12up headless machines.
- 8:14And it's already got over 100 stars. I
- 8:16just published this a few days ago,
- 8:19which is awesome. So there's a lot of
- 8:20issues that I should probably take a
- 8:22look at. So once First Mate set up the
- 8:24triage crewmates, the triage crewmates
- 8:25can help me a lot with processing those
- 8:28issues. And here we can see the headless
- 8:30crewmate is already here, right?
- 8:32It's already starting to do things and
- 8:35it's being told by First Mate on what to
- 8:37do. Yeah, so this is going to be the bot
- 8:39that processes this headless
- 8:41repo for me moving forward. And it's got
- 8:44a routine now.
- 8:45It's doing the first pass triage as
- 8:47well. It's covering one PR and a bunch
- 8:50of issues. Yeah, so we'll just I'll head
- 8:53back to First Mate. I don't need to look
- 8:54at the crewmate there.
- 8:56But basically it's doing the triage. Now
- 8:59it's telling me that this repo has no
- 9:01vision.md.
- 9:02This is a very important concept I want
- 9:04to maybe touch on.
- 9:06So the reason I can let the bots
- 9:10process a lot of these PRs for me and
- 9:13know what is safe to merge.
- 9:16For example here, why did this bot make
- 9:19these comments and say these things are
- 9:21needed, right? These are not random. I'm
- 9:23not letting the LLM decide those things.
- 9:27Every repo I have has this vision.md
- 9:29file.
- 9:30And this vision.md file basically wrote
- 9:33down the principles for where I want to
- 9:36take this project, right? What are some
- 9:38of the boundaries? What are some of the
- 9:40principles? What kind of changes do I
- 9:41want to take? What kind of changes do I
- 9:43not want to take for the project? And
- 9:45every triage crewmate will respect this
- 9:48vision.md file and use this to determine
- 9:52what kind of PRs are safe to merge
- 9:54versus not. And that is in addition to
- 9:56good engineering practices. Yeah, and
- 9:58now this is telling me this headless
- 10:01repo does not have that yet. I actually
- 10:03should go write that down. So let me do
- 10:04that separately. And if you're curious
- 10:06how I write those vision.md files, this
- 10:08is the skill that I use. Um, this skill
- 10:11will actually push you really hard uh
- 10:14with hypothetical changes to the product
- 10:16and then test your boundaries to figure
- 10:18out what are the things that you are
- 10:20actually good with versus not. Uh and
- 10:22then after a few rounds uh it will help
- 10:25you write down your vision. I'll
- 10:26probably not wrap it whole into this
- 10:28right now. I might make another video at
- 10:30some point to introduce some of these
- 10:32important skills that I use. Uh if you
- 10:34think that's interesting, then let me
- 10:35know in the comments and I can
- 10:37prioritize based on what is interesting
- 10:39to people. Okay, back to Grokbot. Um we
- 10:42just started this headless crewmate,
- 10:44right, to triage the headless repo. And
- 10:47uh I think it's already done some work.
- 10:49We can see here two messages from
- 10:50headless. Uh this is um the headless
- 10:53triage bot sending messages to the
- 10:55firstmate bot and the firstmate relaying
- 10:57them to me. Uh this is useful because uh
- 11:00sometimes the bots will send something
- 11:02that doesn't require my attention and
- 11:04firstmate will just send something back,
- 11:06right, without bothering me at all. So
- 11:08although it may feel like oh the bots
- 11:10are sending messages to each other, uh
- 11:12is it wasting tokens? It's actually
- 11:14pretty useful. Um so now this is
- 11:16something that actually needs my
- 11:17attention. That's why firstmate uh send
- 11:19this message to me. Uh it says five of
- 11:22the open issues are real bugs. Okay. Uh
- 11:25the worst one is this uh on Windows. Uh
- 11:28there is an SSL setting. Uh okay.
- 11:30Uh this is another risk. Uh okay. This
- 11:34one PR number 25.
- 11:37Uh
- 11:38okay. This is a four line fix. That's a
- 11:40very easy fix to bring the code back in
- 11:42line with what the doc already promised.
- 11:44Okay. Uh so that's a correction of uh
- 11:47what we already want.
- 11:48Um
- 11:50um there is no grep tile. Okay, okay.
- 11:52Some of my other repos have grep tile
- 11:54enabled uh because grep tile um gives
- 11:56open source repos some free credits to
- 11:59go do code reviews, which I find pretty
- 12:01useful. Uh but on this repo I haven't
- 12:02set it up yet. Uh that's okay. But
- 12:04because I don't have the vision.md file
- 12:07written down yet, uh I want to be a
- 12:09little bit careful. So I'm going to
- 12:11actually look at this PR.
- 12:12Uh so this PR, yeah it's really just
- 12:15four lines.
- 12:16Um and the PR was raised through no
- 12:19mistakes, which we can see here. It's
- 12:22done a bunch of live validation to make
- 12:24sure it actually works. I pretty much
- 12:26all my open source repos require using
- 12:29no mistakes to raise the PR because then
- 12:31it ensures there's a minimum quality
- 12:33bar. So I can see this PR has already
- 12:35gone through a lot of rigorous internal
- 12:37steps before it's even raised here. So
- 12:41here we can see yeah a comment was
- 12:43already made by me which was coming from
- 12:46the triage bot.
- 12:48And it's saying CI is green, change
- 12:50looks good on the merits.
- 12:52Relaxes this. This is a captain decision
- 12:55hold. Okay. So because there's no
- 12:57vision.md, the bot actually think this
- 13:00behavior change requires my attention.
- 13:02So it said it's not waiting on the
- 13:04author.
- 13:05It's a captain decision hold. Captain
- 13:07means me. So that's why the message got
- 13:10to me and I'm here to decide whether
- 13:13this is the right thing. And I think I'm
- 13:15going to actually look at this.
- 13:17It's really just like correcting how the
- 13:20string matches
- 13:22and some documentation. So this is all
- 13:24good. I'm going to go back to the bot
- 13:26and say merge 25 and allow that going
- 13:28forward.
- 13:31So there we just triaged one PR, right?
- 13:33And first mate will continue on giving
- 13:36me other things that need my decision.
- 13:38So let's see what it comes up with. Also
- 13:40here you can actually see it's updating
- 13:42agent profile. So first mate is now
- 13:45updating headless to say it's okay to
- 13:47not have greptile now, right? So this is
- 13:51one of the things that happens when you
- 13:52have a first mate as the orchestrator.
- 13:55It just smooths out all these rough
- 13:57edges and make the crew mates work more
- 13:59and more smoothly down the road. Yep and
- 14:01first mate said the crew will merge it
- 14:03down and then immediately there's a
- 14:05message from headless saying it's
- 14:06already merged. Okay. So this basically
- 14:09this was done.
- 14:10If we go back to the PR, yeah it's
- 14:12merged. And
- 14:14I think we actually yeah a thank you
- 14:17note as well.
- 14:19So that's basically the automation
- 14:21handling this and occasionally the
- 14:23things the decisions will come to me and
- 14:26it's me reviewing some of the ambiguous
- 14:28stuff. Okay, now I'm curious what other
- 14:30decisions I have to make so I'm going to
- 14:32talk to first mate.
- 14:34What are some of the other PRs waiting
- 14:36for my decision?
- 14:38This is actually where first mate is
- 14:40going to read the database.
- 14:42If you see first mate is not talking to
- 14:44any crew mates right now.
- 14:46It's just reading the database and it
- 14:48will know which PRs are waiting for my
- 14:50decision
- 14:51without having to do a lot of messaging
- 14:53back and forth between the crew mates.
- 14:56Oh okay, this is actually a lot.
- 14:5888 PRs
- 15:00waiting for my word.
- 15:03Okay.
- 15:05Time sensitive. Okay.
- 15:08Okay.
- 15:10I'm going to yep, I'm going to say ahoy.
- 15:13Ahoy is a shortcut for giving me the
- 15:16most important thing
- 15:18one thing at a time. So let's see first
- 15:21mate I think it will actually do this.
- 15:24One thing waiting on you whether to go
- 15:26ahead with this one
- 15:28runs every PR checks on Ubuntu as well.
- 15:33Okay, it runs the PR CI pipeline on an
- 15:35additional OS version to just check
- 15:39whether it has problems. It's a
- 15:41contributor PR.
- 15:43I think this is good.
- 15:46But I'm curious why don't we block the
- 15:48PR when we know there's going to be a
- 15:50problem, right?
- 15:51Shouldn't we make this PR check actually
- 15:54block the PRs because it's going to be
- 15:56very soon that we will be forced to
- 15:58migrate.
- 16:01Okay.
- 16:02So yeah, sometimes these decisions come
- 16:04to me and I have to discuss with first
- 16:07mate a little bit.
- 16:09And first mate is checking how this PR
- 16:11does on that today to tell me
- 16:14based on source of truth. So yeah, let's
- 16:16see.
- 16:17Some of these decisions do need require
- 16:19some discussions.
- 16:20Um, so it says it's actually pretty
- 16:22quick. Um, captain, you are right. It's
- 16:24about to become required
- 16:26um since this now passes on this.
- 16:29Um, should we move to this? Yep, I
- 16:32actually think we should just move to
- 16:33this because it's going to be happening
- 16:36very soon. So,
- 16:37uh let's migrate. Okay. So, that's
- 16:39another decision made. Um, and I think
- 16:42after that I can just ask for another
- 16:43decision. Yeah, this is basically how I
- 16:45deal with the queue of all the issues
- 16:47and PRs that are coming to my open
- 16:50source repos. Yeah, it says the first
- 16:51mate crew has the rework of this
- 16:53underway. This is my rule that says
- 16:56basically if I have a slightly different
- 16:58idea for how a PR should be done, I will
- 17:02actually pay the cost of doing the
- 17:03modifications instead of asking the
- 17:05contributor to do that. Um, if it's a
- 17:08very big rework, then I'll send that
- 17:10back send the feedback back to the
- 17:12contributor.
- 17:13If it's just different opinions, I will
- 17:15do that. So, the crew will do the work.
- 17:18And if we look into the first mate bot
- 17:21here,
- 17:22it's viewing the PR. It's going to do
- 17:24something something. And then to make
- 17:26the code changes, it's going to use the
- 17:28cursor cloud agent. Yeah, you can see
- 17:30here launching cloud agent, right? So,
- 17:32it's using the cursor cloud agent to
- 17:34actually do the coding work. It doesn't
- 17:36do the work in this bot directly. Cursor
- 17:38cloud agent is a really good way to
- 17:41scale up a lot of this heavy coding work
- 17:44to a large amount of sandboxes. So, even
- 17:46if I have to make 100 PRs right now,
- 17:48this computer the Grokbot computer will
- 17:51not get too busy. So, I'm not going to
- 17:54like just sit here and wait. I'm going
- 17:56to say ahoy again. Basically just keep
- 17:59asking first mate to give me one more
- 18:01decision one more decision. And there's
- 18:04like 88 waiting for me. So, I'm not
- 18:06going to finish everything tonight, I
- 18:08don't think. So, yeah, I'm just here to
- 18:10show you how I work with first mate in
- 18:13Grokbot to do this open source
- 18:15maintenance, right? And you can see it's
- 18:17really beneficial to have one single
- 18:19first mate that can work across
- 18:21different projects for me. Otherwise, I
- 18:23will have to jump between all these
- 18:24bots, which is pretty much an
- 18:26anti-pattern uh in my eyes now. Oh, one
- 18:29thing I do want to go back to, which was
- 18:31that first mate uh CI was red, right? Uh
- 18:34we saw that earlier. Where is it? Yep,
- 18:36here. Um so I don't know why Grok bot
- 18:39will gray out some of these uh previous
- 18:41decisions. I think it's a new behavior,
- 18:43but basically I can just uh reply to
- 18:45this message and say uh what should we
- 18:48do about this now? Um actually I I want
- 18:51to show you something. Um
- 18:54ask the Kun bot to uh figure out how
- 18:57would Kun go about this.
- 19:01Uh
- 19:02there's a little uh typo here. Okay.
- 19:04Uh Kun bot uh is a really cool bot. Uh I
- 19:08will show you here. Um there's this bot
- 19:10called Kun. This bot basically has all
- 19:13my knowledge, uh everything I wrote in
- 19:15the public. Uh so my tweets, my uh blog
- 19:18posts, my YouTube videos, everything uh
- 19:21distilled into this bot. And the way it
- 19:24works is that uh I have this uh Kun
- 19:28repo.
- 19:29Uh you can actually find this as well.
- 19:31Uh it's a uh skill that you can use in
- 19:34any agent, not just Grok bot. It's a
- 19:36skill that is basically a near real-time
- 19:38distillation of my experience and uh
- 19:41knowledge and tools, workflows, and
- 19:42skills. Um the way this works is that in
- 19:45this uh repo, you can see this
- 19:48opinions.md.
- 19:49Uh these are actually my opinions. These
- 19:52are distilled from everything I said in
- 19:54the public, right? So um you can read
- 19:57this file. Uh it's really interesting. I
- 19:59I when I read it, I was very surprised
- 20:01how accurate it is. Um I I have a whole
- 20:04workflow um to uh generate this file
- 20:06every day based on what I said. So
- 20:09there's opinions, there's tools, uh what
- 20:12kind of tools that I use. Um and then
- 20:14there is uh assets content. Yeah,
- 20:17there's content as well. So every single
- 20:19video uh that I made, you can see the
- 20:22transcript uh written here. And
- 20:25basically, this is like everything I
- 20:27wrote or said or published in the
- 20:29public. It's all in this repo. And then
- 20:32the skill knows how to use all this
- 20:34content to answer questions. So
- 20:37basically, the more I write in the
- 20:38public, the more videos I make, the more
- 20:41blog posts I write, the more tweets I
- 20:43tweet,
- 20:44the more powerful this skill and the bot
- 20:46will be. So if I go back here, this bot
- 20:49is basically just using that skill.
- 20:51Let's see what First Mate said to me.
- 20:53The Coden Bot's answer is to leave the
- 20:5530 minutes limit alone.
- 20:58It's planned for fixing this at three
- 20:59parts, okay? Split the tests across
- 21:02parallel jobs.
- 21:04Yep.
- 21:06Warn when any job has its 20 minutes.
- 21:09Yep, that's something that I very often
- 21:11do. I set a lower threshold to get some
- 21:15warnings
- 21:16and so that we can actually fix things
- 21:18before they reach the hard limit.
- 21:21Speed up lint. Cool.
- 21:24These are actually like probably things
- 21:27I would do.
- 21:28And I likely already set those in some
- 21:31of my tweets in the public.
- 21:33Should we ship the Coden plan?
- 21:37Yes,
- 21:38I think that's a good idea. Basically,
- 21:40it's kind of interesting you see me
- 21:43talking to my bot,
- 21:44but this is actually pretty useful
- 21:46because I don't want to think about
- 21:48these things all the time, right? I
- 21:50already know how to solve some of these
- 21:52problems, so I just let the Coden Bot
- 21:54solve that. And you can use that too.
- 21:57You can just import the Coden Bot into
- 22:00your Grok Bot and ask it to solve like
- 22:03various kind of problems for you,
- 22:05especially when you think those problems
- 22:07are things that I may have some
- 22:09expertise on, then the bot can help you
- 22:11much faster than I could. Something
- 22:13that's even more fun is this Distill
- 22:16Anyone bot. This is another bot that I
- 22:18share that you can import into your Grok
- 22:21Bot as well.
- 22:22This bot can help you distill anyone a
- 22:26bot.
- 22:27So here I was playing. I distilled Mark
- 22:30Zuckerberg and Elon Musk and
- 22:33Sam Altman I think. And I asked them to
- 22:36discuss various kind of AI topics. It
- 22:39was really fun to watch. But basically
- 22:40this can be used to distill anyone that
- 22:43has public content. As long as they
- 22:45publish content publicly, then you can
- 22:48distill them into a bot and you can talk
- 22:49to them, ask them questions. This is
- 22:51very useful for getting a proxy to some
- 22:54of the domain experts that you would
- 22:56love to get inputs from. So you can very
- 22:58often just ask, hey how would that
- 23:00person solve this problem, right? Maybe
- 23:02just for the fun of it, let's distill
- 23:04someone else.
- 23:06Let's distill Jensen Huang. Okay.
- 23:11Let's see what happens. Okay, the
- 23:14distillation is happening.
- 23:16I hope it found the right person. I'll
- 23:18lock his identity from Wikipedia and
- 23:21check with you before saving. Okay,
- 23:23good. Okay, it's trying to confirm with
- 23:25me. Okay, this is
- 23:27founded Nvidia. Yep, that's him.
- 23:30So yeah. So now it's got the right
- 23:33person. It's now trying to actually
- 23:35fetch the content.
- 23:37Jensen Huang is locked. I'm setting up
- 23:39his folder, starting the first pass now.
- 23:41Cool. All right, it's done. Cool, taken
- 23:43from 22 talks and interviews and 21 of
- 23:47the posts. Okay,
- 23:48let's see. Okay, let's just talk to
- 23:51Jensen.
- 23:53What's on your mind? No, I think I will
- 23:55want to ask, how do you think about
- 23:59Chinese models?
- 24:02Let's see.
- 24:04Okay, it's got back an answer.
- 24:06Not the answer I was looking for though,
- 24:09but it's okay.
- 24:11One interesting thing is that this
- 24:14distillation process actually creates a
- 24:17voice profile.
- 24:18So this bot will actually talk like
- 24:21Jensen.
- 24:22And that's something that's really cool.
- 24:25You can see here,
- 24:26look, you have to start with the facts.
- 24:29Something like This is actually similar
- 24:31to how Jensen talks, right? So, this is
- 24:34something that's really cool, and I hope
- 24:35you all will have fun with this. All
- 24:37right, that's it for today. I will share
- 24:40links to all these Grok bots that I
- 24:41mentioned, so you can import them into
- 24:43your Grok bot as well. All of them are
- 24:45free. I'm not trying to sell anything
- 24:47here, just trying to share something
- 24:49that I have been using and hope you will
- 24:51find them useful as well. Thank you for
- 24:53watching and see you next time.
About this transcript
This page contains the full transcript of Agentic Engineering in Grok Bot by Kun Chen, generated from the public captions YouTube serves with the video. The transcript has 4,457 words across 662 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.