Abstract
Released May 6, 2026, TRAE SOLO Mobile is a cross-platform mobile client built for the TRAE SOLO desktop AI coding engine, launching simultaneously on iOS App Store and Android Google Play with zero invitation code required for free download. The core differentiated capability of this mobile app lies in cross-device continuous task scheduling: users can voice-record vague requirement outlines on mobile during commutes, meetings or downtime, and the system converts unstructured speech into structured engineering plans. Heavyweight code generation, testing and build workloads are offloaded to paired desktop TRAE instances or cloud endpoints, with finished deliverables synced back to the mobile device for review. Two core operational modes (Code Mode for engineers, MTC Mode for product, design and finance staff) cover full development lifecycle scenarios. This guide retains all workflow scripts, scenario case data, regional version differences and competitor comparison metrics from the original document, restructured into standardized technical prose. Teams managing unified multi-model LLM traffic may integrate Treerouter as a centralized API gateway to synchronize custom model configuration across desktop and mobile SOLO deployments.
1. Core Foundational Facts About SOLO Mobile
Three critical defining attributes distinguish SOLO Mobile from standalone mobile AI chat applications:
- Not an independent isolated product SOLO Mobile functions purely as a lightweight remote control entry point, sharing identical workspaces, task queues and conversation context with TRAE SOLO web and desktop clients. No separate environment or account isolation exists between mobile and desktop instances.
- Mobile acts as a scheduler, not a heavy inference runtime The mobile client’s exclusive responsibility is requirement input, task triggering, progress monitoring and result review. All resource-intensive compute tasks (code generation, multi-step agent execution, large-file parsing) run on paired desktop machines or cloud backend servers, eliminating mobile hardware memory and compute bottlenecks.
- Dual-audience dual-mode architecture Two dedicated operating modes target distinct user groups: Code Mode built for full-stack developers handling code editing, refactoring and debugging; MTC (Multi-Task Context) Mode designed for non-technical stakeholders including product managers, data analysts, UI designers, legal and finance staff to process documentation, spreadsheets and business reports.
The core value proposition of SOLO Mobile is cross-device continuity: users capture vague real-time ideas via voice input anywhere, the AI formalizes structured engineering plans automatically, and upon reaching the office desktop, most implementation work is already pre-completed for review and final delivery. The official product tagline summarizes this positioning: Think Anytime, Ship Everywhere.
2. Code Mode vs MTC Mode: Mode Selection Framework
A clear dimensional comparison clarifies use cases, input/output formats and underlying foundation models for both operating modes:
| Evaluation Dimension | Code Mode (Developer-Focused) | MTC Mode (Multi-Task Context, Non-Engineering) |
|---|---|---|
| Target User Group | Full-stack engineers, backend/frontend developers, QA engineers | Product managers, analysts, UI/UX designers, legal, finance, operations |
| Supported Input Types | Natural language coding prompts, bug descriptions, local file uploads (code snippets, design assets) | Text notes, meeting audio transcription, CSV/Excel data tables, document uploads, survey raw data |
| Standard Output Deliverables | Executable project code, migration scripts, unit test suites, refactored modules | Structured Word/PPT reports, visualized data charts, standardized requirement change documents, formatted business summaries |
| Underlying Base Model | Claude 4 Sonnet (International Edition) | Claude 4 Sonnet (International Edition) |
| Representative Production Scenario | "Add a paginated user list API endpoint for our SaaS backend" | "Consolidate this batch of user feedback into a prioritized visualization report for the leadership team" |
Selection rule of thumb: Activate Code Mode for any task requiring source code generation or modification; switch to MTC Mode for document sorting, data analysis, meeting note consolidation and business report drafting. Users can toggle freely between the two modes within one shared SOLO workspace without re-authenticating or resetting context state.
3. Installation & Initial Device Pairing (5-Minute Full Setup Flow)
3.1 Brainstorm Voice Task Creation Workflow
This flow is optimized for unplanned idea capture during commutes, meeting intervals or before sleep, eliminating the need for fully polished requirement drafts before triggering AI pipelines. Step-by-step operation sequence:
- Open the SOLO Mobile application, tap the bottom floating "+" button to initialize a new task session
- Select Brainstorm Mode from the mode selector panel
- Tap the microphone icon to record natural voice requirements; full Chinese speech recognition is natively supported
- Wait 10–30 seconds for the AI to transcribe audio and generate a structured phased implementation plan
- Edit, delete or reorder individual task steps directly on mobile to correct AI misinterpretations
- Tap either "Dispatch to Desktop for Execution" or "Run Locally on Mobile" to launch the full workflow
Sample voice input prompt for a SaaS backend engineering task: "Build a usage statistics dashboard for our SaaS platform. Users need to view their daily API call volume, with built-in charts and one-click CSV export functionality."
Sample AI structured phased plan output:
- Core objective: Develop a user-specific API usage statistics dashboard module
- Phase 1 data layer: Design a dedicated
usage_logsdatabase table schema - Phase 2 backend logic: Implement an API endpoint
/api/usage?user_id=&date_range= - Phase 3 frontend visualization: Integrate Recharts line chart components
- Phase 4 permission control: Restrict data visibility to the authenticated user only
- Phase 5 export feature: Add CSV file download logic
- Estimated total implementation cycle: 1.5 working days
Key operational note: Brainstorm Mode never executes full code generation natively on mobile; it only outputs editable planning outlines, allowing users to refine scope before dispatching heavy compute workloads to desktop endpoints.
3.2 Mobile Dispatch Cross-Device Scheduling Core Logic
The core architectural principle of Mobile Dispatch separates lightweight orchestration from heavy inference: mobile handles task submission and monitoring, paired desktop TRAE clients or cloud backends process all resource-heavy build, test and code generation steps, with real-time progress and finished result push notifications sent back to the mobile device.
End-to-end cross-device execution chain:
- User opens SOLO Mobile at any location and enters natural language task requirements
- Tap "Dispatch Task to Paired Desktop Instance" to submit the request to the shared workspace queue
- Mobile UI displays real-time status: "Task queued for desktop execution"
- The continuously running desktop TRAE client automatically pulls pending tasks from the synchronized workspace
- Desktop runtime executes the full pipeline: Plan parsing → Code generation → Unit testing → Build validation
- Upon full completion, a push notification is sent to the mobile device containing full project deliverables and diff summaries
Recommended deployment practice: Leave the desktop TRAE client running persistently in the background without active human supervision; the desktop machine operates as a dedicated on-demand AI build server responding to all mobile-dispatched tasks.
3.3 Multi-Task Parallel Workspace Management
SOLO Mobile inherits the desktop client’s multi-session isolation capability: users maintain multiple fully independent task pipelines simultaneously on mobile, each with isolated conversation context and separate execution queues with no cross-task state leakage. Methods to initialize additional parallel tasks:
- Tap the "New Task" button at the top of the left-hand task sidebar panel
- Pull down the task list page to trigger a refresh and open a new blank session
Typical parallel multi-task production example:
- Task A (MTC Mode): Analyze competitor product documentation from meeting recordings
- Task B (Code Mode): Dispatch a backend API development build task to the desktop instance Both pipelines run asynchronously, with independent context memory and separate notification triggers upon completion.
3.4 Local File Upload Context Attachment
SOLO Mobile supports uploading local mobile files as supplementary context input for task pipelines, with standardized format support mapped to distinct engineering use cases:
| File Format Category | Supported Extensions | Core Workload Application |
|---|---|---|
| Document Files | .docx, .pdf | Upload requirement specification docs for AI parsing and implementation planning |
| Data Spreadsheets | .csv, .xlsx | Import raw business datasets to generate analysis charts and summary reports |
| Design Assets | .png, .jpg | Attach UI mockup screenshots for AI conversion into frontend component code |
| Source Code Files | Common script/programming extensions | Submit existing code snippets for review, refactoring or bug remediation |
Upload operation flow: Tap the attachment icon at the bottom of the task dialogue panel, select assets from local photo galleries or device storage, and attach the file as permanent context for the current AI task session.
4. Three Real-World End-to-End Production Scenario Demonstrations
Scenario 1: Backend Developer Commute Requirement Planning
User profile: Full-time backend developer with a 40-minute daily train commute End-to-end timeline workflow:
- 8:00 AM Train commute: Open SOLO Mobile Brainstorm Mode, voice-record database schema modification requirements; AI generates a structured migration task plan
- 8:05 AM Mobile operation: Review and validate the AI-generated plan, tap "Dispatch to Desktop Execution"
- Unsupervised desktop runtime: TRAE desktop automatically executes database migration scripts, model updates and logic testing while the developer travels to the office
- 9:00 AM Office arrival: Mobile push notification confirms task completion; open desktop SOLO client to review code diffs and approve pull requests
Core efficiency gain: All implementation work finishes during transit; office hours are reserved purely for code review and stakeholder alignment instead of manual drafting.
Scenario 2: Product Manager Real-Time Meeting Feedback Documentation
User profile: B2B SaaS product manager capturing live customer feedback during client sync meetings End-to-end timeline workflow:
- Live meeting (any time): Open SOLO Mobile MTC Mode, transcribe verbal customer pain points and feature requests via voice input
- Within 5 minutes post-meeting: Submit the consolidated meeting notes to MTC Mode, requesting standardized structured requirement change documentation with priority ranking
- Within 10 minutes: AI outputs fully formatted requirement change drafts ready for direct copy-paste into Confluence or engineering team communication channels
Sample structured AI output snippet for product requirement change logs:
- Document Version: Requirement Change v1.0
- Source Origin: Enterprise Client Feedback Sync (July 13)
- Core Change Type: Batch data export capability expansion
- High-Priority Request: Multi-row selection with one-click CSV download for frontend data tables
- Affected Systems: Frontend table UI + backend export API layer
- Stakeholder Priority Tier: P1 (High-Impact Customer Retention Feature)
Scenario 3: Independent Developer Off-Hours Multi-Product Parallel Scheduling
User profile: Freelance full-stack developer maintaining three separate SaaS client products End-to-end workflow:
- End of workday desktop session: Open SOLO Mobile and create three independent task pipelines outlining weekend feature deliverables for each product, dispatch all tasks to the desktop TRAE instance queue
- Weekend asynchronous execution: Desktop TRAE processes all three build pipelines sequentially without user supervision; mobile receives individual completion notifications for each product
- Monday office hours: Three finalized feature pull requests await review and sign-off
Key architectural advantage: The desktop client continues executing queued tasks even after the mobile app is fully closed, enabling developers to leverage off-hours time windows for AI-driven engineering work without continuous device supervision.
5. Regional Version Split: International vs Domestic China Edition Limitations
TRAE maintains two separated product deployments at distinct domain endpoints with divergent model support, network prerequisites and functional parity: trae.ai (Global International Edition) and trae.cn (Mainland China Domestic Edition). A side-by-side comparison of core differences:
| Evaluation Dimension | Global Edition (trae.ai) | Domestic China Edition (trae.cn) |
|---|---|---|
| SOLO Mobile Availability | Fully launched with complete feature set | Feature rollout delayed; check official site for real-time status |
| Foundation Model Backend | Claude 4 Sonnet | ByteDance Doubao, DeepSeek and domestic open-source LLMs |
| Network Access Requirement | Stable international network connectivity | Domestic mainland internet access with no cross-border routing required |
| Data Compliance Framework | Anthropic global privacy policy | Localized mainland data security compliance standards |
Official user operation guidance for regional deployments:
- Domestic China users must first verify
trae.cnofficial announcements to confirm full SOLO Mobile feature rollout - Global edition users require consistent cross-border network connectivity for mobile-cloud synchronization
- MTC Mode workflow implementation differs slightly between regional builds; follow in-app UI instructions as source of truth
6. Competitive Differentiation Benchmark
This matrix contrasts SOLO Mobile against competing mobile AI development tools including Cursor (no native mobile client) and the official Claude mobile chat application:
| Comparison Dimension | TRAE SOLO Mobile | Cursor Mobile (Third-Party Workaround Only) | Official Claude Mobile App |
|---|---|---|---|
| Core Product Positioning | Native mobile orchestration entry for full AI code delivery pipelines | No official native mobile application available | Standalone conversational chat client with no code execution backend |
| Cross-Device Code Execution | Full Mobile Dispatch remote desktop task triggering | Requires unsupported third-party middleware hacks | Cannot execute any production code generation tasks locally or remotely |
| Multi-Task Parallel Isolation | Natively supported with independent context queues | No built-in parallel session capability | Single continuous conversation thread only |
| Non-Technical User Support | Dedicated MTC Mode optimized for product/design/finance stakeholders | Exclusively built for software engineers | Generic general-purpose chat with no workflow specialization |
| Mainland China Network Compatibility | Global edition needs cross-border network; domestic regional mirror available | Requires complex network configuration | Claude.ai regional access restrictions apply |
Unique market differentiator: SOLO Mobile is one of very few mobile AI development platforms offering a complete end-to-end pipeline: requirement capture → remote task dispatch → desktop heavyweight execution → mobile result review delivery via the proprietary Mobile Dispatch cross-device scheduling engine.
7. Frequently Asked Technical FAQ
Q1: Is SOLO Mobile completely free to use?
The mobile application download itself carries no upfront cost. Usage is metered via fast request token quotas under tiered subscription plans: the free baseline plan includes a daily limited token allocation, while Pro/Ultra paid tiers unlock expanded concurrent task limits and higher throughput caps. Full pricing documentation is published at trae.ai/pricing; first-time SOLO Code users receive a one-time 200 fast-request bonus quota.
Q2: Does Brainstorm Mode support Chinese voice input transcription?
Yes. SOLO Mobile integrates native device-level speech recognition paired with LLM semantic understanding, delivering high accuracy for Mandarin voice prompt capture and structured plan generation.
Q3: Will desktop-dispatched tasks continue running after closing the mobile app?
All queued execution pipelines persist on the desktop TRAE runtime independently of mobile client state. The desktop instance will finish all assigned build, test and generation workflows regardless of whether the mobile application is minimized or fully shut down.
Q4: Can SOLO Mobile integrate third-party custom LLM model endpoints?
SOLO Mobile inherits all custom model provider configurations set within the desktop TRAE client. If users have integrated self-hosted or third-party compatible LLM services via standardized OpenAI-compatible API schemas (or unified routing via Treerouter), mobile dispatched tasks will utilize the defined custom model endpoints. Note that custom model mobile-side compatibility varies by app build version; pre-validate model performance on the desktop client before mobile production scheduling.
Q5: Is SOLO Mobile officially launched for the domestic China regional build?
As of July 13, 2026, SOLO Mobile has fully launched for the global trae.ai international edition. Feature parity rollout for the domestic trae.cn deployment proceeds on a separate timeline; users must reference real-time official website announcements for the latest availability status.
8. Conclusion & Target Workload Matching Summary
SOLO Mobile fills a distinct market gap as a lightweight cross-device orchestration layer rather than a standalone code generation mobile runtime. The platform’s core competitive advantage stems from decoupling lightweight mobile requirement capture from resource-heavy desktop inference workloads, eliminating mobile hardware memory and compute constraints for complex engineering pipelines.
Unsuitable Workloads for SOLO Mobile
- Large-volume raw source code editing and full review natively on mobile hardware
- Complex heavyweight compilation or deep runtime debugging executed directly on mobile devices
- Teams requiring a fully self-contained offline mobile coding environment with no desktop dependency
Ideal Target Workloads for SOLO Mobile
- Voice-based unstructured requirement capture, automated structured plan formalization during off-hours transit or meetings
- Offloading resource-intensive code generation, refactoring and build pipelines to persistent desktop TRAE instances via Mobile Dispatch
- Maximizing overall engineering throughput by extending the development window to commutes, meetings and downtime outside traditional office hours
For distributed engineering teams operating mixed regional model deployments and cross-device task scheduling, unified API routing platforms such as Treerouter streamline consistent custom LLM configuration sync between desktop TRAE runtimes and mobile SOLO clients, standardizing endpoint access without repetitive per-device configuration edits. As frontier AI coding agent workloads grow increasingly resource-intensive, cross-device split architectures like SOLO Mobile’s mobile scheduler + desktop heavy execution paradigm will become the baseline standard for scalable enterprise AI software development workflows.
