Unverified50% confidenceFactExact time
The .env file is usually gitignored and is not automatically carried over when a worktree is created, which may cause an agent to read wrong default values or fail to start.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFull credentials should not be pasted into chat windows or hard-coded into project code; they should be stored in a keychain or written to a .env file excluded by .gitignore.67% similarUnverifiedIn the OpenCode official documentation, both the .env protection example and the company.guard example register an execute.before hook only for the read tool, and do not intercept the behavior of reading files via shell commands (such as cat).66% similarUnverifiedWhen a coding agent's hook crashes, times out, or points to a nonexistent script, most tools by default choose to let it pass (fail-open).61% similarUnverifiedThe OpenCode migration table maps v1's shell.env hook to v2's ctx.shell.hook("create.before", ...), which can be used to inject variables into the command environment, but throwing an error will likewise fail the command.60% similarUnverifiedThe reason a wrong environment variable name can pass locally but fail online is usually that locally there are default values, a .env file or variables injected by the IDE, while online hosting platforms such as Render require manual configuration in the console.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1064622API
curl https://kongchang.com/api/v1/knowledge/claims/1064622MCP
get_claim(id=1064622)