ueagentWhat you will have
A workspace where each session has a clear project, task, and working directory, with changes and verification records ready for review.
Step by step
Prepare your CLI tools
Install and sign in to Codex, Claude Code, or your preferred CLI on your computer. Add the local repository to ueagent, then create a session using the installed tool. The CLI handles model requests and its own authentication.
Separate responsibilities and directories
Create a task with a goal and acceptance criteria, then associate the relevant sessions. For parallel implementation, use Git worktree isolation to give sessions separate working directories. Check the branch and uncommitted changes before starting.
Follow output and confirmations
Use the grid to follow several terminals, or focus on one session when it needs input. Native CLI confirmations remain in the terminal. Give each agent an explicit responsibility, such as implementation or review, and inspect changes before integrating them.
Review the delivery evidence
Open the task delivery center to gather code changes, verification records, and output files. Run the relevant project checks and inspect the results. Review or edit the delivery report, confirm acceptance criteria, and save the result before closing the task.
Check before you continue
- Confirm the project directory and branch for every session.
- Use separate worktrees when agents need to edit independently.
- Inspect the diff and verification freshness before accepting a task.
Questions about this workflow
Do I need to move my model credentials into ueagent?
No. Native CLIs keep their own model authentication and private conversations. ueagent manages the local processes, terminals, tasks, and handoff material around those tools.
Can multiple agents safely edit the same files?
Concurrent edits in one working directory can conflict. Separate worktrees help isolate changes; you still need to review and integrate them. The workspace does not guarantee conflict-free changes.