AirCode Studio · AI app builder for Web, iOS & Android

Build it. Run it. Prove it works.

AirCode Studio brings your AI coding agent, projects, files, terminal, Git review, and live Web/iOS/Android applications into one workspace. Describe what you want to build, watch the agent implement it, run the real application, verify the result, and keep refining without leaving Studio.

Coming soon Read the Docs

Coming to macOS · Windows · Linux

AirCode Studio. The sidebar lists projects and their sessions. In the AcmeDashboard session the agent plans and builds a SaaS dashboard, runs it in the Web preview and tests it there; in SnakeGame it builds a snake game and launches it on the Android Emulator; in LumenLoop the start screen is refined message by message while the preview updates.

More than code generation

The agent doesn’t stop at the diff.

Most coding agents finish when they have edited the files.

AirCode Studio continues through the development loop: Plan → Build → Run → Check → Review

  1. 01

    Plan

    The agent understands the task and project.

  2. 02

    Build

    Files are edited and the actual project is built.

  3. 03

    Run

    Launch the application on Web, iOS, or Android.

  4. 04

    Check

    Interact with the application and verify the result.

  5. 05

    Review

    Inspect the diff, stage changes, and commit.

One task. One workspace. The complete development loop.

Web + iOS + Android

Build across platforms without leaving the conversation.

Switch between a browser, iOS Simulator, and Android Emulator while keeping the same project, agent session, files, terminal, and Git changes.

StopTest appSettings
http://127.0.0.1:5180Copy URLOpen in browser ↗

Build output

› Detected Vite · React · npm
› npm run dev -- --port 5180
  Local: http://127.0.0.1:5180/
✓ Preview attached

Run it in Studio’s browser preview

  • Automatic framework detection
  • Package-manager detection
  • Managed development servers
  • Interactive browser preview
Dev server runningPreview infoBuild output

Local native pipelines

Not just a web app inside a phone frame.

AirCode Studio works with existing native and cross-platform projects and orchestrates the local toolchains they already use.

  • Xcode projects

    Build, install, launch, capture screenshots, and inspect runtime output.

  • Gradle projects

    Build Android applications locally and launch them on an emulator.

  • Flutter

    Run the Flutter workflow with runtime logs and hot reload.

  • React Native

    Coordinate the native build with Metro.

  • Capacitor & Cordova

    Prepare and synchronize the native project before launch.

Studio orchestrates the real local development stack instead of hiding it.

Agent-driven verification

Your coding agent can test what it built.

AirCode Studio gives the agent controlled access to the running web application so it can verify behavior instead of assuming its code works.

AcmeDashboard

Test the sign-up flowArchive

Test sign-up: create an account and make sure it lands on the dashboard.

  1. Opening /signupnavigate
  2. Clicking “Create account”click
  3. Entering test datatype
  4. Submitting formsubmit
  5. Checking rendered resultcheck
  6. Capturing screenshotcapture
Verification passed6 of 6 steps · evidence saved

signup-result.png

  • Click UI elements
  • Type into forms
  • Submit interactions
  • Navigate between pages
  • Capture screenshots
  • Save verification evidence

Browser control runs through an origin-restricted local bridge.

Objective completion checks

“Code written” isn’t the same as “working.”

Build

Build passed

Studio checks the actual build process and exit status.

Checking…Build exited successfully

UI

UI rendered

Studio confirms that the application mounted visible content.

Checking…Visible application content detected

Runtime

Runtime clean

Studio checks for uncaught browser errors.

Checking…No uncaught errors detected

AirCode Studio uses observable runtime signals to help check whether a task actually reached a working state.

Git built into the workflow

Build with the agent. Review like a developer.

Add start screen, subtitle and best score

1 of 2 sections staged · resolve the conflict to commit

Msrc/screens/StartScreen.tsx+3 −1

@@ -14,6 +14,8 @@Staged

14 return (15 <section className="start">16 − <h1 className="title">Lumen Loop</h1>16 + <h1 className="title title--xl">Lumen<br />Loop</h1>17 + <p className="subtitle">One photon. Three orbits.</p>18 + <p className="subtitle">How long can you stay in the light?</p>19 <button className="start-run" onClick={onStart}>

Asrc/components/BestScore.tsx+18

@@ -0,0 +1,18 @@Not staged

1 +export function BestScore({ value }: { value: number }) {2 + return (3 + <div className="best" aria-label="Best score">4 + <strong>{String(value).padStart(5, "0")}</strong>

Csrc/game/config.tsConflict

@@ -7,5 +7,1 @@Conflict with main

7<<<<<<< main8export const RING_COUNT = 4;9=======10export const RING_COUNT = 3; // “Three orbits.”11>>>>>>> agent/start-screen
7 +export const RING_COUNT = 3; // “Three orbits.”
  • Review changes

    See exactly what the agent modified.

  • Stage selectively

    Stage individual sections rather than accepting an entire generated change.

  • Resolve conflicts

    Handle conflicts inside the same development workspace.

  • Commit

    Move verified work into Git without leaving Studio.

The running application, conversation, and code review stay connected — and you stay in control: review changes before you ship them.

Local session continuity

Close Studio. The work doesn’t disappear.

Agent execution belongs to AirCode Studio’s shared local service rather than the lifetime of a single UI window.

If Studio closes or restarts, it can reconnect to the existing session without resubmitting the task.

  • Draft persistence
  • Local history
  • Crash recovery
  • Session reconnection
  • Multiple sessions per project

Isolated local previews

Every project gets its own lane.

AirCode Studio manages preview processes per project instead of treating every development server as one global process.

Preview processes3 running
  • AcmeDashboardhttp://127.0.0.1:5173Copy URL
  • LumenLoophttp://127.0.0.1:5189/index.htmlCopy URL
  • RenewalDeskhttp://127.0.0.1:5190Copy URL
  • Isolated preview ports
  • Listener ownership checks
  • Automatic recovery
  • Protection against stopping unrelated processes

Your development workspace stays within reach.

  • AI Agent

    Streaming responses, progress, tool activity, image attachments, and interactive questions.

  • Projects

    Create projects or open existing local folders.

  • Sessions

    Run multiple sessions per project with rename and archive.

  • Files

    Browse and edit project files.

  • Terminal

    Full interactive multi-tab terminal.

  • Changes

    Review Git diffs and repository state.

  • Preview

    Run and interact with your application.

  • Models

    Select compatible AI models and providers.

From idea to verified change.

  1. Describe

    “Add authentication and create a responsive sign-in screen.”

  2. Agent builds

    Files change while Studio streams progress and tool activity.

  3. Studio runs

    The application launches on the selected target.

  4. Agent checks

    The agent interacts with the running application and captures evidence.

  5. You review

    Inspect the diff and running result side by side.

  6. Commit

    Stage the approved changes and commit.

Build with an agent that can see the result.

Bring the AI coding loop—from instruction to implementation to running application to reviewed change—into one native workspace.

Coming soon Explore the Docs

Coming to macOS · Windows · Linux