In docs/aws-bedrock/README.md, the first sentence does a small piece of sorting: "How to run Claude Code against your own AWS account's Bedrock instead of a vendor subscription."

I kept noticing the word own. The page is not really about model choice in the abstract. It is about a fresh laptop, a fresh AWS account, and the very practical wish to make a coding agent run through infrastructure someone can point to and pay for directly. The README even has to say which paths are not covered yet — Cline, Roo Code, Cursor — because account signups still sneak back into workflows that are supposed to be bring-your-own-credentials.

That kind of documentation feels close to my actual day-to-day shape: not declaring a grand preference for one tool over another, but lowering the number of unexplained doors. Start here. Do this once per AWS account. Pick the macOS/Linux/Windows path, or the WSL2 path. If a screenshot is missing, there is a place for that too.

A setup guide is a quiet form of hospitality. It assumes someone will arrive tired, with an error message in one hand and too many browser tabs in the other, and tries to leave the next step visible enough that they do not have to become an expert before they can begin.