2. 设置和个性化定制助理 [GA]
启用 API - 这是 Bumble 管理员会执行的操作。请说明此操作不适合参与者，因为参与者可能无法访问 Google Cloud 控制台。
需要将此项添加为云管理员完成研讨会的先决条件
配置个性化功能
下拉菜单中没有“Consumer Software & Mobile App Development”，因此他们需要选择“自定义”，然后添加此
然后，他们必须关闭该弹出式窗口
3. 配置数据连接器 [正式版]
此操作由 Gemini Enterprise 管理员完成，而不是由参与者完成。因此，请将此作为研讨会的必备条件提及。
4. 与 Jira 连接器的基本互动 [正式版]
首先，需要为每位参与者授权连接器，以便他们使用 Jira 和 GitHub 连接器。以下是相关屏幕截图
image-1-jira-authozie.png
image-2-jira-authoziation-page.png
image-3-after-jira-authoziation.png
对 GitHub 执行相同的操作
还要求在处理 Jira 或 GitHub 连接器时停用 Google 搜索
image-4-disable-google-search.png
1. 查找 Jira 项目密钥 - 提供有关如何打开聊天窗口向 Gemini 提问的指南，以下屏幕截图供您参考
Image-5-jira-list-projects.png
对于其他测试（例如创建任务、评论、更新状态等），也请执行相同的操作。还相应地更新了相关屏幕截图
image-6-jira-create-projects-1.png
image-7-jira-create-projects-2.png
image-8-jira-create-projects-3.png
image-9-jira-comment-1.png
image-10-jira-comment-2.png
image-11-jira-comment-3.png
image-12-jira-status-1.png
image-13-jira-status-2.png
image-14-jira-status-3.png
5. 与 GitHub 连接器的基本互动 [正式版]
如需提交待办事项，您需要知道代码库名称。因此，我们来设置一个如下所示的提示，以获取代码库名称。
在运行此命令之前，需要告知参与者停用其他连接器，只保留 GitHub。
对于所有测试，获取相关图片并相应地添加。以下是屏幕截图文件名。
image-15-github-enable-1.png
image-16-github-list-repo-2.png
image-17-github-list-commit-3.png
image-18-github-list-pull-request-4.png
image-19-github-list-pull-request-summary-5.png
6. 交叉对比文档与执行 [正式版]
在“上传要求文档”步骤下，应先完成第 2 步“上传一个名为 requirements.txt 的文件，其中包含以下内容”，这样参与者就可以在笔记本电脑中创建该文件，以便他们拥有该文件。如需在 Mac 上创建 .txt 文件，请使用内置的“文本编辑”应用。打开“文本编辑”，前往顶部菜单，依次点击“格式”>“制作纯文本”。输入文本，依次点击“文件”>“保存”，为文件命名（确保文件名以 .txt 结尾），选择保存位置，然后点击。为其他笔记本电脑提供类似说明
此外，“在 Gemini Enterprise 对话界面中，点击 +（加号）图标或拖放文件以进行上传。”在此阶段不相关
创建需求文本后，打开新的对话窗口，停用其他连接器，仅启用 Jira，然后使用 Gemini 创建示例数据，接着运行分析，此时用户需要将 TXT 文件上传到 Gemini 应用。请参阅下方此测试的屏幕截图，这些屏幕截图的文件名按顺序排列。
image-20-jira-req-txt-1.png
使用 Gemini 创建示例数据的图片
image-21-jira-create-ticket-2.png
image-22-jira-create-ticket-confirmation-3.png
image-23-jira-create-ticket-done-status-confirmation-4.png
image-24-jira-create-ticket-confirmation-5.png
image-25-jira-create-ticket-inprogress-status-confirmation-6.png
image-26-jira-create-ticket-created-6.png
image-27-jira-create-tinjira-portal-7.png
“运行分析”的图片
image-28-jira-run-analysis-1.png
image-29-jira-run-analysis-output-2.png
“点击回答中提供的引用，验证 Gemini 引用的是文件或 Jira 工单的哪个部分。”但我实际上看不到引用
7. 使用 NotebookLM 分析冲刺待办项 [正式版]
同样，首先创建 txt 文件，为此提供说明，然后点击“创建新笔记本”。然后，上传一个名为 retro.txt 的文件，其中包含以下模拟笔记：
提供有关点击哪些内容以生成数据分析的说明。
以下是这些屏幕截图的图片文件
image-30-notebook-lm-output.png
image-31-notebook-lm-mindmap.png
8. 深入研究市场趋势 [公开预览版]
查看实际测试运行的屏幕截图，并更新说明（如有任何遗漏）。屏幕截图图片的相应文件名。另请提及，这些任务需要一些时间才能完成，因此请先触发这些任务，然后继续进行下一个实验，直到这些任务准备就绪。还应提供有关报告中要审核的内容、审核的详细信息
deep-research-1.png
deep-research-2.png
deep-research-3.png
9. 借助创意生成功能集思广益 [公开预览版]
查看实际测试运行的屏幕截图，并更新说明（如有任何遗漏）。屏幕截图图片的相应文件名。另请提及，这些操作需要一些时间才能完成，因此请触发并继续进行下一个实验，直到准备就绪。还应提供有关报告中要审核的内容、审核的详细信息
idea-agent-1
idea-agent-2
idea-agent-3
idea-agent-4
idea-agent-5
10. 构建多步骤 Scrum Master 助理 [公开预览版]
第一步是点击“新建代理”时显示的“Chat Agent”，因为“新建代理”下有一个“Workflow Agent”的预览选项，我们不会在本部分中介绍该选项。
请参阅图片 scrum-master-1.png
如需重命名代理，您需要点击中间的方框以打开侧边栏，请参阅图片 scrum-master-3.png 和 scrum-master-4.png
请参阅图片，了解下一步如何提供提示 - scrum-master-5.png
对于步骤 3“为此智能体提供以下指令”，实际上是创建了启用 Google 搜索的智能体，并将智能体重命名为“Lead Scrum Master”，请参阅图片 scrum-master-6.png。因此，我们移除将代理重命名为“Bumble-Lead-Scrum-Master”的第 2 步，因为提示会重命名代理，但请确保提示始终将代理命名为“Lead Scrum Master”。
此外，在提示中要求它仅使用 Jira 和 GitHub 连接器，而不使用 Google 搜索。
同时，将其余指令中的“Bumble-Lead-Scrum-Master”替换为当前代理名称
添加专业子智能体
第 1 步
在说明中提及，项目密钥之前已在第 4 步中搜索过。与 Jira 连接器的基本互动 [正式版] 实验步骤 1
取消选中 Google 搜索，仅保留 Jira
请参阅以下图片，并确保相应地更新说明
scrum-master-7.png
Scrum-master-8.png
第 2 步
在说明中提及，之前在第 5 步中搜索过代码库名称。GitHub 连接器的基本互动 [正式版] - 步骤 1
取消选中 Google 搜索，仅保留 GitHub
请参阅下图，并确保相应地更新说明
scrum-master-9.png
scrum-master-10.png
scrum-master-11.png
此提示实际上是在搜索公共 GitHub，并获得了“Generate the high-priority update for the Bumble project for the past 24 hours.”这一结果，这完全是错误的。代理应仅查找我提供的 Jira 项目和 GitHub 代码库中的数据。不确定原因。
请参考此屏幕截图，了解我获得的输出 - scrum-master-12.png。以下是实际输出
请务必正确更新指令，以便仅搜索在代理中配置的 Jira 项目和 GitHub 报告
Generate the high-priority update for the Bumble project for the past 24 hours.
Response complete
Gemini replied
Here is the high-priority daily update for the Bumble project ecosystem over the past 24 hours. [107, 109, 928, 934]
-
🚀 Overall Progress Summary
The past 24 hours saw significant progress in integrating Google’s Bumble Bluetooth stack across downstream tools, notably introducing native Windows support for NXBT
and adding optional BLE pairing transports to smpclient [107]. Additionally, core refactoring in Bumble's AVDTP (Audio/Video Distribution) layers has successfully eliminated resource-locking bugs [928]. Meanwhile, the community is actively tackling high-priority Classic Bluetooth pairing failures and Windows boot-up driver issues [59, 934].
-
✨ Key Achievements & Code Progress (GitHub)
Repository / Project
Contribution
Details
intercreate/smpclient
BLE Transport with Pairing (PR #107)
Added an optional bumble extra (smpclient[bumble]) providing SMPBumbleTransport [107]. This BLE transport drives external HCI USB controllers, supporting secure scanning, pairing PIN flows, and stored LTK encryption [107].
google/bumble
AVDTP In-Use Management (PR #928)
Merged! Avoids explicit stream in_use flag management by delegating to a dynamic property checking if stream state is IDLE [928]. This resolves previous edge-case resource leaks [923].
typenoob/nxbt
Native Windows Support (Issue #4)
Announced a major integration with Bumble enabling native Windows support for NXBT controllers via hci-socket and usb (WinUSB) transports
.
badoo/codeisok
Security Hardening (PR #109)
Enabled the secure flag for authentication cookies in the Login controller to prevent unencrypted session token transmission [109].
-
⚠️ Current Blockers & High-Priority Issues
While no tracking issues were found in Jira for "Bumble", the following high-priority issues are currently impeding progress in the GitHub ecosystem:
Classic Bluetooth Pairing Failures (Issue #59 - kindle-hid-passthrough) [59]
Status: Active / Investigation [59]
Impact: Classic-only Bluetooth HID devices (such as the Logitech K811 keyboard) fail during Simple Secure Pairing (SSP) with an AUTHENTICATION_FAILURE_ERROR (0x05) [59]. Bumble appears to bypass the user pairing delegate entirely [59].
Next Steps: Testing a speculative fix on feature/brcm-bt-support that relaxes pairing config constraints for BR/EDR [59].
Windows Startup Power-On Failures (Issue #934 - google/bumble) [934]
Status: Open [934]
Impact: Bluetooth USB dongles fail to power on during the very first boot on Windows systems [934]. The Intel driver receives a disallowed error (HCI_COMMAND_DISALLOWED_ERROR) during the initial HCI_RESET_COMMAND [934].
-
Would you like me to draft any replies to these active issues or prepare a Confluence summary document of the Windows workarounds?
give me the link for this repo intercreate/smpclient
Response complete
Gemini replied
The link for the intercreate/smpclient repository is:
👉 https://github.com/intercreate/smpclient
intercreate/smpclient repo is not in my repo in mumanoha/gemini-code-review-agent-demo. intercreate/smpclient is a public repo why are you getting me all the public repo
Response complete
Gemini replied
I retrieved results from public repositories because the search query for "Bumble" was executed globally across all of GitHub rather than being restricted to your specific repository (mumanoha/gemini-code-review-agent-demo).
When I initially searched your internal Jira projects and repositories for the project "Bumble", it returned no matches. To ensure I didn't miss any relevant information, my search query broadened its scope to look for any active issues or pull requests containing the keyword "Bumble" globally, which pulled in these public repositories (like Google's bumble library and intercreate/smpclient).
-
🔍 Filtering to Your Specific Repository
If "Bumble" is a branch, a specific folder, or a topic within your repository, I can narrow down the search.
Would you like me to run a targeted analysis specifically on mumanoha/gemini-code-review-agent-demo for any updates or commits made in the past 24 hours instead?
如果我使用此提示“Generate the high-priority update for the my projects for the past 24 hours.”，我会得到以下输出
请参阅图片 scrum-master-13.png
Generate the high-priority update for the my projects for the past 24 hours.
Response complete
Gemini replied
📊 Daily Project Status Report (Past 24 Hours)
-
🚀 Overall Progress Overview
Currently, the projects are focused on resolving critical infrastructure blockers on Google Cloud Platform while maintaining a steady baseline on application services. While there has been no new code merged or committed in the last 24 hours, the active development continues to center around service integration, and the infrastructure pipeline is currently held back by two newly updated high-priority Jira issues
.
-
🛠️ Code Progress & Achievements (GitHub)
There are no new commits or merged pull requests to report for the past 24 hours. The primary active work-in-progress remains:
Repository / PR
Status
Description
mumanoha/gemini-code-review-agent-demo PR #1: feat: Add menu-service application
🟡 Open
This pull request introduces the core menu-service application to the repository.
-
⚠️ Blockers & High-Priority Issues (Jira)
The following high-priority infrastructure issues were updated in the past 24 hours under the ge-bugs project and require immediate attention to prevent further deployment delays on the GCP Migration Strategy
:
Key
Priority
Status
Summary
Impact
GB-5
🔴 High
To Do
IAM permission shadowing in VPC
Conflicting IAM policies between the VPC and GKE cluster are causing intermittent permission denied errors for active services
.
GB-4
🔴 High
To Do
GKE node pool auto-scaling timeout
The GKE node pool is failing to auto-scale automatically, leading to pod scheduling failures under load
.
-
Let me know if you would like me to help assign these blockers or draft a follow-up message to the infrastructure team!
另外，我不确定连接器是否必须添加到根代理中。我移除了根代理中的连接器，并进行了测试，以下是输出结果。哪种配置是正确的？我不确定，我会让您决定正确的配置
请参阅图片 - scrum-master-14.png
Generate the high-priority update for the my projects for the past 24 hours.
Response complete
Gemini replied
High-Priority Update: Project GB (ge-bugs)
Here is the summary of P0/P1 (Highest/High priority) issues and blocked tickets in Project GB (ge-bugs) along with their current impact:
1. P0/P1 Issues (High Priority)
GB-4: GKE node pool auto-scaling timeout
Priority: High (P1)
Impact: The GKE node pool is failing to auto-scale dynamically under load. This results directly in pod scheduling failures, threatening application reliability and performance during high traffic
.
GB-5: IAM permission shadowing in VPC
Priority: High (P1)
Impact: Conflicting IAM policies between the VPC and the GKE cluster are causing intermittent "permission denied" errors for services, leading to unstable internal communication
.
2. Blocked Tickets
GB-7: Fix database latency issues
Priority: Medium
Status: Blocked
Impact: Progress on resolving database latency is halted. The ticket is currently blocked while waiting for the infrastructure team to increase IOPS
.
-
I will now hand control back to the root agent to synthesize this update into your unified daily report. Let's make sure this progress is tracked.
I have checked the open Pull Requests in the mumanoha/gemini-code-review-agent-demo repository:
Open Pull Requests:
PR #1: feat: Add menu-service application
State: Open
Review Status: There is currently one review submitted by gemini-code-assist[bot], which has a status of COMMENTED (not CHANGES_REQUESTED). The reviewer provided general code quality, testing, and dependency cleanup suggestions but did not block the PR with an explicit changes-requested status.
Therefore, there are no Pull Requests currently in the "Changes Requested" state.
I will now transfer control back to the root_agent to compile the complete update. Here is your unified daily report for the past 24 hours, highlighting the high-priority Jira blockers and active code progress on GitHub.
I, Gemini Enterprise, have analyzed your active projects and compiled the most critical updates to keep you and your team aligned.
-
🚨 High-Priority Jira Issues & Blockers
There are currently two high-priority bugs active in Project GB (ge-bugs), along with one blocked issue that requires infrastructure intervention.
Issue
Priority
Status
Description & Impact
GB-4: GKE node pool auto-scaling timeout
High
To Do
The GKE node pool is failing to auto-scale under load, resulting in active pod scheduling failures.
GB-5: IAM permission shadowing in VPC
High
To Do
Conflicting IAM policies between the VPC and GKE cluster are causing intermittent service permission errors.
GB-7: Fix database latency issues
Medium
🛑 Blocked
Progress is currently halted. The team is waiting on the infrastructure team to increase IOPS.
-
💻 GitHub Code Progress
Active progress continues on the gemini-code-review-agent-demo repository with one open pull request. There are currently no PRs blocked under a "Changes Requested" status.
PR # & Title
State
Review Status
Key Highlights
#1: feat: Add menu-service application
Open
Commented
Adds the menu-service Quarkus application. gemini-code-assist[bot] provided recommendations to clean up pom.xml, improve JPA mapping, utilize Panache's active record pattern, and expand test coverage.
-
Would you like me to help you draft a follow-up message to the infrastructure team to expedite the IOPS increase for GB-7, or would you like to dive deeper into any of these updates?
11. 构建资源影响分析器代理 [公开预览版]
第一步是点击“新建代理”时显示的“Chat Agent”，因为“新建代理”下有一个“Workflow Agent”的预览选项，我们不会在本部分中介绍该选项。
请参阅图片 scrum-master-1.png
改为选择“创建新代理”>“前往构建器”。我们可以在聊天中直接提供提示。请参阅此屏幕截图 resource-impact-1.png
代理创建项目后，需要取消选中 Google 连接器，然后点击“预览”以测试提示“团队成员‘Muthu’将外出 3 天。有什么影响？”
请参考图片，并务必根据说明相应地更新
resource-impact-2.png 和 resource-impact-3.png
测试完成后，点击“创建”以发布智能体
12. 高级：使用 ADK 构建和部署 [公开预览版]
我为这些步骤拍摄了屏幕截图，请查看这些屏幕截图，确保说明准确无误，并更新每个步骤的屏幕截图，使其清晰明了
第 1 步：设置环境
agent-cli-1.png
第 2 步：身份验证和设置
agent-cli-2.png
agent-cli-3.png - this steps a long time
agent-cli-4.png -
在说明中提及，CLI 会请求运行命令的权限，请选择“允许一次”
方法 B：使用 Gemini CLI（自然语言）
请参考图片，根据控制台中实际发生的情况正确更新说明。根据需要使用这些屏幕截图更新 Codelab，并提供可靠的说明
要审核的图片 - agent-cli-5.png 到 agent-cli-9.png
以下是 CLI 中的输出
我已使用智能体开发套件 (ADK) 为您构建了 Bumble-Ops-Assistant 智能体。
1. 代理实现
代理位于 bumble-ops-assistant/app/agent.py 中。它包含 check_build_health 工具，该工具会针对任何环境返回硬编码的“GREEN”状态。
1 def check\_build\_health(environment: str) \-\> str:
2 """Checks the build health for a given environment.
3
4 Args:
5 environment: The environment to check (e.g., 'prod', 'staging').
6
7 Returns:
8 The health status of the build.
9 """
10 return "GREEN"
11
12 root_agent = Agent(
13 name="Bumble_Ops_Assistant",
14 # ...
15 instruction="You are Bumble-Ops-Assistant, an operations assistant. 您可以查看生产环境和预演环境的 build 健康状况。
16 tools=[check_build_health],
17 )
2. 冒烟测试
我执行了两种类型的冒烟测试：
* 单元测试：我在 bumble-ops-assistant/tests/unit/test_health_tool.py 中创建并运行了单元测试，以直接验证工具的逻辑。
* 结果：2 个测试在 3.03 秒内通过
* 评估冒烟测试：我在 bumble-ops-assistant/tests/eval/evalsets/smoke_test.evalset.json 中搭建了一个简单的评估集，用于测试智能体的互动。
* 注意：评估运行遇到 PERMISSION_DENIED 错误，因为 aiplatform.googleapis.com API 未在 cloudshell-gca 项目中启用，并且我没有
启用该 API 的权限。
agent-cli-10.png - 显示了点击后打开编辑器并要求参与者查看文件以了解 agent cli 创建的内容，并针对 agent cli 创建的每个文件提供了说明，详细信息请参阅文档
Playground 测试 - 在部署和发布之前提供这些步骤。
请参考这些图片来了解测试情况，并相应地创建说明
图片 - agent-cli-11.png 到 agent-cli-15.png
我尝试让代理 CLI 创建 Playground 并对其进行测试，但遇到了问题。
找不到会话：f681747b-c55d-42d6-9324-77f394d0ecb8。运行程序配置了应用名称“bumble_ops_assistant”，但根代理是从“/home/admin_/bumble-ops-assistant/app”加载的，这意味着应用名称为“app”。确保运行程序 app_name 与该目录匹配，或者在构建运行程序时显式传递 app_name。不匹配会导致 runner 无法找到会话。如需在会话缺失时自动创建会话，请在构建 runner 时将 auto_create_session 设置为 True。
在要求代理修复后，权限问题得到解决，大腿开始正常工作。
13. 部署并发布到 Gemini Enterprise [公开预览版]
我想使用自然语言部署和发布到 GE
因此，请保留手动方式和自然语言方式这两个选项
我要求部署代理，它将代理部署到了 Agent Engine。请参阅图片，了解相关步骤并创建相关说明
图片 - agent-cli-deploy-1.png 至 agent-cli-deploy-4.png
我让 Gemini CLI 发布到 GE 应用
我使用了 - 发布到 Gemini Enterprise 应用 bumble-workshop-lab-test-1_1778167389086
请参阅以下图片，了解这是如何完成的，并相应地创建说明
agent-cli-publish-1.png 到 agent-cli-publish-7.png