Expand description
An agent’s Bundles list: the bundles picked for it, in order
(SPEC_RENAME_KNOWLEDGE_TO_MEMORY_2026_10_06.md §3.6).
The agent’s own bundle (AgentDefinition::memory_id) is not stored here:
it is always first and can’t be removed, so Store::agent_bundle_chain
puts it in front of the picks. The table is per channel, like the agent’s
own bundle (#3148); bundles themselves live in the identity store, so a
listed id can name a bundle deleted elsewhere, and readers skip it.
The Stash’s old Startup tab stored one bundle as startup_bundle_id
agent content. Reading the list folds that pick in and removes it, which
covers existing agents and one an older build writes later.
Constants§
- STARTUP_
BUNDLE_ CONTENT_ TYPE - The agent content type the old Startup tab stored its one bundle under.
Functions§
- agent_
picked_ bundles - The bundles picked for
agent_id(frommstore), looked up inbundle_store, in list order. A bundle that no longer exists is skipped. - format_
agent_ bundle_ block - The picked bundles’ part of the startup file: one
# [Bundle] <name>section per bundle with instructions, in list order, joined by the rule Global Memory uses.bundlesare the picks as found (a deleted one is already missing). Empty when none has instructions. - join_
startup_ blocks - The text launch puts after
# Memoryin the startup file: Global Memory, then the agent’s picked bundles, each part only when it has content.