Essential bootstraps are the first thing you should run after connecting to a new Lowkey agent. They don’t add optional features — they establish the baseline your agent needs to behave correctly and safely. Without them, the agent uses default settings that are often wrong for a production AWS environment: the wrong model context window, no coding standards, no memory search, and no disk space awareness.
Run all essential bootstraps at once
Paste this into your agent chat:
The agent reads every file in the directory and applies them in order. This takes a few minutes. When it’s done, it will confirm what was configured.
Run BOOTSTRAP-MODEL-CONFIG before any other bootstrap. It sets the correct model context window for Claude on Bedrock — without it, Opus 4.6 gets capped at 32K tokens instead of 200K, which causes frequent context limit errors during long tasks.
Run a specific bootstrap individually
If you need to re-run or update a single bootstrap, point your agent at the specific file:
Replace BOOTSTRAP-MODEL-CONFIG.md with the filename of whichever bootstrap you want to run. This is useful after an agent update or if you want to refresh a single configuration without re-running the entire set.
After the essential bootstraps complete, your agent writes marker files (e.g. memory/.bootstrapped-model-config) so it knows which bootstraps have already run. If you re-run the full essential set, already-completed bootstraps are skipped automatically.
