feat(eino): update zh and en docs

_typos.toml

@@ -14,3 +14,4 @@ mmaped = "mmaped"
 exten = "exten"
 invokable = "invokable"
 typ = "typ"
+Rabit = "Rabit"

content/en/docs/eino/FAQ.md

@@ -1,13 +1,13 @@
 ---
 Description: ""
-date: "2025-12-11"
+date: "2026-01-20"
 lastmod: ""
 tags: []
 title: FAQ
 weight: 6
 ---
 
-# Q: cannot use openapi3.TypeObject (untyped string constant "object") as *openapi3.Types value in struct literal; cannot use types (variable of type string) as *openapi3.Types value in struct literal
+# Q: cannot use openapi3.TypeObject (untyped string constant "object") as *openapi3.Types value in struct literal，cannot use types (variable of type string) as *openapi3.Types value in struct literal
 
 Ensure the `github.com/getkin/kin-openapi` dependency version does not exceed `v0.118.0`. Starting from Eino `v0.6.0`, Eino no longer depends on the `kin-openapi` library.
 
@@ -59,8 +59,10 @@ toolCallChecker := func(ctx context.Context, sr *schema.StreamReader[*schema.Mes
              // finish
              break
           }
+
           return false, err
        }
+
        if len(msg.ToolCalls) > 0 {
           return true, nil
        }
