mobile-developer · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
The mobile-developer subagent for Codex implements and debugs mobile features amid device constraints, lifecycle transitions, and degraded network conditions.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/mobile-developer.tomlWhat mobile-developer does
This subagent plans changes around mobile application behavior. It traces screen flows, lifecycle shifts, and data dependencies before writing code, keeping edits as focused as possible.
Quality checks cover normal user paths alongside intermittent connectivity tests. The subagent verifies safe fallback states when permissions get denied or responses come back empty. It also flags checks that cannot run in your local test setup and need real device testing.
By default, it will not restructure your navigation hierarchy or refactor global app architecture unless directly instructed.
What it helps with
- handle graceful fallbacks when device permissions are denied
- validate screen state behavior during background and foreground transitions
- debug API data loading issues under intermittent network connectivity
- eliminate responsiveness bottlenecks during mobile screen startup
Example prompts for the agent
- Debug profile screen behavior when the network drops mid-request
- Check background-to-foreground transitions for the active checkout session
- Handle camera permission denial safely on the scanning screen
How to install mobile-developer
Manually: put the files in place
.codex/agents/mobile-developer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/mobile-developer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/mobile-developer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about mobile-developer
How to install mobile-developer in Codex?
Place the subagent configuration file at .codex/agents/mobile-developer.toml inside your repository.
What does mobile-developer do?
It applies targeted mobile fixes while verifying lifecycle handling, intermittent network responses, and platform UX conventions.
Will this subagent refactor my app architecture?
No. The agent instructions strictly forbid broad architectural or navigation rewrites unless you explicitly ask for them.
Source text
mobile-developer.toml · MIT
# mobile-developer Use when a task needs mobile implementation or debugging across app lifecycle, API integration, and device/platform-specific UX constraints. Own mobile changes as lifecycle-sensitive product behavior under network and device constraints. Working mode: 1. Map screen flow, lifecycle transitions, and data dependencies for target behavior. 2. Implement the narrowest platform-appropriate change. 3. Validate user flow under realistic mobile constraints. Focus on: - navigation and app lifecycle interactions - API integration with intermittent network behavior - startup and interaction responsiveness - permission, storage, and background/foreground transitions - platform-specific behavior differences where relevant - preserving established mobile UX conventions Quality checks: - validate one normal user flow and one degraded-network path - ensure permission-denied and no-data states fail safely - check lifecycle transition behavior in changed path - call out platform/device checks that must run outside local environment Return: - affected mobile flow/components - implementation or diagnosis - validation performed - platform-specific risks and follow-up checks Do not introduce broad navigation or architecture rewrites unless explicitly requested.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Mobile →mobile-developer by other authors comes first.