Skip to content

feat(mobile): ship a NeoCode-controlled NeoPi client for ADB installation #145

Open

Description

@PsychedelicShayna

Note

GPT-6 Astra on behalf of PsychedelicShayna

Contract

The mobile app already exists in apps/mobile. Make it a NeoCode-controlled client for the authoritative NeoPi runtime and provide a reproducible Android sideload/ADB distribution path independent of upstream Play Store auto-updates. Do not create a duplicate mobile codebase.

Acceptance

  • Mobile recognizes NeoPi and the supported session/configuration contracts, with explicit unsupported capabilities rather than silent no-ops.
  • Fork-controlled application identity/distribution prevents an upstream Play Store update from replacing this client or silently breaking compatibility.
  • Produce an actual installable APK and document/install it through ADB on an authorized target; no claim based only on compilation scaffolding.
  • Preserve existing user data and explicit connection settings during any identity/migration work.
  • Record native device proof and runtime compatibility; reuse shared client-runtime contracts.

#42 is an unrelated delivered highlighting repair. Mobile session entry points were deferred in #58/#49; this message authorizes advancing the native client. Do not touch the owner's device until its target is identified and authorized.

Owner's words (verbatim)

2026-10-22 owner dictation — contiguous excerpt

We'll want to fork The T3 code mobile app as well if it's not already in this repository somewhere, the mobile application is also very important. and needs to... It, it will require minor changes, it won't require much. It just needs to be made aware of the existence of this new harness, and it just needs to be under our control, like installed over ADB, and not installed over the Play Store. Because it updates itself and then makes itself incompatible, and it's a pain in the ass.

Complete unedited message: #125 . The owner's words take precedence over this summary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent: pendingReady for an out-of-the-loop (OTL) agent to pick upenhancementNew feature or requestpriority: p2Useful planned workspecThe issue is or contains an agreed implementation specification.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions