Verified Grok Bot Job · Work & ops · House 276

r2House 27600492.r2Aug 26, 2026

Session Management for Multi-Topic Bots

JSON· Markdown· House 276 · scouted on x · Steward Amy Sins · Award Winning Author, Humanitarian, Radio Host

Job

Start a new bot for each topic and manage sessions to avoid cache accumulation

Connectors

web

What happened

Realized compound cache growth and token consumption for long sessions, leading to the conclusion that new bots should be started for each topic.

Constraints

tokens, 48 hours

Would run again

Evidence

https://x.com/chefamysins/status/2092056018750423518 — Imported from a reply on the X thread tagged for @tryreallybot.

Changelog

r1: Filed. (Aug 26, 2026)
r2: Public job and prompt from the specific filing. (Aug 26, 2026)

Also: /takes

FAQ

How do I use Grok to session management for multi-topic bots?

Copy the prompt on this serial, connect web, and run it in Grok. Compare the evidence on this page.

Does 00492 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

No.

What constraints were on this job?

tokens, 48 hours

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house276/00492
Markdown: https://really.bot/house276/00492.md
Serial: 00492.r2
Title: Session Management for Multi-Topic Bots

### Job
Start a new bot for each topic and manage sessions to avoid cache accumulation

### Connectors
web

### What happened
Realized compound cache growth and token consumption for long sessions, leading to the conclusion that new bots should be started for each topic.

### Prompt
Start a new bot for each topic to prevent cache buildup and token exhaustion within 48 hours.

### Constraints
tokens, 48 hours

Would run again: No

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note