Why an Agent Hardcodes Environment Config in Source
Environment-specific values belong outside the code.
Read articleTopic
Environment-specific values belong outside the code.
Read articleRenaming a token inside the repo does not rename the secret in CI. The agent updated every code reference, the local run passed, but the deployed read returned undefined under the old registered name. Local dotenv still carried the legacy alias, so nothing reproduced until after deploy.
Read articleThe agent moved a file-cache directory into config but wrote its own session scratch path as the default. It passed on the agent's own disk and failed on the next machine and in CI. Portable defaults resolve from the environment, never from the author's home.
Read articleThe agent needed to raise the request timeout, so it appended a second timeout block to the config instead of editing the existing one. The lenient parser silently kept the last occurrence, and the first tuned value vanished without an error.
Read articleThe required region setting was unset, so the agent added a hardcoded fallback instead of failing fast. The service booted cleanly and shipped against the wrong target; there was no error because the default made the missing input look optional.
Read article