Drive Claude Code on your desktop, approve its commands from your phone, and push builds to TestFlight and your device — without opening your laptop.
Every other "control your coding agent from your phone" app treats the phone as a remote control. For a mobile developer, it's also the device the app runs on. Forge closes that loop.
Claude Code reads, edits, and runs commands in the project already open on your desktop.
Commands and file edits wait for your sign-off. Approve with Face ID, or deny straight from the lock screen.
Forge builds the app and pushes it to TestFlight, Firebase App Distribution, or a USB-connected Android device.
A push tells you the build's ready. Install it, test it on the phone in your hand, and tell the agent what to fix.
Most "control your coding agent from your phone" apps stop at streaming output and approvals. Forge adds the mobile release loop on top — build detection, TestFlight and App Distribution shipping, USB installs, diff review, scheduled runs, and spend caps — so the phone that approves the code is also the phone that tests it.
Watch every tool call, file edit, and token land in real time, straight from your desktop's session.
Deny right from the notification, or tap in and approve with Face ID — with a countdown before it auto-denies.
Trust the commands you already trust and skip the prompt. High-risk commands always ask — no exceptions.
Review every file Claude touched, line by line, and revert any file if it goes sideways.
The full git loop from a six-inch screen: stage, commit, push, and open a pull request.
Forge recognizes Flutter, iOS (Xcode), Android (Gradle), and web projects and knows how to build each one.
Ship a new build straight to TestFlight, kicked off from your phone.
Push a build to testers the moment it's ready — no laptop required.
Plug an Android device into your desktop and install the latest build over ADB, triggered from your phone.
Simulator screenshots and a live preview, so you can see what's on screen without walking back to your desk.
Cron a nightly session against your codebase and wake up to a Slack summary of what changed.
Set a per-session budget. When a session crosses it, the app stops the run instead of just sending an alert.
From a cold terminal to approving commands from the couch, in about the time it takes to make coffee.
One command provisions your own Firebase project and sets up the relay — the data plane is yours from the first second.
Open the app, scan, done. The pairing key never leaves your two devices — no account handoff to a third-party server.
Leave it running — it keeps Claude Code, your build tools, and your phone connected while you work.
Forge Remote doesn't route through an Iron Forge Apps server, because we never built one. The relay on your desktop and the app on your phone talk directly to a Firebase project you create and control. That's the whole pipe.
Every session, prompt, diff, and build lives in the Firestore project you set up during init — under your billing, your rules.
We don't operate a database of your code. If our servers vanished tomorrow, your sessions would keep streaming.
Unpair a desktop from Settings in one tap. It's your Firebase project, so rotating keys, wiping data, or deleting it is up to you — no support ticket required.
"Can you see my code?" No. We didn't just promise that — we didn't build the pipes that would let us.
Scheduled runs execute on a real cron — nightly, weekly, or a custom schedule — and actually run your agent against your codebase. No simulation, no "coming soon."
Cost rules that don't just alert — they can stop a running session once it crosses your budget.
No tiers, no trial, no per-seat fee. Forge Remote runs entirely on the Firebase project you already control — you pay Google for usage, not us for a subscription.
Everything on this page — live streaming, approvals, diff review, builds, TestFlight and App Distribution shipping, scheduled runs, and spend caps — ships in the same free app.
No. The relay on your desktop and the app on your phone talk directly to a Firebase project you create — there's no Iron Forge Apps server in between. We couldn't read your code if we wanted to; we never built the pipe that would let us.
Claude Code. The whole loop — the approval prompts, the diff review, the auto-approve list — is built around its real permission model, not a generic wrapper around several tools.
Build detection covers Flutter, iOS (Xcode), Android (Gradle), and web projects today. TestFlight uploads go through fastlane; Firebase App Distribution goes through the Firebase CLI. React Native apps build through the same underlying Xcode and Gradle projects, so they work too — there's no dedicated React Native mode yet.
For iOS builds and TestFlight, yes — your desktop runs the actual build, and Xcode requires macOS. Android and web builds don't need a Mac.
Yes. Forge Remote has no paid tier. You bring your own Firebase project and pay Google directly for whatever usage you generate — which for most solo developers stays inside the free tier.
Pair your first desktop, approve your first diff, and get the next build pushed to the phone in your hand.