Bot「转世」：长聊天太贵时，让新 Bot 接任同一岗位而不丢经验

场景

一个小型 Bot 组织（CEO Bot、各项目 keeper、技能管理员、新闻观察员）跑了几周，每个 Bot 背着整段聊天，越长越贵；清空聊天又会丢掉学到的东西

A small org of bots (a CEO bot, per-project keepers, a skills librarian, a news watcher) ran for weeks; every bot carries its whole chat so each turn costs more, but wiping the chat loses what it learned

他们怎么做

把「岗位」和「在岗者」分开：岗位（角色、职责、汇报线、组织图位置）存进账号内所有 Bot 可读的共享记忆；在岗者是当前这个 Bot（自己的聊天、记忆和 Routine）。在岗者太贵时退休，由新 Bot 接任同一岗位。交接便条只写：岗位指针（不重写职责）、常设规则、当前状态与未完成工作、待我决策事项、它的 Routine 清单（供新 Bot 重建）、踩坑经验。新 Bot 读便条→把指针存进记忆→重建 Routine→确认；旧 Bot 改名「(retired)」并指向继任者，其他 Bot 更新汇报线。规则：只在聊天很长且常被唤醒时做；不在任务中途换；便条里不放机密；未经本人同意不删旧 Bot。整套写成可复用 Skill「bot-metempsychosis」

Split the position (role, job description, reporting line, place in the org chart; kept in shared memory every bot on the account can read) from the holder (the current bot with its own chat, memory and routines). When a holder gets too expensive it retires and a fresh bot takes the same position. One handover note carries: a pointer to the position (never a rewritten job description), standing rules, live state and open work, anything awaiting a decision, its routines so the new bot can recreate them, and hard-won lessons. The new bot reads it, saves pointers to memory, recreates routines and confirms; the old one is renamed '(retired)' with a pointer to its successor and other bots update reporting lines. Rules: only when the chat is long and the bot is woken often; never swap mid-job; no secrets in the note; don't delete the old bot until told. Saved as a reusable skill, bot-metempsychosis

结果与限度

作者自述做法，未给用量节省数据；帖子曝光很低（约 34 次），尚无社区反馈。

The author's own method with no usage-saving numbers; the post had very low reach (~34 impressions) and no community feedback yet.

同场景的其他案例

• 剑桥学生 + 创业者：按生活领域分 Bot，Chief of Staff 独占每日任务清单并调解冲突X, 2026-11-10
• 用银行「集团授信」的思路管 Grok Bot 周额度：分项限额、节奏线和上限缓冲X, 2026-11-10
• Grok Bot 定时搜 X 热点 + 飞书多维表格素材库 + Claude 写稿的内容流水线X, 2026-11-08