Architecture

The architecture section describes the bridge-first system design and the constraints that shape ReCursor’s mobile experience.

Bridge-first by design: ReCursor intentionally avoids cloud services. All communication between the mobile app and your development environment flows through a local bridge server you control.

Core concepts

System overview

The core component model: mobile app, bridge server, and Claude Code integration points.

Data flow

Message-level sequence diagrams showing how commands travel from mobile to desktop.

Bridge protocol

The HTTP/WebSocket protocol specification for bridge communication.

Data models

Core data structures: requests, responses, sessions, and repositories.

Project structure

Repository organization: Flutter app, bridge server, and documentation.

Design principles

Principle	Implementation
Local-first	Bridge runs on localhost, no cloud services required
Transparent	All data stays in your network boundary
Reversible	No persistent state changes without explicit approval
Observable	Full logging and monitoring of all bridge traffic

Navigation guide

• Start with System overview for the core component model
• Use Data flow when you need message-level sequence details
• Read Bridge protocol and Project structure for implementation-facing reference material