Autonomous AI Software Engineering Agents·v2.4

Build from
anywhere.

An asynchronous mobile gateway that converts developer intent into production repository-level code commits using persistent cloud AI agents.

Connection Independent
Redis Queue
Docker Sandbox
01
Mobile Control
Intent Generation & Approvals
02
Async Gateway
Redis Queue & Job State
03
AI Runtime
Sandbox Execute & Push
Git RepositoryCI/CD PipelineDeploymentMobile Notification
The Problem

AI coding agents are powerful.Their interfaces are still desktop-first.

01

Desktop Dependency

Most agentic development workflows assume a persistent desktop, terminal, IDE, and local development environment.

02

Mobile Constraints

Traditional IDEs become difficult to operate on small, touch-based mobile interfaces.

03

Network Instability

Remote desktop and continuous browser sessions degrade when mobile connectivity becomes unstable.

The core limitation isn't compute.

It's access.

Research Gap

The Resource Interface Duality

The best device for interacting with an AI agent is not necessarily the best device for executing its work.

Interface Plane

Mobile Device

Intent generationExcellent
ApprovalsExcellent
MonitoringExcellent
Large IDE workloadsLimited
Execution Plane

Cloud Runtime

Repository operationsExcellent
AI agentsExcellent
Build & testingExcellent
Direct interactionIndirect
Proposed principle
Separate intent from execution.
Proposed Solution

One gateway. Four core responsibilities.

Core Capability

Asynchronous Execution

Requests become persistent Redis jobs. The mobile browser does not need to remain connected while an AI agent works autonomously on the cloud host.

01 · REQUEST
02 · QUEUE
03 · EXECUTE
04 · REPORT
RUN
TASK-JOB-8942
Admin Analytics Dashboard Hotfix
ACTIVE WORKER
Runtime
ONLINE

Persistent AI Runtime

The cloud executor remains available 24/7 independently of the developer's workstation or smartphone connection.

24/7
PM2 Background Daemon
Uptime 99.9%
Repository Native

Work directly with Git.

Native version control workflow without exposing local uncommitted state.

Git CloneCheckout BranchLLM Code EditLocal BuildTest CheckGit Push
Mobile First

Control plane, zero editing.

High-level intent inputs optimized for touch viewports.

Intent Prompting
Clerk / OAuth Login
Live Terminal Logs
WhatsApp Alerts
System Architecture

Three independent layers.

Interaction, orchestration, and execution remain logically separated.

MOBILE CONTROL PLANE

Developer interaction without a mobile IDE.

The mobile client focuses on repository selection, high-level prompts, approvals, task monitoring, logs, and deployment state. Heavy development operations never execute on the phone.

From Start To Finish

What actually happens?

9-Stage Interactive Workflow
Phase Index
01
Step 1 of 9

Mobile Prompt Capture & Intent Parsing

Client Interaction Layer

The developer submits a high-level intent prompt from any mobile browser. The request is structured into a normalized JSON payload containing repository target, branch name, prompt directives, and authorization signatures without triggering local compilation.

Mobile Web UIHTTPS Post
Architectural Comparison

Why not just use Remote Desktop?

Capability Matrix
Async GatewayPROPOSED
Cloud IDE
Remote Desktop
Mobile-first interaction
Native Control
~ Partial / Heavy
Touch Weak
Connection-independent execution
Persistent Jobs
~ Varies by host
Requires Stream
Background long-running tasks
Cloud Workers
~ Supported
Session Locked
AI-native agent orchestration
Core Design
~ Plugin Based
External Tool
Repository automation & push
Automated Git
~ Available
Manual Terminal
Interactive Scenario

From one mobile prompt to production.

DEVELOPER PROMPT

“Add an analytics dashboard to the admin panel using Tailwind and the project's existing data hooks.”

gateway.log
15:42:01 Request received
15:42:01 Repository access verified
Task created: TASK-4821
STATUS QUEUED
Fault Tolerance

What happens when the phone disconnects?

Nothing happens to the execution job. The phone acts as a control interface, not the runtime. When connectivity returns, the client retrieves the latest persisted task state seamlessly.

Mobile Client
Network unavailable
OFFLINE
Gateway
Task state persisted
ONLINE
AI Worker
Processing TASK-4821
EXECUTING
Repository
Workspace available
CONNECTED
Security Model

Automation without sacrificing control.

🔑

OAuth Authentication

Repository access is strictly linked to verified PKCE developer credentials.

Clerk / GitHub Auth
📦

Isolated Workspaces

Tasks execute inside ephemeral Docker containers without host exposure.

Docker Sandbox
🛡️

Secret Management

Sensitive API keys remain server-side and never reach the mobile browser.

Zero Expose

Approval Gates

High-impact branch pushes and deployments require explicit mobile confirmation.

Mobile Confirm
Technology Stack

Built as a system.

Production-grade tools powering client interaction, persistent orchestration, agentic AI, and continuous delivery.

Interface
Next.js 16Next.js 16
TypeScriptTypeScript
Tailwind CSSTailwind CSS
Database & Auth
Supabase BaaSSupabase BaaS
PostgreSQLPostgreSQL
GitHub OAuthGitHub OAuth
Queue & Runtime
Redis QueueRedis Queue
Node.js DaemonNode.js Daemon
Docker SandboxDocker Sandbox
AI BYOK Core
OpenRouter AIOpenRouter AI
Google GeminiGoogle Gemini
Anthropic ClaudeAnthropic Claude
DevOps & Alerts
Git EngineGit Engine
Vercel CI/CDVercel CI/CD
WhatsApp AlertsWhatsApp Alerts
Literature Review

Research foundation.

