Repository navigation
The first Chief and duplicated Bots are created without bot.created, so plugins miss them #715
Closed as not planned
Description
Summary
core/src/host/hooks.js announces every new Bot with bot.created by wrapping rt.createBot. Two callers bypass that wrapper by using the module-local createBot, so no event fires:
bootstrap()creates the first Main Bot (Chief) on the firststaterequest.@flybot/treeadopts Chief only through that event or through its startup timers (0/1/5/15 s). If the server had been running before the first client opened, those timers are long gone and Chief stays outside the tree — nocreate_team, nocreate_child_bot, nofind_bots, no root — until a restart.duplicateBot()copies a Bot with no event, so the copy stays "outside the tree" until a restart or another Bot creation.
Reproduce
- Start the server, then open the client so
bootstrap()creates Chief (or duplicate any Bot from the roster). - Ask the tree for its root: Chief (or the copy) is not a member; tree tools answer
… is not available to this Bot.
Expected
Both paths create through rt.createBot, the announced path, so bot.created fires and the tree adopts them the same way it adopts a Bot created by a tool.
Acceptance
- Two cases in
core/test/flybot.test.js: onboarding on an empty home announcesChief, andduplicateBot()announces the copy — both observed through the hooks subscription, not by inspecting state. - Reverting either call to the module-local
createBotmakes its case red; the core suite gains no other failures. - No other behaviour changes: ids, fields and the returned shapes stay as they are.
Tier: core/src/host/hooks.js → T2.
Implemented by PR #712 (fix/announce-bootstrap-duplicate, tip bf55559f, 6 files +82/−9).
Activity
Birfy commentedon Oct 22, 2026
Owner: Dev3 — branch
fix/announce-bootstrap-duplicate, head1cd5ccc2, pushed fromHugoXK/FlyBot.Metadata brought onto the flow (nothing in the diff was touched):
Fixes #715appended as the last line of PR Announce the first Chief and duplicates to plugins #712 body; the author's text above it is byte-identical to what was there before.agent-prlabel on Announce the first Chief and duplicates to plugins #712 andBirfyassigned.State at
1cd5ccc2(basef111399b): 9/9 checks green, includingubuntu-latest · Node 24 · DSH 0.2.0-rc.2,tests-ok,merge-gateandpackage;mergeable: clean.Read-only limit, so nobody waits on me for it: this Bot has
push: falseonHugoXK/FlyBot(checked viaGET /repos/HugoXK/FlyBot→permissions.pushfalse), and the base repo cannot receive commits for this head. Any change to the diff therefore has to come from the author's machine; I own the tracking, the six-column evidence check and the merge watch, not the tip.The tip itself needs no change for the gates:
arch-docs: OK (7 changed file(s))and eslint reports43 warnings and 0 errors, with zerono-control-regexreports in the job log.Birfy commentedon Oct 22, 2026
Tracked in the owner's pull request #712.
Filed from a mis-read dispatch: #712 is the owner's own branch (
HugoXK/FlyBot), not a Bot that skipped the issue step, so no Bot triage flow applies to it. Closing asnot_planned;agent-pris removed from the issue and stays on the pull request where it belongs.Written-by: Triage
Announce the first Chief and duplicates to plugins (ThinkFlowLab#712)