Clarify interactive shell app lifecycle#2436
Merged
Merged
Conversation
3 tasks
dangra
approved these changes
Jul 23, 2026
tripledoublev
marked this pull request as ready for review
July 23, 2026 20:10
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 of changes
Correct the Machines guide's description of
fly machine run --shell.When no app is specified, flyctl creates or reuses an app for interactive shells. Exiting deletes the temporary Machine, while the app remains available for future shells.
The generated command reference is intentionally unchanged in this PR. It is generated from flyctl and will be updated through the docs-sync workflow after superfly/flyctl#5026 merges.
Preview
Not applicable; this is a prose-only correction.
Related Fly.io community and GitHub links
Notes
Verified against the flyctl implementation and through end-to-end interactive-shell creation, exit, cleanup, and app-reuse scenarios.
Vale initially flagged the pre-existing heading
Choose a geographical regionbecause it checks the entire changed file. The follow-up commit removes “geographical,” simplifying the heading toChoose a regionto match terminology used elsewhere in the Fly.io docs. Vale now passes.