You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(agentex): materialized Task.current_state for reactive state observability
Expose an agent's StateMachine current state to REST/SSE consumers via a
nullable, opaque `Task.current_state` label. It is written through the existing
UPDATE_TASK / PUT /tasks/{id} path, which already publishes a `task_updated` SSE
event carrying the full task, so updates are reactive (push) while GET /tasks/{id}
remains the authoritative point-read for load/reconnect reconciliation.
The field is framework-agnostic and default-null: agents opt in by writing it;
existing tasks and stream consumers are unaffected (additive, backward compatible).
- ORM column + Alembic migration (nullable add, down_revision a1b2c3d4e5f6)
- Task response schema, UpdateTaskRequest, TaskEntity + converter
- update_mutable_fields_on_task applies it in the same update_task write as
task_metadata (single task_updated publish)
- both PUT routes thread it through
- regenerated openapi.yaml
- tests: route PUT/null/no-clobber, task_updated carries current_state,
service-layer emit+persist, extra="ignore" forward-compat pin
0 commit comments