Run and steer supported Devin work from your iPhone.

Join the TestFlight beta · Download DevinX Connector · Local setup guide

TestFlight access does not include a Devin account or shared Devin data. Each tester connects their own Devin organization, pairs a local device they control, or uses both.

DevinX is mobile mission control for supported Devin Cloud and Devin for Terminal workflows. It is built for the moments when you are away from your desk but still need to start work, check progress, answer a question, or review a result.

• Start work remotely. Create supported Cloud or Local sessions with the context exposed by the selected destination.
• See sessions in one place. Cloud and Local sessions remain clearly labeled so their trust and data boundaries never blur.
• Keep work moving. Read bounded history, send steering messages, and respond when a session needs input.
• Review demos in place. Devin-produced Cloud screenshots and videos appear in the session when the documented attachment API returns them; videos load only after you tap play.
• Use the real available catalog. Repositories, workspaces, playbooks, Knowledge, attachments, modes, and models come from documented Cloud APIs or the live local ACP catalog—not hardcoded guesses.
• Speak detailed prompts. On supported iOS 26 devices, dictation is transcribed on device. The optional Organize prompt preview uses Apple Foundation Models when available and falls back to deterministic on-device formatting.
• Inspect supported product surfaces. Depending on account permissions, DevinX can expose Automations, Usage, Review, repository Wiki content, read-only integration/MCP status, and genuine code_scan Security Work.
• Keep a helpful companion nearby. The DevinX companion reflects session state without becoming an operating-system overlay or covering primary controls.

Cloud authentication does not pair a local device. Local pairing does not copy Devin credentials to the iPhone. Each connection has its own authentication, permissions, storage, and revocation path.

flowchart LR
    I["DevinX on iPhone"] -->|"Documented API over TLS"| C["Devin Cloud"]
    I -->|"Tailscale + pinned TLS + signed requests"| X["DevinX Connector"]
    X -->|"Bounded ACP operations"| T["Devin for Terminal"]

DevinX operates no relay for normal Cloud or Local session traffic.

1. Install Apple's TestFlight app.
2. Open the DevinX Early Access link.
3. Install Build 0.1.0 (77) and complete the in-app onboarding.
4. Choose Devin Cloud, Local, or Cloud + Local.

Cloud mode requires an existing Devin organization and a least-privilege service user created by that organization. Follow Devin's official service-user authentication guide, then enter the generated service-user key and organization ID only inside DevinX onboarding. The credential is validated directly against Devin and stored with device-only protection in iOS Keychain.

Do not paste Devin credentials into issues, screenshots, setup prompts, shell history, or chat messages. TestFlight does not provide a shared Devin credential, and no tester receives access to another user's sessions through the beta link.

Connector is optional. Cloud-only users do not install it.

• macOS 13 or later on Apple silicon
• Tailscale on the Mac and iPhone, signed into the same tailnet
• Devin for Terminal installed and authenticated on the Mac
• DevinX on the iPhone

1. Download the signed DMG and checksum from the latest official DevinX release.
2. Verify the checksum published with that release.
3. Open the DMG and move DevinX Connector to Applications.
4. Open Connector and confirm it detects both Tailscale and Devin for Terminal.
5. In DevinX, open Settings → Local devices → Add local device.
6. Scan the short-lived code and approve the named iPhone plus its requested permissions on the Mac.

The iPhone onboarding also includes a guarded assisted-setup prompt for an AI assistant on the Mac. It uses only the official signed release, verifies the published checksum, and stops when a release or trust check is unavailable. macOS still requires visible user approval; the iPhone app cannot and does not silently install a desktop application.

For detailed installation, update, uninstall, development, and notarization information, read docs/devinx-connector.md.

The native per-user Windows application, DPAPI-protected state helper, notification-area lifecycle, installer, deterministic uninstaller, pinned-runtime package, and automated Windows verification are implemented. Windows 11 x64 is an active release target.

The Local runtime is supported by Cognition's official Windows Devin CLI installer and documented devin acp subprocess. Connector still negotiates the installed CLI's actual ACP methods at runtime and fails closed rather than inventing unsupported controls. Cognition's separate Windows cloud-session environments are not the Connector runtime.

The unsigned EXE and ZIP artifacts produced by ordinary CI are deliberately marked NOT FOR RELEASE. The Store-signed Windows 11 x64 package is publicly installable from the Microsoft Store listing for controlled testing. It is still a public test track, not a completed support claim, until the clean physical matrix in spec 037 passes with the exact Store package. That matrix covers official Devin ACP discovery, Tailscale routing, pairing, read/send/create grants, AskUserQuestion, sleep/reconnect, update, and uninstall. Testers should follow the Windows Connector physical test checklist and must never sideload the unsigned CI artifacts.

Tailscale and Connector provide two separate required layers for Local mode:

1. Tailscale provides private network reachability between the iPhone and Mac.
2. Connector provides the trusted local service that talks to Devin for Terminal, authenticates each iPhone, enforces its permissions, and returns bounded results.

A Tailscale IP, server URL, or shared password is not a Devin session service. Without compatible software listening on the Mac, there is nothing for the phone to authenticate to or request sessions from. DevinX uses short-lived QR pairing so every phone gets its own cryptographic identity, permission set, and revocation path instead of sharing one reusable password.

