Homepage
Not present in the local metadata.
brew package intelligence
flyctl
Automic Vault tracks flyctl because plain text fly.io access token matters when AI agents run command-line tools on macOS.
overview
What Automic Vault knows about flyctl
Command-line tools for fly.io services
Commands and aliases
No executable aliases were found in the local package database.
radioisotope
Plain Text Fly.io Access Token
flyctl stores its API token as access_token in ~/.fly/config.yml. Our isotope stores that token in the macOS keychain and injects it as FLY_ACCESS_TOKEN only while `flyctl` runs.
Local README excerpt
flyctl Radioisotope
flyctl stores its Fly.io API token as access_token in ~/.fly/config.yml. It also supports FLY_ACCESS_TOKEN, which is a clean wrapper boundary for runtime credential injection.
This radioisotope migrates the saved access token into the macOS keychain, removes the plaintext token from the config file, and wraps flyctl so the token is present only while the command runs.
Caveats
- We currently migrate
~/.fly/config.ymlonly. - Other non-secret flyctl config entries remain on disk.
- Direct execution of the original binary will not receive credentials.
Source: data/radioisotopes/flyctl/README.md
Coverage source
Caveats
- We currently migrate ~/.fly/config.yml only.
- Other non-secret flyctl config entries remain on disk.
- Direct execution of the original binary will not receive credentials.
install metadata
Resolver facts
| Package key | brew:flyctl |
|---|---|
| Last updated | 2026-05-20T21:14:27Z |
| Pulse | updated |
source trail
Generated from repository data
This page is regenerated by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.
Used sources
- Nucleus package database
- local isotope README
- radioisotope security manifest