How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

fly - Prompt - OpenSmartRoute

Name: fly
Author: kevin-earl-denny

Prompt file imported from kevin-earl-denny/city-doodle (.claude/commands/fly.md). Copyright stays with the author.

/fly - Fly.io Deployment Management

Manage Fly.io deployments, secrets, scaling, and monitoring.

Subcommands

deploy

Deploy to Fly.io.

/fly deploy                 # Deploy current app
/fly deploy --no-cache      # Deploy without build cache

secrets

Manage application secrets.

/fly secrets list           # List secret names
/fly secrets sync           # Sync .env.local to Fly.io
/fly secrets set KEY=value  # Set a secret

logs

View application logs.

/fly logs                   # Stream logs
/fly logs --no-tail         # View recent logs

status

Check application status.

/fly status                 # App and machine status

ssh

SSH into running machine.

/fly ssh                    # Interactive shell
/fly ssh "command"          # Run command

Instructions

When the user invokes /fly:

For `deploy`:

Check if Fly CLI is installed and authenticated
Check if fly.toml exists
Run deployment:

# Standard deploy
fly deploy

# Without cache
fly deploy --no-cache

Report deployment status and URL

For `secrets list`:

Run fly secrets list
Display secret names (values are hidden by Fly.io)

For `secrets sync`:

Check if .env.local or .env.production exists
Use the Fly secrets provider:

from lib.vibe.secrets.providers.fly import FlySecretsProvider

provider = FlySecretsProvider(app_name="app-name-from-fly-toml")
results = provider.sync_from_local(".env.local", "production")
provider.deploy()  # Deploy the staged secrets

Report success/failure for each secret

For `secrets set`:

Parse KEY=value from arguments
Run fly secrets set KEY=value
Report success

For `logs`:

# Stream logs
fly logs

# Recent logs only
fly logs --no-tail

For `status`:

Run fly status for app overview
Run fly machine list for machine details
Report app URL, machine status, regions

For `ssh`:

# Interactive
fly ssh console

# Command
fly ssh console -C "command"

Example Session

User: /fly deploy

Claude: I'll deploy to Fly.io.

Checking prerequisites...
✓ Fly CLI authenticated
✓ fly.toml found (app: my-app)

Deploying...

✓ Deployment complete!

App URL: https://my-app.fly.dev
Machines: 2 running in iad
Version: v42

Common Issues

Issue	Solution
Not authenticated	Run `fly auth login`
No fly.toml	Run `fly launch` to create
Build failed	Check Dockerfile and logs
Health check failing	Verify /health endpoint
Out of memory	Increase `memory_mb` in fly.toml

recipes/deployment/fly-io.md - Full Fly.io documentation
recipes/security/secret-management.md - Secrets handling

Install fly and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# /fly - Fly.io Deployment Management Manage Fly.io deployments, secrets, scaling, and monitoring. ## Subcommands ### deploy Deploy to Fly.io. ``` /fly deploy # Deploy current app /fly deploy --no-cache # Deploy without build cache ``` ### secrets Manage application secrets. ``` /fly secrets list # List secret names /fly secrets sync # Sync .env.local to Fly.io /fly secrets set KEY=value # Set a secret ``` ### logs View application logs. ``` /fly logs # Stream logs /fly logs --no-tail # View recent logs ``` ### status Check application status. ``` /fly status # App and machine status ``` ### ssh SSH into running machine. ``` /fly ssh # Interactive shell /fly ssh "command" # Run command ``` ## Instructions When the user invokes `/fly`: ### For `deploy`: 1. Check if Fly CLI is installed and authenticated 2. Check if `fly.toml` exists 3. Run deployment: ```bash # Standard deploy fly deploy # Without cache fly deploy --no-cache ``` 4. Report deployment status and URL ### For `secrets list`: 1. Run `fly secrets list` 2. Display secret names (values are hidden by Fly.io) ### For `secrets sync`: 1. Check if `.env.local` or `.env.production` exists 2. Use the Fly secrets provider: ```python from lib.vibe.secrets.providers.fly import FlySecretsProvider provider = FlySecretsProvider(app_name="app-name-from-fly-toml") results = provider.sync_from_local(".env.local", "production") provider.deploy() # Deploy the staged secrets ``` 3. Report success/failure for each secret ### For `secrets set`: 1. Parse KEY=value from arguments 2. Run `fly secrets set KEY=value` 3. Report success ### For `logs`: ```bash # Stream logs fly logs # Recent logs only fly logs --no-tail ``` ### For `status`: 1. Run `fly status` for app overview 2. Run `fly machine list` for machine details 3. Report app URL, machine status, regions ### For `ssh`: ```bash # Interactive fly ssh console # Command fly ssh console -C "command" ``` ## Example Session ``` User: /fly deploy Claude: I'll deploy to Fly.io. Checking prerequisites... ✓ Fly CLI authenticated ✓ fly.toml found (app: my-app) Deploying... ✓ Deployment complete! App URL: https://my-app.fly.dev Machines: 2 running in iad Version: v42 ``` ## Common Issues | Issue | Solution | |-------|----------| | Not authenticated | Run `fly auth login` | | No fly.toml | Run `fly launch` to create | | Build failed | Check Dockerfile and logs | | Health check failing | Verify /health endpoint | | Out of memory | Increase `memory_mb` in fly.toml | ## Related - `recipes/deployment/fly-io.md` - Full Fly.io documentation - `recipes/security/secret-management.md` - Secrets handling

