Separate repository work at the queue boundary
Set Codex, Claude, and OpenCode concurrency independently for each project. A busy queue in one repository does not have to hide work running in another. Account for total provider load across projects when choosing those limits.
Retain the context of each requested change
A task stores its request, activity, result, and supported conversation identifier. Available task-owned patches help explain what the agent reported changing. The separate workspace view can include other disk changes observed during execution, so do not attribute every workspace edit to one task.
Build status updates from the correct source
Use project-scoped Standup to summarize successful attempts in a dated window. Reconcile that development evidence with your own review, merge, and deployment process before describing work as delivered to a client.
Understand the current product boundary
This is a local operator workspace, not a hosted team collaboration or access-control system. Multi-seat terms, shared cloud history, and enterprise service guarantees are not advertised. Model-provider handling remains part of your client workflow.