@kakera_note_Hyu Play with it and learn along the way! Always put the gate in the sheet before you add the next bot. Draft only. You control what goes out!
@nowmodesol The four doors belong in the sheet before a single word exists. That's the vault! The next draft gets held against that....once you've figured it, copy that onto the next Bot so you don't have to constantly re-create it!
Everyone's posting 10 things people built.
Wrong list.
01 File the last 24 hours — GATE
02 Draft. Don't post. — GATE
03 Grok Build a page — TOY
04 See the books. Don't move a dollar. — GATE
05 Auto-send the follow-up — TOY
06 Connect Gmail — TOY
07 Compound a vault file — GATE
08 Tap send / spend / publish — GATE
09 Staff a 122-agent company — TOY
10 A bigger context window as the brain — TOY
A gate means I always have to tap send / spend / publish before anything goes out.
No tap/authorization? That's a toy
Knowing the difference and how/when to use it, changes everything!
@liamihorne@martin_casado@zachperret You don't have to give the Bot sensitive context, just give it the job sheet and the right gate. Since it's the same computer and logins, I just don't trust that separate bots create a security boundary.
@kaseyklimes@heyitsnoah If the rule isn't explicitly written into the Bot, you leave too much up to chance. I make sure to write the invariant into the job sheet. Then I recycle it for every Bot after.
@MadeByBilal True! The window is not a company itself. My suggestion is to write and save prompts, decisions, and corrections into a vault every bot can grab.
Then pull memory manually. Don't just count on the chat remembering for you.
In my mind, a 'hard gate' is a customized 'NEVER' list. The Bot cannot ever skip it or go above it.
The Bot drafts for me, but in this case, it can't send, spend money, or publish anything without my authorization.
You can find everything in the Grok Bot Skills Pack of things I've learned so far:
https://t.co/KrI4wrOsNx
@atmoio Took me a while before I felt it all 'click'....and the moment it changed, I truly noticed that Grok Bot is more than just an agentic chat bot, and really the hardest-working employee I could have! I just make sure each Bot has one job and I set up a hard gate.
@doakchop great question (I forget that it's easy to use lingo in the AI world, but may be a term not used by everyone!). I mean a 'hard gate' as in, making sure the Bots are set up with instructions or directions that include mandatory user approval before any high-risk decision is made to publish or send something. An easy way to start learning this is to chat with Grok first, explain your goal and the Bot's specific job/role and then have Grok give you the best prompt or language for creating a "gate" or "mandatory user approval", so that you can paste it into the Grok Bot. Once you do it a few times, you'll get the hang of it ! You can also create a universal rule or set of instructions that you can apply to all Bots you create in the future. Have fun building !
A bigger context window is a distraction.
A Company Brain is what you put in the vault.
Prompts. Decisions. Corrections. Shared by every person and every agent.