{ "prompt": "# /fly - Fly.io Deployment Management\n\nManage Fly.io deployments, secrets, scaling, and monitoring.\n\n## Subcommands\n\n### deploy\nDeploy to Fly.io.\n\n```\n/fly deploy # Deploy current app\n/fly deploy --no-cache # Deploy without build cache\n```\n\n### secrets\nManage application secrets.\n\n```\n/fly secrets list # List secret names\n/fly secrets sync # Sync .env.local to Fly.io\n/fly secrets set KEY=value # Set a secret\n```\n\n### logs\nView application logs.\n\n```\n/fly logs # Stream logs\n/fly logs --no-tail # View recent logs\n```\n\n### status\nCheck application status.\n\n```\n/fly status # App and machine status\n```\n\n### ssh\nSSH into running machine.\n\n```\n/fly ssh # Interactive shell\n/fly ssh \"command\" # Run command\n```\n\n## Instructions\n\nWhen the user invokes `/fly`:\n\n### For `deploy`:\n\n1. Check if Fly CLI is installed and authenticated\n2. Check if `fly.toml` exists\n3. Run deployment:\n\n```bash\n# Standard deploy\nfly deploy\n\n# Without cache\nfly deploy --no-cache\n```\n\n4. Report deployment status and URL\n\n### For `secrets list`:\n\n1. Run `fly secrets list`\n2. Display secret names (values are hidden by Fly.io)\n\n### For `secrets sync`:\n\n1. Check if `.env.local` or `.env.production` exists\n2. Use the Fly secrets provider:\n\n```python\nfrom lib.vibe.secrets.providers.fly import FlySecretsProvider\n\nprovider = FlySecretsProvider(app_name=\"app-name-from-fly-toml\")\nresults = provider.sync_from_local(\".env.local\", \"production\")\nprovider.deploy() # Deploy the staged secrets\n```\n\n3. Report success/failure for each secret\n\n### For `secrets set`:\n\n1. Parse KEY=value from arguments\n2. Run `fly secrets set KEY=value`\n3. Report success\n\n### For `logs`:\n\n```bash\n# Stream logs\nfly logs\n\n# Recent logs only\nfly logs --no-tail\n```\n\n### For `status`:\n\n1. Run `fly status` for app overview\n2. Run `fly machine list` for machine details\n3. Report app URL, machine status, regions\n\n### For `ssh`:\n\n```bash\n# Interactive\nfly ssh console\n\n# Command\nfly ssh console -C \"command\"\n```\n\n## Example Session\n\n```\nUser: /fly deploy\n\nClaude: I'll deploy to Fly.io.\n\nChecking prerequisites...\n✓ Fly CLI authenticated\n✓ fly.toml found (app: my-app)\n\nDeploying...\n\n✓ Deployment complete!\n\nApp URL: https://my-app.fly.dev\nMachines: 2 running in iad\nVersion: v42\n```\n\n## Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| Not authenticated | Run `fly auth login` |\n| No fly.toml | Run `fly launch` to create |\n| Build failed | Check Dockerfile and logs |\n| Health check failing | Verify /health endpoint |\n| Out of memory | Increase `memory_mb` in fly.toml |\n\n## Related\n\n- `recipes/deployment/fly-io.md` - Full Fly.io documentation\n- `recipes/security/secret-management.md` - Secrets handling", "variables": [], "notes": "Deploy and manage Fly.io applications Tools: Bash, Read, Write.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/kevin-earl-denny/city-doodle", "path": ".claude/commands/fly.md", "ref": "4fdbfe2335d62405aea8c499c2faa3e26c4ea0a7", "url": "https://github.com/kevin-earl-denny/city-doodle/blob/4fdbfe2335d62405aea8c499c2faa3e26c4ea0a7/.claude/commands/fly.md", "key": "kevin-earl-denny/city-doodle/.claude/commands/fly.md" } } }

fly

About

/fly - Fly.io Deployment Management

Subcommands

deploy

secrets

logs

status

ssh

Instructions

For `deploy`:

For `secrets list`:

For `secrets sync`:

For `secrets set`:

For `logs`:

For `status`:

For `ssh`:

Example Session

Common Issues

Related

Install fly and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

/fly - Fly.io Deployment Management

Subcommands

deploy

secrets

logs

status

ssh

Instructions

For deploy:

For secrets list:

For secrets sync:

For secrets set:

For logs:

For status:

For ssh:

Example Session

Common Issues

Related

Install fly and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

For `deploy`:

For `secrets list`:

For `secrets sync`:

For `secrets set`:

For `logs`:

For `status`:

For `ssh`: