Fly App

Overview

Publish packages, find releases, and deploy to production without leaving your coding agent.

Install the Fly App, sign in, and you’re ready. It detects your coding agent and your package managers and wires them up to Fly. Authentication, registry configuration, and credential routing run in the background. Talk to your coding agent.

Install it first. The other local interfaces depend on it.

What you can do

With the Fly App installed, your coding agent, terminal, and package managers can all talk to Fly:

Publish and find packages. Your npm publish, docker push, and pip install commands route through Fly as usual. Search later by content: “Find the release where I fixed the login bug.”
Ship and track from your coding agent. Ask your agent to release, deploy, and check what’s running. “Deploy the login fix to staging.” “Is it live in production?”
Agent context management. Conversations with your coding agent become Decision Records linked to the releases they shape. The why ships with the what.

Setup

Download the Fly App. Click to download at fly.jfrog.ai/home, or run from your terminal:

macOS

curl -fsSL https://fly.jfrog.ai/download/desktop | bash

Windows

powershell -c "irm https://fly.jfrog.ai/download/desktop | iex"

Sign up or sign in.
Walk through the onboarding. The Fly App connects your coding agent, detects your package managers, and shows you the Fly App menu.

Click the Fly App icon in your menu bar (macOS) or system tray (Windows) to open the menu. From here you can see what’s connected, toggle anything on or off, and check your account.

Coding agents

The Fly App scans for supported coding agents on your machine: Cursor, VS Code (Copilot), Claude Code, and OpenCode. Each one shows up in the menu with a toggle.

Toggle on the agent you use. The Fly App wires up Fly MCP and Fly skills behind the scenes, registers the config in the right place, and your agent picks up Fly’s tools automatically. No manual MCP setup. Talk to your agent.

Working across coding agents? Toggle on more than one. Pick your default from your profile.

Package managers

The Fly App scans for the package managers you have installed: npm, pip, Docker, Helm, Go, Maven, and others. Each one shows up in the menu with a toggle.

Toggle on the package managers you want to use with Fly. The Fly App reconfigures each one to route through your Fly Registry. Your everyday commands keep working as before: npm publish uploads to Fly, pip install pulls from Fly, go get resolves through Fly. No .npmrc edits, no manual login.

For Docker and Helm, include the Fly Registry path in your command. Authentication is handled in the background:

docker push <your-team>.jfrog.io/docker/my-image:tag
helm push my-chart.tgz oci://<your-team>.jfrog.io/helmoci

Toggle a package manager off any time to skip Fly for that one. Your other tools stay routed.

See Package Managers → for per-tool details.

Profile

Open the Profile to see your identity in Fly: your username, your team, and your Fly Registry subdomain. From here you can also switch your default coding agent, or check whether the Fly App is up to date.

Troubleshooting

Package manager not detected? The Fly App scans standard installation paths. If your tool is in a non-standard location, configure it manually using the Fly Client CLI bundled with the app: fly setup <package-manager>.

Coding agent not recognizing Fly? Make sure the coding agent connection is toggled on in the Fly App menu. If it is on but still not working, toggle it off and back on, then restart your coding agent. If the issue persists, restart the Fly App. Check that the Fly MCP config file exists for your agent:

Coding agent	Config file
Cursor	`.cursor/mcp.json`
VS Code (Copilot)	`Code/User/mcp.json`
Claude Code	`.claude.json`
OpenCode	`opencode.json`

Can’t find the Fly App? On macOS, look in the menu bar (no Dock icon). On Windows, check the system tray overflow area.

Need to log out? Open your user profile from the Fly App menu, then click log out.

Grabbing logs for support? Open your user profile from the Fly App menu and click Open Logs. You can also enable Debug Logging there for more detailed traces.

Need to sign in again? Restart the Fly App to re-trigger the sign-in flow.

Next steps

Coding agent → - The interface where you’ll work day to day
From Planning to Production → - The lifecycle, end to end
Where to Use Fly → - All the interfaces