Connector grants are per iPhone and enforced on the Mac:

• Read session titles and history
• Send messages to sessions
• Create new sessions

The Mac owner chooses these permissions during pairing and can revoke a phone later. The iPhone can request signed revocation while Connector is reachable. If the Mac is offline, DevinX offers an honest local-only removal instead of claiming the Mac-side grant was revoked.

Closing the Connector window leaves its visible menu-bar service running. Quit DevinX Connector stops it. Launch at login is an explicit user choice. Connector includes no root daemon, public tunnel, analytics SDK, or silent updater.

• Cloud service-user credentials stay in iOS Keychain with device-only protection.
• Local Devin credentials remain on the paired device and are never copied to the iPhone.
• Connector identity, TLS material, and paired-device grants stay in platform-protected storage.
• Every protected Connector request is authenticated, replay checked, rate limited, Zod validated, and authorized server-side. Unauthorized resource access receives a generic non-disclosing error.
• Local transport pins the Connector certificate and signs requests with a per-install iPhone key.
• Raw dictation audio is processed on device, is not uploaded by DevinX, and is not retained after transcription.
• Session content, transcripts, credentials, and QR payloads are excluded from analytics and logs.
• Disconnecting wipes credentials, protected caches, drafts, templates, and remembered session context from the iPhone.
• Version 1 ships no product-analytics, crash-reporting, or remote-push SDK.

Read the complete Privacy Policy, Security Policy, Authorization Matrix, and latest dependency audit. Report vulnerabilities through GitHub's private vulnerability reporting, never through a public issue containing sensitive details.

DevinX exposes only behavior supported by the authenticated account and a documented Cloud API, official Devin MCP tool, or approved local ACP capability.

• Cloud availability depends on organization tier and service-user permissions. Missing access is shown as unavailable; it is not bypassed with browser cookies, private endpoints, or human-account impersonation.
• Security Work opens genuine top-level sessions whose canonical origin is code_scan. It is not Cognition's enterprise findings dashboard and does not invent a scan-creation endpoint.
• Wiki and integration/MCP surfaces are read-only where the official Devin MCP exposes them.
• Local workspaces and models come from the live local catalog. Exact identifiers are preserved when dispatching work.
• Local tool approvals, arbitrary file access, arbitrary shell commands, public tunnels, and shared server passwords are outside the Connector grant model.
• Personal profile/OAuth settings, plan and invoice management, organization administration, and unsupported Web-only mutations remain owned by Devin Web.
• The initial mobile release is iPhone-only. Android and iPad are not supported. Connector 0.1.4 supports Apple-silicon Macs. Windows 11 x64 is an active release implementation whose public download activates only after its signature and physical compatibility gates pass; Linux and Intel Mac packages remain unavailable.

The maintained parity inventory is in specs/033-cloud-local-settings-parity.md.

• Node.js 24.18.0 (pinned in .nvmrc and package.json)
• Xcode and CocoaPods for native iOS builds
• macOS for Connector release checks
• Windows 11 x64 plus .NET 10 for Windows Connector verification
• A configured Expo/EAS development environment

git clone https://github.com/fenner888/Devinx.git
cd Devinx
npm ci --legacy-peer-deps
npm run ci

Native voice, camera, Keychain, certificate-pinning, and pairing modules require a native development or TestFlight build. Expo Go is not the release test environment.

No package may be added until it is verified in the official registry, including its publication history, download history, and source repository. Dependencies are lockfile-enforced; never use a guessed package name.

src/app/                 Expo Router screens
src/components/          UI and interaction components
src/api/devin/           Cloud API and MCP clients, Zod schemas, endpoint contracts
src/auth/                Keychain credentials and connection providers
src/lib/                 Product rules, voice, polling, diagnostics, and utilities
src/cache/               Protected Cloud read cache
modules/                 Reviewed native iOS modules
bridge/                  Authenticated local Connector service
connector/macos/         Native macOS application
connector/windows/       Native Windows application
connector/windows-installer/ Per-user Windows installer and uninstaller
specs/                   Product and security source of truth
docs/                    Setup, parity, threat-model, and release evidence
tests/                   Unit, integration, security, and UI contract tests

Start with the Build Specification, Connector Guide, Authorization Matrix, and AGENTS.md.

The specification is the source of truth. Update the relevant spec before changing a supported product or trust boundary. Contributions must preserve:

• server-side authorization for every protected route;
• Zod validation at every external input boundary;
• generic 404 non-disclosure for unauthorized resources;
• rate limits on authentication and write paths;
• Keychain or secure-store credential handling;
• no hardcoded secrets or auth tokens in browser storage;
• verified, lockfile-enforced dependencies; and
• dependency, secret, authorization/IDOR, dead-code, artifact, and physical-device release gates.

Before opening a pull request:

npm run ci
git diff --check

Use public issues for ordinary bugs and feature requests. Never include credentials, QR payloads, private session content, repository secrets, or exploit details.

• Open a bug or feature request
• Report a vulnerability privately
• Read the privacy policy
• View DevinX releases

Original DevinX software and documentation are available under the MIT License. See NOTICE for third-party dependencies, names, model-provider marks, screenshots, reference material, and trademark boundaries.

The MIT License does not grant permission to use the DevinX name or branding as a trademark or to imply affiliation with Cognition AI, Devin, or any model provider.