kaxil commented on code in PR #71464:
URL: https://github.com/apache/airflow/pull/71464#discussion_r3764864522
##########
providers/anthropic/docs/operators/anthropic.rst:
##########
@@ -282,6 +282,60 @@ task's real outcome is preserved and a warning is logged.
session records instead. This is the same scenario as the retry warning
above, so
``retries=0`` keeps both problems away.
+Configuring the agent
+"""""""""""""""""""""
+
+Agent-level settings are not operator arguments: they belong to the agent,
which is created
+once and referenced by ID on every run.
+:meth:`~airflow.providers.anthropic.hooks.anthropic.AnthropicHook.create_agent`
forwards
+keyword arguments to the API unchanged, so these need no provider support.
+
+**Pinning the inference region.** Pass ``model`` as a config object instead of
a bare id to
+confine inference to one region:
+
+.. code-block:: python
+
+ hook.create_agent(
+ name="us-only-analyst",
+ model={"id": "claude-opus-4-8", "inference_geo": "us"},
+ )
+
+The accepted values are ``"us"`` and ``"global"``; anything else is rejected
with
+``400 inference_geo: must be one of ["global" "us"]``. When ``inference_geo``
is unset,
Review Comment:
Not taking this one, but you were right that the line was wrong -- it just
needed removing rather than fixing.
That string was quoting the API's response verbatim, and the API really does
return `["global" "us"]` with no comma. Adding the comma would have made the
quote inaccurate. But it reads as a typo, which is the problem: an error string
copied verbatim invites exactly this correction, and it had already drawn one
round of review over backslash escaping.
So the quote is gone. The text now says an unsupported value is rejected
with a 400 naming the accepted set, and links to the page that owns the list --
which also answers your drift question on the same line.
--
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]
