e/acc. one human, many agents. stats and systems. doomers in shambles.
Sector X
Joined February 2019
- Tweets5.1K
- Following5.7K
- Followers4.6K
- Likes705K
Part 2: scripts fix the fetching. The next leak is memory.
Every bot re-reads its whole chat each time it wakes up, so long chats get expensive fast.
My fix is a shared brain. One folder of plain notes all my bots read from:
- Every chat ends with a short note. Decisions, numbers, open questions
- One bot edits the main files. Everyone else just reads
- Bots load only the section they need, never the whole thing
- One bot fetches a link, the rest read its note
Chats become disposable. The brain is permanent.
How to stop hitting Grok Bot usage limits: stop using it like a chatbot
My split last 7 days: chats 61%, group chats 24%, routines 9%, bot-to-bot 6%
In a plain chat app, a cheaper model is your only lever. Grok Bot gives every bot its own computer. Most people never use it.
The play: scripts do the fetching > routines run on top of the scripts > chat is only for thinking
Steps:
- anything your bot repeats (prices, stats, feeds), have it write a script once
- the script runs on the bot's computer on a schedule and dumps a small file. zero bot usage
- point your routines at that file instead of having the bot research from scratch
- keep chat for instructions, decisions and thinking. it's the costliest thing you do
- in group rooms, only invite the bots that topic needs. every bot reads every message
The catch:
- someone has to write the scripts once. ask your bot to do it
- scripts break when a source changes. have a routine check they still run
Reply with the one thing your bot does every day and let's see if it can be scripted.
Bookmark this before you hit your limits again.
How to stop hitting Grok Bot usage limits: stop using it like a chatbot
My split last 7 days: chats 61%, group chats 24%, routines 9%, bot-to-bot 6%
In a plain chat app, a cheaper model is your only lever. Grok Bot gives every bot its own computer. Most people never use it.
The play: scripts do the fetching > routines run on top of the scripts > chat is only for thinking
Steps:
- anything your bot repeats (prices, stats, feeds), have it write a script once
- the script runs on the bot's computer on a schedule and dumps a small file. zero bot usage
- point your routines at that file instead of having the bot research from scratch
- keep chat for instructions, decisions and thinking. it's the costliest thing you do
- in group rooms, only invite the bots that topic needs. every bot reads every message
The catch:
- someone has to write the scripts once. ask your bot to do it
- scripts break when a source changes. have a routine check they still run
Reply with the one thing your bot does every day and let's see if it can be scripted.
Bookmark this before you hit your limits again.
How to run 13 Grok Bots without them talking over each other (org chart below)
My setup: 13 bots plus group chats. Routines are only ~8% of my usage. Chat is the rest.
The play: one job per bot > lanes in group rooms > one bot gets the final word.
Steps:
- give every bot one job and one anti-job (eg. My X bot writes drafts, never DMs anyone)
- in group rooms, each bot owns a lane. eg. macro, sources, fundamentals, quant
- rule: re-read the room before posting. new facts or corrections only, otherwise stay silent
- one coordinator bot reconciles at the end. no recap
- routines stay quiet unless there's something to act on
The catch:
- bots still repeat sometimes. the rule is new
- chat burns way more usage than routines. shorter replies save more than pausing routines
Reply with how many bots you run and their jobs, let's see if we can optimize.
Bookmark this before you build your next bot.
