Repository navigation
Add a feature map to the Common AI docs - #74723
Merged
Merged
Conversation
Turn features.rst into a feature map: one row per feature with the page that documents it, the extra it needs, the oldest Airflow version it runs on, and whether it is stable. Link it from the landing page next to Why Common AI, and add labels for the three sections it links into.
The map keeps the feature, what it does and the extra it needs. Airflow version floors live in the installation page, which gains the two the map used to carry (usage limits across retries and the AI Model tab), and stability lives in the stability page.
Lee-W
approved these changes
Oct 14, 2026
vatsrahul1001
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Someone who has used Airflow but never Common AI had no single place to see what the provider can do.
features.rstlisted eight call-level settings. Operators, toolsets, sandboxing, retry policies, provider fallback, batch, durable execution, usage limits, other agent frameworks and tracing were spread across the sidebar, and nothing said which extra each one needs.Rendered page:
This turns
features.rstinto a feature map: one row per feature, grouped by what the reader is trying to do. Each row gives a one-line description, a link to the page that documents it, and the extra it needs. The extras come from[project.optional-dependencies]inpyproject.tomland the optional imports behind each feature (for example,SQLToolsetand@task.llm_sqlimportsqlglotfrom thesqlextra; the managed-agent toolset comes from the Amazon or Google provider'scommon.aiextra).The page keeps its path and its
howto/featureslabel, so existing links still work. The landing page links it next to Why Common AI, and it moves to the top of the Guides group in the sidebar as "Feature map". Three linked sections had no label to link to, so this adds labels for the AI Model tab, the confidence gate and "Any other framework".Minimum Airflow versions and stability stay on their own pages, which the map's intro links to. The installation page's version table gains the two floors it was missing: usage limits counted across retries (3.3) and the AI Model tab (3.4).
Tool-call logging has no row yet. It is on by default with nothing to configure, and #74694 is making
LoggingToolsetprivate and rewriting that page.