gopidesupavan opened a new pull request, #63081: URL: https://github.com/apache/airflow/pull/63081
followup of this https://github.com/orgs/apache/projects/586/views/1?pane=issue&itemId=160878385&issue=apache%7Cairflow%7C62872 ## Summary This PR adds a **Human-in-the-Loop (HITL) Review** flow for agentic operators . After the LLM generates output, a human reviewer can **approve**, **reject**, or **request changes** via a chat UI. The operator blocks until a terminal action or timeout. ***Approch*** Plugin + Workers (State store via XCOMS) **Main components:** - **HITLReviewMixin** — Mixin that drives the review loop inside `execute()`, polling XCom for human actions and triggering regeneration. - **HITL Review Plugin** — FastAPI app mounted at `/hitl-review`, exposing REST endpoints and a chat UI. **Flow:** The operator pushes the initial output and session metadata to XCom, polls for human actions, and on **approve** returns the output, on **reject** raises `HITLRejectError`, or on **changes_requested** calls `regenerate_with_feedback` and loops. All state is stored in XCom on the task instance. --- ## 2. Architecture ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ Plugin │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ HITL Review Plugin (FastAPI @ /hitl-review) │ │ │ │ • GET /sessions/find • POST /sessions/feedback │ │ │ │ • POST /sessions/approve • POST /sessions/reject │ │ │ │ • GET /chat, /chat-by-task (interactive UI) │ │ │ │ • Reads/writes XCom via metadata DB │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ └─────────────────────────────────────────────────────────────────────────────┘ │ │ XCom (metadata DB) ▼ ┌─────────────────────────────────────────────────────────────────────────────┐ │ Worker (Task Execution) │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ AgentOperator + HITLReviewMixin │ │ │ │ 1. Generate output → push session + output to XCom │ │ │ │ 2. Poll airflow_hitl_review_human_action │ │ │ │ 3. On approve → return; reject → raise; changes_requested → │ │ │ │ regenerate_with_feedback → push new output → goto 2 │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` **Storage:** XCom keys `airflow_hitl_review_*` store session, human action, agent outputs, and human feedback. Both worker and plugin read/write these keys. **Communication:** Worker pushes session and output to XCom; human reviewer uses UI or REST API to submit feedback/approve/reject; plugin writes human action to XCom; worker polls and acts on the action. --- ## 3. Additional Considerations (Future Scope) - **Webhooks:** - **Callbacks** - Pydantic [AGI](https://ai.pydantic.dev/ui/ag-ui/). --- ## Context This work is a **first step** toward the **Progress interface and iterative HITL feedback** envisioned in [AIP-99 Common Data Access Pattern + AI](https://github.com/orgs/apache/projects/586?pane=issue&itemId=160880877), providing an in-process, XCom-based HITL loop for agentic operators. - [ ] Add tests - [ ] Update docs - [ ] Plugin UI enhancements https://github.com/orgs/apache/projects/586?pane=issue&itemId=160880877 <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [X] Yes (please specify the tool below) - yes used cursor for UI handling. dont have any experience with UI. cursor helped alot. :) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
