boot

Loading shared team protocols on agent startup requires running a boot sequence that reads designated team-wide protocol documents, ensuring consistent behavior across automated tasks and coordinated multi-agent workflows.

Agent memory sync with git remotes works by pulling recent memory changes from a configured remote repository to update the local agent state, ensuring persisted memory stays synchronized across different workstations or pods.

Selective memory preload is the process of loading global and project memory files explicitly marked for a specific agent while skipping files not intended for preload, ensuring agents start with only relevant context.

Yes, the boot sequence applies to agent startup in both local workstations and cluster pods, preparing context for automated tasks by syncing memory, reading protocols, and inspecting recent code changes.

The best way to prepare agent context for multi-agent workflows is to run a boot sequence that syncs git-backed memory, ingests shared protocols, preloads agent-specific files, and inspects recent code commits.

No, a remote repository is not strictly required; the boot sequence ensures git-based memory synchronization occurs only when a remote exists, otherwise loading local agent state directly.