Docs: the agent machine is kept warm, not scaled to zero - #280
Merged
Conversation
Both files still described the auto-stop behaviour the agent had as its own app. It now stays warm because Fly's proxy gives an auto-started machine ~8s to bind its port and this process needs ~10s, so every wakeup against a stopped machine failed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Both files still described the auto-stop behaviour the agent had as its own app. Corrected to match reality after #279.
Docs-only, so
Test & Deployskips on push — but PR checks still run, which is the asymmetric-filtering design working as intended.🤖 Generated with Claude Code