State-of-the-art foundation research powering autonomous multi-agent systems and cloud runtimes.

15+
Papers targeted
5
Domains
3
Core layers
Agentic AI & ACIs#1

SWE-agent: Agent-Computer Interfaces Enable Automated Software Engineering

John Yang et al. (NeurIPS / arXiv)

Introduces Agent-Computer Interfaces (ACIs) tailored for LLMs, demonstrating that simplified commands outperform raw terminal shell access.

arXiv:2405.15793Read
Software Benchmarks#2

SWE-bench: Can Language Models Resolve Real-World GitHub Issues?

Carlos E. Jimenez et al. (ICLR / arXiv)

Defines the standard benchmark suite for evaluating repository-level issue resolution using real GitHub pull requests.

arXiv:2310.06770Read
Agent Platforms#3

OpenHands: An Open Platform for AI Software Developers as Generalist Agents

Xingyao Wang et al. (ICLR / arXiv)

Proposes an open platform for autonomous software agents executing inside sandboxed container runtimes.

arXiv:2407.16741Read
Multi-Agent Systems#4

MetaGPT: Meta Programming for A Multi-Agent Collaborative Framework

Sirui Hong et al. (NeurIPS / arXiv)

Encodes Standard Operating Procedures (SOPs) into multi-agent prompt flows to generate structured code outputs.

arXiv:2308.00352Read
Communicative Agents#5

ChatDev: Communicative Agents for Software Development

Chen Qian et al. (arXiv)

Demonstrates multi-agent chat chains for collaborative software design, coding, and automated debugging.

arXiv:2307.07924Read
Agent Runtimes#6

SWE-World: Docker-Free Execution Environments for Agent Evaluation

Yuxiang Wei et al. (arXiv)

Develops surrogate execution feedback models to eliminate container instantiation overhead during evaluation loops.

arXiv:2602.03419Read
Issue Resolution#7

SWE-Adept: Agentic Traversal and Structured Resolution for Repository Issues

Anonymous Authors (arXiv)

Proposes depth-first dependency traversal and shared memory checkpoints for precise issue localization.

arXiv:2603.01327Read
Trajectory Distillation#8

Open-SWE-Traces: Advancing Dual-Mode Distillation for Software Agents

Wasi Uddin Ahmad et al. (arXiv)

Releases expansive multi-language agentic trajectory datasets for fine-tuning long-horizon software reasoning.

arXiv:2606.16038Read
Software Evolution#9

SWE-EVO: Benchmarking Autonomous Software Evolution

Anonymous Authors (arXiv)

Evaluates multi-step release-sized software modifications across large versioned Python codebases.

arXiv:2512.18470Read
Code Auditing#10

RepoAudit: Autonomous LLM-Agent for Repository-Level Code Auditing

Anonymous Authors (ICML)

Explores autonomous code auditing, static analysis, and bug detection in large repository structures.

arXiv:2508.17343Read
Cloud Architecture#11

Microservices-Based Scalable Architectures for AI-Driven Systems in Cloud

Researchgate Publication

Establishes design patterns for decoupling AI inference services using microservices and Redis caching.

ResearchGate-404321670Read
Mobile Cloud#12

Lightweight Mobile Cloud Computing Environment for Mobile Applications

Sarvesh Rai et al. (ResearchGate)

Investigates resource offloading frameworks from mobile terminals to cloud-assisted backend gateways.

ResearchGate-339723782Read
Cloud Scheduling#13

Workflow Management and Scheduling in a Cloud Computing Context

Zacharie Brodard (KTH / DiVA)

Evaluates asynchronous message queues and elastic computing for workflow scheduling and batch processing.

DiVA-2:1305761Read
Real-Time Protocols#14

Real-Time Collaboration Architecture via WebSocket Protocols

IJERT Publication

Details persistent, low-latency WebSocket connection handling for real-time bidirectional data exchange.

IJERT-WhiteboardRead
Async Messaging#15

Microservices Best Practices and Asynchronous Communication

Microservice Study Group (arXiv)

Compares synchronous HTTP REST vs. asynchronous message queue protocols in distributed cloud gateways.

arXiv:2212.11758Read
Implementation Strategy

12 weeks from concept to validation.

Four structured phases delivering infrastructure, real-time transport, agentic execution, and empirical testing.

01
WEEKS 01–03

Foundation

Core Auth & Cloud Infra
Clerk PKCE Authentication
Cloud Infrastructure
Redis Queue Architecture
02
WEEKS 04–06

Communication

Real-Time State Sync
WebSocket Stream Protocol
Persistent Task State
Mobile PWA Control
03
WEEKS 07–09

Intelligence

LLM Agent & Sandbox
Autonomous Agent Runtime
Isolated Git Sandbox
Automated Verification
04
WEEKS 10–12

Validation

CI/CD & Benchmarking
Automated CI/CD Webhooks
Security Audit & Linters
Benchmark Report & Docs
Project Evaluation

How will we know it actually works?

The project is evaluated using measurable system outcomes and objective benchmark metrics, not only a manual demonstration.

01
Task Completion Rate
Target: > 92% end-to-end pass
02
Queue Latency
Sub-second Redis push & dispatch
03
Build Success Rate
Isolated Sandbox verification
04
Reconnect Recovery
State sync after network drops
05
Execution Time
Parallel LLM worker dispatch
06
Change Accuracy
Repo diff validation & linting
Asynchronous Mobile Gateway

Development shouldn't stopwhen the laptop closes.

A mobile-first control plane for persistent AI software engineering agents — review diffs, approve pushes, and monitor builds anytime, anywhere.

Star on GitHub ★
Connection IndependentRedis Persistent QueueDocker Security Sandbox