Skip to content

Conversation

@shentongmartin
Copy link
Contributor

No description provided.

@shentongmartin shentongmartin requested review from a team as code owners January 20, 2026 11:46
@netlify
Copy link

netlify bot commented Jan 20, 2026

Deploy Preview for cloudwego ready!

Name Link
🔨 Latest commit 8c9e954
🔍 Latest deploy log https://app.netlify.com/projects/cloudwego/deploys/6971f5cdd7c99a00088240dc
😎 Deploy Preview https://deploy-preview-1499--cloudwego.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@@ -93,7 +93,7 @@ ChatModel(LLM) 生成要调用的 []ToolCall(包含 ToolName,Argument 等)

每个 ToolCall 调用完成后的结果,又会封装为 *schema.Message,作为 ToolsNode 输出的一部分。

## **Tool 定义**
## **Tool ****定义**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

是不是写错了

<tr><td>协作方式</td><td>描述</td></tr>
<tr><td> Transfer</td><td>直接将任务转让给另外一个 Agent,本 Agent 则执行结束后退出,不关心转让 Agent 的任务执行状态</td></tr>
<tr><td>ToolCall(AgentAsTool)</td><td>将 Agent 当成 ToolCall 调用,等待 Agent 的响应,并可获取被调用Agent 的输出结果,进行下一轮处理</td></tr>
</table>

- AgentInput 的上下文策略

<table class="bd-browser-bugs table table-bordered table-hover">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这些改动是预期的吗

```

**返回值:**

- `isResumeFlow`: 如果组件被恢复调用明确指定为目标,则为 `true`。如果为 `false`,组件必须重新中断以保留其状态。
- `hasData`: 如果为此组件提供了数据,则为 `true`。
- `isResume``Target`: 如果组件被恢复调用明确指定为目标,则为 `true`。如果为 `false`,组件必须重新中断以保留其状态。注意,如果组件没有被直接指定,但是是被直接指定的组件的上级,`isResumeTarget` 的结果依然为 `true`。比如 NodeA 中断且被指定为恢复目标,则 NodeA 所在的 GraphA 也会是恢复目标。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

写错了?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants