<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pascal</title>
    <description>The latest articles on DEV Community by Pascal (@mcpasi).</description>
    <link>https://dev.to/mcpasi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4076860%2F624d2ea4-999e-44fb-ab03-894b416a4f47.jpg</url>
      <title>DEV Community: Pascal</title>
      <link>https://dev.to/mcpasi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mcpasi"/>
    <language>en</language>
    <item>
      <title>I Built a Native Codex Development Environment for Android</title>
      <dc:creator>Pascal</dc:creator>
      <pubDate>Fri, 04 Sep 2026 16:35:50 +0000</pubDate>
      <link>https://dev.to/mcpasi/i-built-a-native-codex-development-environment-for-android-po9</link>
      <guid>https://dev.to/mcpasi/i-built-a-native-codex-development-environment-for-android-po9</guid>
      <description>&lt;p&gt;Most AI coding workflows on mobile still assume one thing:&lt;/p&gt;

&lt;p&gt;Somewhere, there is another computer doing the real work.&lt;/p&gt;

&lt;p&gt;I wanted to see how far I could push the opposite idea.&lt;/p&gt;

&lt;p&gt;What if the Android device itself hosted the workspace, terminal, development tools and Codex runtime?&lt;/p&gt;

&lt;p&gt;That became AGENTCODI.&lt;/p&gt;

&lt;p&gt;Codex workflows, directly on Android&lt;/p&gt;

&lt;p&gt;AGENTCODI is an open-source Android application built around the Codex app-server.&lt;/p&gt;

&lt;p&gt;The application interface is native Android, while the runtime, workspace and terminal run directly on the device.&lt;/p&gt;

&lt;p&gt;There is no Termux requirement, no WebView shell and no separate gateway that has to be configured first.&lt;/p&gt;

&lt;p&gt;You install the APK, authenticate with ChatGPT or an OpenAI API key, create a workspace and start working with Codex.&lt;/p&gt;

&lt;p&gt;The AI model itself still runs online, of course. The important difference is where the development environment lives.&lt;/p&gt;

&lt;p&gt;Your Android device is the machine Codex works on.&lt;/p&gt;

&lt;p&gt;What actually runs on the device?&lt;/p&gt;

&lt;p&gt;AGENTCODI currently includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Codex app-server&lt;/li&gt;
&lt;li&gt;A private project workspace&lt;/li&gt;
&lt;li&gt;An interactive terminal&lt;/li&gt;
&lt;li&gt;Node.js and npm&lt;/li&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;ripgrep&lt;/li&gt;
&lt;li&gt;File importing and exporting&lt;/li&gt;
&lt;li&gt;Workspace ZIP export&lt;/li&gt;
&lt;li&gt;Native approval dialogs&lt;/li&gt;
&lt;li&gt;MCP, tools, skills and app discovery&lt;/li&gt;
&lt;li&gt;GitHub and Gmail integration through hosted Codex apps&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can follow commands, plans, reasoning summaries, file changes and tool activity directly inside the conversation.&lt;/p&gt;

&lt;p&gt;The workspace can also be inspected manually at any time.&lt;/p&gt;

&lt;p&gt;So if Codex changes ten files, you are not staring at a chat message hoping everything went well. You can open the workspace and see the result yourself.&lt;/p&gt;

&lt;p&gt;Android changes the security model&lt;/p&gt;

&lt;p&gt;Giving an autonomous coding tool filesystem access on a phone deserves some thought.&lt;/p&gt;

&lt;p&gt;AGENTCODI therefore uses a private application workspace by default.&lt;/p&gt;

&lt;p&gt;In Protected Mode, Codex operates inside that workspace and supported actions can require explicit approval.&lt;/p&gt;

&lt;p&gt;There is also an experimental full-access compatibility mode for workflows that need fewer filesystem restrictions. Recent versions added optional approval handling there as well, so file and command changes can still require confirmation.&lt;/p&gt;

&lt;p&gt;Imports and exports go through Android's document picker, keeping access explicit.&lt;/p&gt;

&lt;p&gt;This is still Early Access&lt;/p&gt;

&lt;p&gt;The current release is AGENTCODI 0.6.11 for ARM64 devices running Android 10 or newer.&lt;/p&gt;

&lt;p&gt;The project is written primarily in Java and C++, and the packaged Codex app-server is currently version 0.148.1.&lt;/p&gt;

&lt;p&gt;For the 0.6.11 release, the test suites completed with:&lt;/p&gt;

&lt;p&gt;231 Java tests passed&lt;br&gt;
297 C++ tests passed&lt;/p&gt;

&lt;p&gt;The latest release also fixed Unicode backspace handling in the terminal and improved approval controls for the full-access workflow.&lt;/p&gt;

&lt;p&gt;There is still plenty I want to improve. Android is a very different environment from a normal Linux workstation, and building a reliable coding-agent runtime there has produced some wonderfully strange problems.&lt;/p&gt;

&lt;p&gt;That is also what makes the project interesting.&lt;/p&gt;

&lt;p&gt;Why build this?&lt;/p&gt;

&lt;p&gt;Phones and tablets have become extremely capable machines.&lt;/p&gt;

&lt;p&gt;Yet most developer tooling still treats them as viewers, remote controls or emergency terminals.&lt;/p&gt;

&lt;p&gt;AGENTCODI is an experiment in treating Android differently.&lt;/p&gt;

&lt;p&gt;A device with its own workspace, runtime, terminal and coding agent can become an actual development environment you carry around.&lt;/p&gt;

&lt;p&gt;And apparently I decided that getting Codex running natively on Android was a perfectly reasonable way to test that idea.&lt;/p&gt;

&lt;p&gt;The project is open source under Apache 2.0.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Mcpasi/AGENTCODI" rel="noopener noreferrer"&gt;https://github.com/Mcpasi/AGENTCODI&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback, bug reports and contributions are welcome.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>android</category>
      <category>programming</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
