fix: preserve background notifications after end_turn#149
fix: preserve background notifications after end_turn#149Gujiassh wants to merge 1 commit intoshareAI-lab:mainfrom
Conversation
|
@Gujiassh is attempting to deploy a commit to the crazyboym's projects Team on Vercel. A member of the Team first needs to authorize it. |
86a75cd to
f2621a4
Compare
|
Follow-up note: this branch was rebuilt from current main around the background-notification wait logic, and the focused regression checks pass locally ( |
f2621a4 to
51f1157
Compare
|
Follow-up note: I rebuilt this branch again from the latest available main snapshot, preserved the no-assistant-ack contract, and reran the focused background notification regression checks locally ( |
|
Status update: after the latest refresh, this branch still has no visible code-side CI failures. The only remaining blockers are the two Vercel team-authorization statuses on the project account side. |
51f1157 to
e62d5ae
Compare
|
Follow-up note: I rebuilt this branch once more directly on top of the latest current main, so it now carries only the background-notification wait fix and its focused regression tests. The refreshed head is |
Summary
end_turnEnd-user benefit
When a long-running background command finishes right after the model returns
end_turn, the current examples can exit before the result is ever surfaced back into the conversation. This change makes the background result reliably show up in the transcript instead of silently disappearing.Testing
python -m pytest tests/test_background_notifications.py -qpython -m py_compile agents/s08_background_tasks.py agents/s_full.py tests/test_background_notifications.py