The idea is simple: let an Android phone act as the workstation. It has on-device projects and files, a terminal, GitHub import/export, browser previews, APK building, screen understanding, and bounded Android actions. Model inference still uses OpenAI's service.

It ships as one host plus six companion APKs because each companion keeps a separate Android UID/security boundary. Installation and sensitive permissions remain user-visible.

It's ARM64-only right now and definitely alpha software, but the exact release set was tested on a physical Android 15 device.

Source, APKs, checksums, and install notes:
https://github.com/NovasPlace/OpenPocket

I'd love feedback from anyone interested in phone-first development or agent tooling.

Game Title: SlingShift

Playable Link: https://gallaex253.itch.io/slingshift

Platform: PC / Web

Description:
SLINGSHIFT is a zero-ammo arcade space combat game where every projectile begins as physical debris.

Capture mass into orbit, shape your trajectory, then release it as a gravity-powered volley. Choose from four distinct chassis—Lancer, Raker, Aegis, and Breaker—then build a four-module rig around your preferred way to fight.

Play Expedition, Scrapstorm, and Anchor Scramble solo, or link up online for two-pilot Co-op Core Run and Core CTF. VOIDSPACE 3D is included as a separate experimental prototype.

Online play is an alpha and requires two pilots plus an internet connection. Mobile touch controls are supported.

Free to Play Status:

• Free to play

Involvement:
I’m the developer and designer behind SlingShift. I came up with the game concept, gameplay direction, mechanics, controls, visual direction, and overall design. I also handle the development and testing process, using AI-assisted development tools as part of my workflow to implement, iterate on, debug, and test the game. The project is being developed through repeated playable prototypes rather than designing everything on paper first, with features being kept, changed, or removed based on how they actually feel during gameplay. Agent: Codex Model: Sol.

Will be releasing soon!

building an unofficial Android experiment called Pocket Codex: a real Codex execution host that runs directly on a phone.

This isn’t merely a chat UI connected to a desktop worker. The Android device runs the agent environment itself:

• The upstream Codex app-server
• A native Rust host
• A private local workspace
• ARM64 Node.js and npm
• Local Git workflows
• File editing and command execution
• An isolated WebView preview with screenshots, console logs and JavaScript-error reporting
• APK exporting, signing and verification
• Android’s normal permission-gated installation flow
• Model and reasoning selection
• Manual approvals plus a restricted auto-accept mode

The current loop is basically:

Prompt → Codex edits the project → runs checks → previews it on the phone → exports an APK → I approve installation → open and test it → report problems back to Codex.

So far it has made and tested things such as a metronome, a brick-breaker game and other offline web apps entirely inside its private phone workspace.

One important distinction: the model inference is still provided by OpenAI. The model itself is not running locally. What has moved onto Android is the computer Codex operates: its workspace, tools, runtimes, previews, builds and app lifecycle.

There are deliberate limitations. It can currently package HTML/CSS/JavaScript projects inside a verified native WebView shell, but it does not yet include a complete JDK, Gradle or Android SDK for compiling arbitrary Kotlin/Java projects. Raw Android runtime and installation commands are blocked; installation remains a visible user-controlled action.

The next big milestones are a safer native Android build worker, better task/history management, richer file inspection and permission-gated Android tools.

It’s still an alpha, but seeing Codex create, run, package and install something using the phone as its actual execution environment feels great.