@@ -69,10 +71,10 @@ toolCallChecker := func(ctx context.Context, sr *schema.StreamReader[*schema.Mes
 }
 ```
 
-Note: this custom `StreamToolCallChecker` checks all chunks for tool calls. When the model is outputting a normal answer, this may reduce “early streaming detection”, because it waits until all chunks are inspected. To preserve streaming responsiveness, try guiding the model with prompts:
+Note: this custom `StreamToolCallChecker` checks all chunks for tool calls. When the model is outputting a normal answer, this may reduce "early streaming detection", because it waits until all chunks are inspected. To preserve streaming responsiveness, try guiding the model with prompts:
 
 > 💡
-> Add prompt constraints such as: “If a tool is required, output only the tool call; do not output text.”
+> Add prompt constraints such as: "If a tool is required, output only the tool call; do not output text."
 >
 > Models vary in how much they adhere to such prompts. Tune and validate for your chosen model.
 
@@ -82,18 +84,16 @@ Older versions of `sonic` are incompatible with `go1.24`. Upgrade to `v1.13.2` o
 
 # Q: Tool input deserialization failed: `failed to invoke tool call {tool_call_id}: unmarshal input fail`
 
-Models typically do not produce invalid JSON. Investigate the specific reason for deserialization failure; in most cases this is due to output truncation when the model’s response exceeds limits.
+Models typically do not produce invalid JSON. Investigate the specific reason for deserialization failure; in most cases this is due to output truncation when the model's response exceeds limits.
 
-# Q: How can I implement batch processing nodes in Eino (like Coze’s batch nodes)?
+# Q: How can I implement batch processing nodes in Eino (like Coze's batch nodes)?
 
 Eino currently does not support batch processing. Two options:
 
 1. Dynamically build the graph per request — the overhead is low. Note that `Chain Parallel` requires the number of parallel nodes to be greater than one.
 2. Implement a custom batch node and handle batching inside the node.
 
-# Q: Panic occurs in Fornax SDK or panic stack mentions Fornax SDK
-
-Upgrade both the Fornax SDK and Eino to the latest versions and retry.
+Code example: [https://github.com/cloudwego/eino-examples/tree/main/compose/batch](https://github.com/cloudwego/eino-examples/tree/main/compose/batch)
 
 # Q: Does Eino support structured model outputs?
 
@@ -105,19 +105,15 @@ Yes, in two steps:
    - Prompt the model explicitly to output structured data.
 2. After obtaining a structured message, use `schema.NewMessageJSONParser` to parse the message into your target struct.
 
-# Q: In image recognition scenarios, error: `One or more parameters specified in the request are not valid`
-
-Check whether the model supports image input (for Doubao models, only variants with `vision` support it).
-
-# Q: How to access Reasoning Content / “thinking” output from a chat model?
+# Q: How to access Reasoning Content / "thinking" output from a chat model?
 
 If the model implementation supports Reasoning Content, it is stored in the `ReasoningContent` field of the output `Message`.
 
 # Q: Errors include `context deadline exceeded`, `timeout`, or `context canceled`
 
 Cases:
 
-1. `context.canceled`: While executing a graph or agent, the user code passed a cancelable context and triggered cancellation. Investigate your application’s context-cancel logic. This is unrelated to the Eino framework.
+1. `context.canceled`: While executing a graph or agent, the user code passed a cancelable context and triggered cancellation. Investigate your application's context-cancel logic. This is unrelated to the Eino framework.
 2. `context deadline exceeded`: Two common possibilities:
    1. During graph or agent execution, the user code passed a context with a timeout, which was reached.
    2. A `ChatModel` or other external resource has its own timeout configured (or its HTTP client does), which was reached.
@@ -126,11 +122,11 @@ Inspect the thrown error for `node path: [node name x]`. If the node name is not
 
 If you suspect 2-a, trace upstream to find where a timeout was set on the context (common sources include FaaS platforms, gateways, etc.).
 
-If you suspect 2-b, check whether the node itself configures a timeout (e.g., Ark ChatModel `Timeout`, or OpenAI ChatModel via an `HttpClient` with `Timeout`). If none are configured but timeouts still occur, it may be the SDK’s default timeout. Known defaults: Ark SDK 10 minutes; Deepseek SDK 5 minutes.
+If you suspect 2-b, check whether the node itself configures a timeout (e.g., Ark ChatModel `Timeout`, or OpenAI ChatModel via an `HttpClient` with `Timeout`). If none are configured but timeouts still occur, it may be the SDK's default timeout. Known defaults: Ark SDK 10 minutes; Deepseek SDK 5 minutes.
 
 # Q: How to access parent graph `State` within a subgraph?
 
-If the subgraph and parent graph have different `State` types, use `ProcessState[ParentStateType]()` to process the parent’s state. If they share the same `State` type, make the types distinct (for example, with a type alias: `type NewParentStateType StateType`).
+If the subgraph and parent graph have different `State` types, use `ProcessState[ParentStateType]()` to process the parent's state. If they share the same `State` type, make the types distinct (for example, with a type alias: `type NewParentStateType StateType`).
 
 # Q: How does `eino-ext` adapt multimodal input/output for supported models?
 
@@ -150,4 +146,33 @@ If schema migration is complex, use the helper tooling in the [JSONSchema conver
 
 # Q: Which ChatModels in `eino-ext` support the Responses API form?
 
-By default, ChatModels generated by `eino-ext` do not support the Responses API; they support only the Chat Completions API. A special case is the Ark Chat Model, which implicitly supports the Responses API when you set `Cache.APIType = ResponsesAPI`.
+- In `eino-ext`, currently only the ARK Chat Model can create a ResponsesAPI ChatModel via **NewResponsesAPIChatModel**. Other models do not support creating or using ResponsesAPI.
+- In `eino-byted-ext`, only bytedgpt supports creating Response API via **NewResponsesAPIChatModel**. Other chatmodels have not implemented Response API Client.
+  - Version `components/model/gemini/v0.1.16` already supports `thought_signature` passback. Check if your gemini version meets the requirement. If using bytedgemini (code.byted.org/flow/eino-byted-ext/components/model/bytedgemini) chatmodel implementation, check if its dependency `components/model/gemini` is the latest version, or directly upgrade gemini via go get.
+  - Replace the currently used bytedgpt package with [code.byted.org/flow/eino-byted-ext/components/model/bytedgemini](http://code.byted.org/flow/eino-byted-ext/components/model/bytedgemini) implementation, upgrade to the latest version, and check the example code to confirm how to pass BaseURL.
+  - If you encounter this error, please confirm whether the base url filled in when generating chat model is the chat completion URL or the ResponseAPI URL. In most cases, it's an incorrect ResponseAPI Base URL being passed.
+
+# Q: How to troubleshoot ChatModel call errors? For example: [NodeRunError] failed to create chat completion: error, status code: 400, status: 400 Bad Request.
+
+This type of error comes from the model API (such as GPT, Ark, Gemini, etc.). The general approach is to check whether the actual HTTP Request to the model API has missing fields, incorrect field values, wrong BaseURL, etc. It's recommended to print the actual HTTP Request via logs and verify/modify the HTTP Request through direct HTTP requests (such as sending Curl from command line or using Postman). After identifying the problem, modify the corresponding Eino code accordingly.
+
+For how to print the actual HTTP Request to the model API via logs, refer to this code example: [https://github.com/cloudwego/eino-examples/tree/main/components/model/httptransport](https://github.com/cloudwego/eino-examples/tree/main/components/model/httptransport)
+
+# Q: The gemini chat model created under eino-ext repository doesn't support passing multimodal via Image URL? How to adapt?
+
+Currently, the gemini Chat model under the Eino-ext repository has added support for passing URL types. Use `go get github.com/cloudwego/eino-ext/components/model/gemini` to update to [components/model/gemini/v0.1.22](https://github.com/cloudwego/eino-ext/releases/tag/components%2Fmodel%2Fgemini%2Fv0.1.22), the latest version, and test whether passing Image URL meets your business requirements.
+
+# Q: Before calling tools (including MCP tools), JSON Unmarshal failure error occurs. How to solve it?
+
+The Argument field in the Tool Call generated by ChatModel is a string. When the Eino framework calls the tool based on this Argument string, it first performs JSON Unmarshal. At this point, if the Argument string is not valid JSON, JSON Unmarshal will fail with an error like: `failed to call mcp tool: failed to marshal request: json: error calling MarshalJSON for type json.RawMessage: unexpected end of JSON input`
+
+The fundamental solution to this problem is to rely on the model to output valid Tool Call Arguments. From an engineering perspective, we can try to fix some common JSON format issues, such as extra prefixes/suffixes, special character escaping issues, missing braces, etc., but cannot guarantee 100% correction. A similar fix implementation can be found in the code example: [https://github.com/cloudwego/eino-examples/tree/main/components/tool/middlewares/jsonfix](https://github.com/cloudwego/eino-examples/tree/main/components/tool/middlewares/jsonfix)
+
+# Q: How to visualize the topology structure of a graph/chain/workflow?
+
+Use the `GraphCompileCallback` mechanism to export the topology structure during `graph.Compile`. A code example for exporting to mermaid diagram: [https://github.com/cloudwego/eino-examples/tree/main/devops/visualize](https://github.com/cloudwego/eino-examples/tree/main/devops/visualize)
+
+## Q: In Eino, when using Flow/React Agent scenarios, how to get the Tool Call Message and the Tool Result of the tool invocation?
+
+- For getting intermediate results in Flow/React Agent scenarios, refer to the document [Eino: ReAct Agent User Manual](/docs/eino/core_modules/flow_integration_components/react_agent_manual)
+  - Additionally, you can replace Flow/React Agent with ADK's ChatModel Agent. For details, refer to [Eino ADK: Overview](/docs/eino/core_modules/eino_adk/agent_preview)

content/en/docs/eino/_index.md

@@ -1,6 +1,6 @@
 ---
 Description: Eino is a Golang-based AI application development framework
-date: "2025-12-09"
+date: "2026-01-20"
 lastmod: ""
 linktitle: Eino
 menu:
@@ -11,4 +11,3 @@ tags: []
 title: Eino User Manual
 weight: 6
 ---
-