PhoneAgents.io

// launch update in progress

Mobile-First AI Agent OS& Self-Improving Memory Vault

Run AI agent workflows from Telegram and a mobile app preview, while every agent, CLI, finding, and project lesson syncs back into a shared operational memory layer.

The Agent Stack

Not one AI tool. A coordinated team.

PAM is the planning and allocation layer for PhoneAgents: it dispatches specialist agent streams, tracks approvals, monitors progress, and keeps work moving across model providers without losing operational context.

~/PAM Orchestrator
Active · Dispatching

pam dispatch --parallel --approval-gated

PAM Orchestrator

Planning & Allocation Manager

Plans waves, assigns specialist lanes, tracks progress, and routes work between Claude, Codex, Pi, and Hermes while preserving human approval gates.

waves: 53PRs: 364+routes: 5
~/CLAUDE-CODE
Active · Opus

claude --session-id=w53

Claude Code

Primary Coding Agent

Owns broad implementation streams with long-context architectural awareness.

context: 1Mlane: build
~/CODEX-CLI
Active · GPT-5

codex run --review

Codex CLI

OpenAI Code Agent

Runs implementation and second-opinion review streams in parallel.

provider: openailane: verify
~/PI-AGENT
Standby · Fallback

pi --fallback --bedrock

Pi Agent

Fallback Coding Lane

Keeps work moving when limits, model availability, or routing constraints appear.

provider: bedrocklane: backup
~/HERMES
Daemon · 24/7

hermes daemon --schedule

Hermes

Orchestration Backbone

Schedules jobs, monitors wave progress, and keeps memory and status loops alive.

uptime: 24/7cron: */1

Each lane stays inspectable as a terminal card: current status, command, role, and operating metadata are visible before a human approves sensitive writes, pushes, or deployments.