Repository navigation
Conversation
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
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.
Adds the Fly.io plugin to the Factory marketplace. It provides Fly.io resource operations through the hosted Fly MCP server and skills for persistent Sprite development: remote tests, checkpoints, authenticated previews, verified patch export, and resuming a workspace.
The contribution includes the native plugin, its marketplace entry, the
flyandbrandskill links required by catalog CI, and a README entry. The package is version 1.0.1 from superfly/fly-droid-plugin.The plugin uses browser OAuth at
https://mcp.fly.io, contains no credentials, and runs no local MCP server. Live use requires Factory model access and a Fly.io account; Python 3 enables the confirmation hooks. Local deployments additionally use flyctl. Resource creation can incur Fly.io charges.Validation:
flyskill and calledget_fly_contextsuccessfully without changing resources.Reviewer walkthrough: install
fly@factory-pluginsfrom this PR's marketplace, complete Fly OAuth withdroid mcp auth, then ask Droid to use the Fly skill to inspect the authorized context. The plugin guide includes prerequisites and example prompts. No credentials or access to our test resources are needed; reviewers use their own Factory and Fly accounts.Generated by Codex.