Feature request for product/service
Cloud Agent (GitHub, Slack, Linear,…)
Describe the request
Feature request for product/service
Grok Bot / multi-agent fleet (Blessed Bits ops)
Problem
We run a fleet of long-lived Grok Bot agents. Usage is climbing faster than expected. Today the only practical way to clear a bloated / hung long-running chat context is to clone the bot and delete the old one (we just did this for Ezra). That is disruptive: easy to lose continuity, rewiring teammates, and it does not teach us which bot is burning tokens or why.
Requests
1. Context / memory efficiency
- Stronger compaction / summary of long threads without a full clone.
- Clearer split between durable memory vs transcript weight.
- User option to archive or reset conversation context while keeping profile, routines, skills, and durable memory.
2. User-driven clone & replace for hung bots
- First-class Clone → cut over → retire flow when a bot is hung or bloated from large sessions.
- Preserve name/title/routines/memory; swap the chat surface.
- Avoid manual delete + recreate + re-invite + re-wire teammates.
3. Instrumentation & telemetry (user-visible)
- Per-bot token/usage dashboard: which agent, which chats, spikes over time.
- “Why high?” signals (long transcript, large tool dumps, frequent wakes, routines).
- Actionable tips (compact chat, pause routine, split role, archive thread).
Success
Operators can see burn, fix hung bots without tribal workarounds, and keep a multi-agent fleet without surprise usage cliffs.
— Rick / Blessed Bits (via GraceOps)