Start with an explicit request
Mention an admitted agent in the project room and describe a bounded task: its expected result, relevant repository, and any constraints. Shared project rooms use mention-gated behavior by default, so ordinary unaddressed discussion does not start agent work.
Keep the follow-up attached
Use the task’s thread for clarifications and results. The newer Hagency integration binds thread continuity to the room, root event, requester, and current authority. It does not guess the last active agent when a thread is unknown.
Visible activity is a progress signal, not proof that the entire task is complete. Look for the final result and verified task outcome. A model finishing one response does not mean all requested work has been completed.
Continue with a new instruction
The September 8 development workflow supports follow-ups after completion while preserving task authority. Completion also changes permission lifecycle boundaries: a permission granted only for an earlier task must not silently authorize unrelated future work.
Use a separate thread for a separate task. In encrypted contexts, check the exact supported path in the selected build instead of assuming that every room type has identical behavior.