Give each repository an explicit boundary
Create separate projects for client repositories, then set the provider capacity appropriate for each. Project separation keeps queue and history ownership clear. It is not a filesystem sandbox and does not automatically isolate simultaneous edits to a shared checkout.
Write acceptance criteria before launching
Name the customer-visible behavior and the checks expected at completion. Attach relevant references when useful. The resulting task record gives you a starting point for review and a clear place to send corrections through supported continuation.
Explain completed work from recorded evidence
Standup drafts a dated project changelog from successful execution attempts in a one-day or two-day window. Ask follow-up questions against that saved evidence, then verify what actually shipped before sending a client-facing update.
Check permissions and provider handling
The task database and artifacts are local, while prompts and relevant context still go to your configured AI providers. Obtain the appropriate client permission for that workflow.