docs(llms.txt): clarify BTC env loading and reservation auto-extension#78
Merged
Conversation
Punch ran the agent quickstart end-to-end and snagged on two doc gaps: - `BTC_PRIVATE_KEY` only loads from a `.env` in the CWD where `alw` runs, but the doc didn't surface `export` as the equivalent CWD-agnostic path. Also added an explicit pointer for the most common error string so a panicked agent maps it back to "your env didn't reach the process". - BTC-source reservations look like they're about to expire when really validators are running the optimistic extension loop in the background. Spell that out so an agent watching the timer doesn't panic.
….allways/.env) The CLI now loads env vars from three places in precedence order, so the doc no longer needs to warn agents about CWD-only behavior or push them toward `export` as a workaround. Trimmed the BTC sending block in both the static llms.txt and the in-app AgentMarkdown copy.
anderdc
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two doc gaps an agent running through the quickstart hit on first contact:
BTC_PRIVATE_KEYonly loads from a.envin the directoryalwruns in. The doc said so but didn't surfaceexportas the equivalent CWD-agnostic path, and didn't tie the most common error string back to "your env didn't reach the process". Both added.alw view reservationcountdown doesn't yank the swap.Test plan
/llms.txton the deployed preview and confirm the new BTC env block + auto-extension bullet land where intended.