5 Comments
User's avatar
Fabrice Talbot's avatar

Very interesting article!

I was surprised you did not mention context management at all. My question to you: are grok bots nice toys or can it load a full blown context (Second brain or md files with proper routing) at session start? Can they share the same context instead of having to dedupe it inside each Grok bot (which would not scale)?

Eugeniu Ghelbur's avatar

I left this out of the 101 on purpose, Fabrice, because it needs its own post. Thanks for raising it.

Short answer: they are not toys.

- All your bots share one computer in the cloud. Put your notes there once, and every bot reads the same files. No copy for each bot.

- Each bot has its own memory, and that memory can be wrong. Keep the important facts in your files instead.

- In each bot's instructions, name the one file it should read first.

- Skills are shared too. Write a skill once, and every bot can use it.

My own notes work this way: github.com/eugeniughelbur/obsidian-second-brain

Fabrice Talbot's avatar

Interesting. Food for thoughts for your next article:

- how to I keep context platform agnostic, i.e. plug-and-play vs hard coded in Grok computer space (composability?)

- can context be on any cloud provider, e.g. OneDrive, GDrive

- how much do I control? Last thing I need is a “smart engine” that decides on my behalf

- Grok or not Grok? It’s yet a new app/UX, can it run on the background and push updates in Slack, Microsoft Teams, etc? Most companies already have a collaboration stack and the not should fit in nicely

- shared vs bot specific context: how do you do that? E.g. shared business context + mktg specific workspace context

Mr C Morales's avatar

I can already see bots becoming my primary form factor for my AI usage

Eugeniu Ghelbur's avatar

Same here. More Grok Bot posts are coming soon: how to share bots, how to build them, and which templates are worth it.