A place for every project
Organize Codex, Claude Code, custom CLI, and Shell sessions by project. Follow output in a grid or focus on one terminal, keeping native CLI input and confirmation flows.
A clear desk for parallel development
Bring Codex, Claude Code, and your CLI into one window. Organize real terminals by project, keep work moving, and know where every task stands.
Windows, macOS & Linux on desktop · Remote access from web & mobile
Keep the tools you know
Less window switching. More progress.
Sessions, tasks, and context in their place. Keep your attention on the code.
Organize Codex, Claude Code, custom CLI, and Shell sessions by project. Follow output in a grid or focus on one terminal, keeping native CLI input and confirmation flows.
Save goals, acceptance criteria, structured handoffs, and checkpoints independently of sessions. After a quota limit or process failure, inspect code changes and prepare the next agent to continue.
Pair your computer and explicitly enable remote management. View real sessions from a browser or phone. Terminal input requires a control lease; offline input is never automatically replayed.
Keep your own development rhythm
ueagent organizes your workspace and tasks. Model requests, authentication, and terminal confirmations follow each CLI’s own workflow.
See how terminals and tasks workPractical guides / Workflows
Learn how to manage multiple coding agents, hand off interrupted tasks, and follow local development from your phone. Each guide includes practical steps and checks.
When several coding agents work at once, a clear project, directory, and task matter as much as another terminal. ueagent keeps native CLI sessions together so you can follow their work and review the result.
Read the guide : Multi-agent developmentA quota limit or interrupted process should not leave the next agent guessing. Save the task goal, completed work, relevant files, test results, and open issues as a handoff you can inspect before continuing.
Read the guide : Agent handoff and recoveryUse your phone to check a local task, read terminal output, and respond when a session needs attention. Code and CLI processes keep running on the paired computer; your phone connects to that workspace.
Read the guide : Remote development from your phoneCommon questions
The demo uses sample output. Real execution requires the desktop app. Remote access needs a paired computer with remote management enabled; that computer runs the commands.
Save a structured handoff and terminal context, stop the old session, then switch agents and review the handoff. This does not convert private model conversations or automatically send a task.
Project files stay on the execution computer. The account service stores account, device, and team metadata and forwards authorized requests. Shared prompts, comments, and templates live on the server; the operator chooses which output to share.
Give your next task a clear place to start