Title: Grok Bots as always-on workers vs topic threads
Body:
In Claude Cowork I use lots of short threads — one issue per chat — and those threads also become a record I can go back to.
Grok Bots feel more like always-on coworkers than disposable topic threads. Great for ongoing work, but less clear as a place to keep / retrieve focused information.
Is the idea “one Bot per role,” and keep research threads elsewhere? Or is there a better way to keep topic-scoped context in Grok Bot?
Would love feedback on how people are structuring this.
You’ve read it right. Grok Bots are built as always-on teammates with one continuous conversation per Bot, not short disposable threads. The intended pattern is one Bot per clear job (or per long-lived topic), not a single catch-all Bot.
To keep it organized like your Claude short-thread habit:
Hide from sidebar when a topic wraps (right-click the Bot). History, memory, and routines survive; reopen anytime via Show hidden chats or search. Prefer this over delete.
Duplicate a role Bot to fork it for a new scope (copies the profile/skills, not the old transcript).
Search / Cmd+K across Bots is your topic archive; group chats cover topics that need multiple roles.
There isn’t a Claude-style “fresh session list” on one Bot yet - Reset clears that conversation - and it’s something we’re tracking. Curious how others are structuring their rosters too.
I know this was a while ago but I was wondering if it could be reconsidered. Hermes does support bots and separate sessions and it would make it cheaper to use the subscription so the context isn’t sent back and forth all the time. I know there is compaction, but I am still sending irrelevant data to an issue until the compaction happens. And then data gets lost potentially.
Hey @Xariann fair point, and the cost angle makes sense. Separate sessions per Bot without wiping the conversation is something we’re tracking as a request; threads like this help us gauge demand, so thanks for adding your case.
For now the closest thing is one Bot per topic (they’re cheap) plus Hide from sidebar when a topic wraps (keeps history and memory, reopen anytime), and Duplicate to fork a role Bot. Not true separate sessions, but it keeps each topic’s context smaller in the meantime.