Mobile-first, accessible, provider-diverse Git repository integrations beyond GitHub

What variant of Codex are you using?

Not currently using a Codex variant. I am a ChatGPT Plus user on Android requesting mobile-first Codex access and cloud repository integration.

What feature would you like to see?

Mobile-first, accessible, provider-diverse Git repository integrations beyond GitHub

Summary

Please expand Codex/ChatGPT repository integration so users can work with cloud-hosted Git repositories directly from Android and iOS, without requiring a desktop development environment and without requiring GitHub as the hosting provider.

This is also an accessibility request. AI-assisted development tools such as Codex can make software development substantially more accessible to people with visual impairments and other disabilities by reducing the need to manually navigate complex development environments, command-line workflows, large codebases, and desktop-oriented tooling.

For some disabled developers, mobile devices already provide a familiar and highly configured accessibility environment. Requiring users to move to a desktop development environment in order to use the full capabilities of Codex can remove those accessibility advantages.

The core request therefore has three connected goals:

1. Mobile-first cloud repository access for Codex/ChatGPT.
2. Accessible development workflows that work well with mobile accessibility features and assistive technologies.
3. Provider-diverse Git hosting support, including GitLab, Forgejo/Codeberg, Gitea, and self-hosted instances where feasible.

GitHub should remain fully supported, but it should be one supported provider rather than the assumed home for all repository-aware Codex workflows.

Why mobile-first and accessibility matter

For users who primarily work from Android or iOS, local desktop-based Codex workflows are not an equivalent solution.

This is particularly important for developers with disabilities. I am visually impaired and primarily work from mobile devices. An AI-assisted tool such as Codex can provide an accessible bridge between my ideas and the technical complexity of building software. It can help me understand a codebase, make changes, diagnose problems, and manage a project without requiring me to manually perform every low-level development task.

A mobile-first Codex experience would allow me to work within the accessibility environment I already use rather than requiring a separate desktop development setup simply to access more capable coding workflows.

A mobile user should be able to connect a repository, grant access to selected repositories, ask Codex to inspect or modify code, propose changes, and create pull requests or merge requests where supported, directly from an accessible Android or iOS interface.

Cloud repository access is therefore more than a convenience. For some users, it is an accessibility feature that can make software development possible or substantially more practical.

Requested providers

• GitHub: Keep existing support.
• GitLab: Full repository integration, not only issue or merge-request metadata.
• Forgejo: Including Codeberg and other Forgejo hosts.
• Gitea: Where technically compatible or feasible.
• Self-hosted Git services: Where secure authentication and API access permit it.

Core requirements

1. Mobile-first access

• Android and iOS users should be able to use repository-aware Codex workflows directly.
• A desktop-only local environment should not be required.
• Core repository workflows should be available through an accessible mobile interface.

2. Accessibility

Mobile repository and Codex workflows should:

• Work well with Android and iOS screen readers and accessibility services.
• Avoid requiring a desktop-only environment for core repository workflows.
• Allow repository selection, permissions, code review, proposed changes, and approval from mobile.
• Present code changes and diffs in formats that remain understandable with assistive technology.
• Preserve access to the conversational AI interface as a primary way of navigating and working with a codebase.

3. Cloud repository read/write capability

This should include:

• Repository context.
• Code review and analysis.
• Proposed file changes.
• Commit or branch workflows where appropriate.
• Pull request or merge request creation where supported.

4. Per-repository permissions

Users should be able to explicitly choose which repositories Codex/ChatGPT can access. Access should be fine-grained rather than all-or-nothing.

5. Provider-neutral design

Repository integrations should treat Git hosting as an ecosystem rather than assuming GitHub is synonymous with Git.

User story

I am a visually impaired, mobile-first developer who primarily works from Android. I prefer Codeberg, which is based on Forgejo, for my open-source projects.

Codex is valuable to me partly because AI-assisted development can make programming more accessible. I can describe what I want to build, ask questions about the implementation, and receive help working with code that would be substantially more difficult for me to manage entirely through conventional development tools.

I want to be able to host my code on Codeberg and independently authorise Codex/ChatGPT to work with selected repositories from my mobile device. I should not need a desktop computer to access the most capable Codex workflows, and I should not need to mirror my project to GitHub simply because it is the supported repository provider.

Choosing to give an AI access to my code should be independent from choosing where my code is hosted. Accessibility should also not depend on owning or being able to comfortably use a desktop development environment.

My personal priority is accessible Codeberg/Forgejo development from Android, but this request is intentionally broader so mobile-first users, disabled developers, and users of GitLab, Forgejo, Codeberg, Gitea, and self-hosted Git services can all benefit.

Suggested approach

A provider-neutral Connect Git host system could support:

• OAuth or personal access token authentication per provider.
• Self-hosted base URLs where applicable.
• A common capability model for repository access.
• Per-repository selection and permissions.
• Mobile-friendly setup and use.
• Provider-specific pull request or merge request workflows.

The goal is not to replace GitHub support. The goal is to make Codex genuinely usable from mobile devices, improve accessibility for developers who benefit from conversational AI-assisted development, and let users choose where their code lives.

Related issues

This request overlaps with several existing issues, but combines mobile-first access, accessibility, and provider-diverse cloud repository workflows in one proposal.

Provider diversity

• #30038 — Requests configurable Git providers and credentials for self-hosted Git servers.
• #8156 — Requested support for non-GitHub Git platforms including GitLab, Gitea, Gogs, and Forgejo.
• #33071 — Requests provider-agnostic and configurable pull/merge request navigation instead of hard-wiring Codex App to GitHub and the gh CLI.

Accessibility

• #22816 — Reports screen reader focus repeatedly jumping to the top while Codex generates output, making active responses difficult to follow.
• #28637 — Reports VoiceOver focus and accessibility-tree problems when using Codex CLI in Warp.

Mobile

• #22800 — Reports Android-specific problems with Codex Mobile, including Android-started threads disappearing and limitations in the mobile permissions UI. This demonstrates demand for initiating Codex workflows from Android, although the reported workflow still depends on a desktop host.
• #20757 — Requested a first-class mobile companion experience for desktop and cloud Codex tasks. This issue was closed as a duplicate, but is related to the broader demand for better mobile access.

Most existing mobile issues I found focus on pairing or remotely controlling Codex Desktop from Android or iOS. This request goes further: it asks for mobile devices to function as first-class Codex development environments through accessible cloud repository workflows, without requiring a desktop host.

These issues demonstrate related demand for provider-neutral Git workflows, accessible Codex experiences, and stronger mobile support. This issue focuses specifically on bringing those concerns together with native mobile-first use on Android and iOS.

Additional information

_No response_