kaxil opened a new pull request, #62870: URL: https://github.com/apache/airflow/pull/62870
The existing `AGENTS.md` for the common AI provider covers hooks and operators but has no guidance for toolsets. As we start adding more toolset backends alongside `SQLToolset`, contributors need a clear pattern to follow. This adds: - **"One backend per toolset" design principle** — each toolset wraps a single execution backend. When a new backend needs the same tool interface, create a new toolset class rather than adding conditional branches. Users compose toolsets via `AgentOperator(toolsets=[...])`. - **"Adding a New Toolset" section** — covers the four-tool SQL pattern (`list_tables`, `get_schema`, `query`, `check_query`), shared helper extraction, constructor hygiene (no silently-ignored params), and `sequential=True` guidance. - **Toolsets key path** added to the Key Paths section. ## Why now With DataFusion and other backends on the horizon, having this guidance upfront keeps new toolset PRs consistent and avoids dual-mode classes that branch on constructor params. -- 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]
