产品72°

Google 发布自改进 AI 智能体 Loop,可自主推进长期目标

精选理由

Google 新出的 Loop 智能体能自己盯 KPI、拆任务再动手写代码执行,集成了一百多个工具还能挂自定义 MCP。跟 Jules 只管写代码不同,它更像个长期运营助手,做产品增长和维护的开发团队可以先开个 Workspace 试试。

Google 宣布推出自改进 AI 智能体 Loop,内部代号 Jitro,与此前 Jules v2 的内部名称相同。它以 Workspace 为单位工作,用户连接 GitHub 项目并添加基本信息后,Loop 会自主分析项目细节,生成关于产品和产品指标的 Skills,这些 Skills 以 Markdown 形式存放在独立标签页中,可在 UI 里编辑。

正文

Loop 的核心机制是 "Loops":中长期的、可由代码实现的目标,例如 "Scale Telegram community contributions"。每个 Loop 会被拆解为子 KPI(如社区成员数、注册贡献者、活跃成员),在仪表板上展示进度状态;目标下方再分解为 Tasks,每个 Task 附带描述、标签和更新日期,并配有 Solutions(含 Impact、scope、Risk 标注)和 Evidence 标签页,Evidence 链接到 Loop 拉取上下文的来源。用户可从任务页直接启动方案开发,由 Gemini 执行实现。

上下文接入方面,Loop 支持 Integrations、Files、Links 和额外仓库,提供超过 100 个集成,包括 Jira、Linear、Datadog、Sentry、Notion、Snowflake、Salesforce、Intercom、Discord、Slack、Figma 等,并支持自定义 MCP。与 Jules 聚焦代码生成不同,Loop 面向持续运行的产品指标改进场景,把目标管理、证据溯源和 Gemini 执行放在同一工作流中,对需要长期运营自动化目标的开发者和产品团队有直接使用价值。

原文 · TestingCatalog

Google recently announced Loop, its new self-improving AI agent that can autonomously work toward a given goal.

Loop is internally called Jitro; interestingly, that was the exact name for Jules v2.

Here is how it works 👀

1. Users start creating a Workspace by connecting it to a selected Github project and adding basic information.

2. Users can create loops manually or select ones that are already predefined (ex., Harden Application Security)

"Custom Loops" can be created via a prompt or by manually filling in the Loop title, icon, and objective.

> "Loops are mid- to long-term objectives for Stitch Loop to continuously work toward. They can range from highly specific to broad, but should always be something code can achieve," says the description.

3. Users can connect additional context in the form of Integrations, Files, Links, or additional repositories.

More than 100 integrations are available there, including services like Jira, Linear, Datadog, Sentry, Notion, Snowflake, Salesforce, Intercom, Discord, Slack, Figma, and many others.

Custom MCPs are supported as well.

4. After creating a workspace, Loop will start digging into your project details and generate its own Skills about the product and product metrics.

These Skills will live in a separate tab and can be edited in the UI in Markdown.

5. When the Workspace is ready, Loop will suggest metrics and goals based on its own research. Users can convert these suggestions into loops right away.

When a Loop is created, it appears as a running process in the main UI.

6. When a Loop is finished, users will see a list of suggestions for every loop, along with a number associated with a target metric and progress status.

Example Loop: - Goal - Scale Telegram community contributions. - KPIs - community members, registered contributors, active members.

A high-level goal would be broken down into sub-KPIs. When users open a dedicated Loop page, all these KPIs will be visible on the dashboard.

Below, Users will see a list of Tasks, Skills, and Activity tabs.

Example Task: - Telegram channel lacks discussion threads and a dedicated bot.

Each task has a detailed description, labels, and the date when it was updated. Below, users will see tabs for Solutions, Activity, and Evidence.

Activity appears as a summary describing what happened, what was done, and the general Timeline.

Evidence contains links to where Loop pulled the context behind this Task. In my example case, it refers to the TestingCatalog website and the Telegram channel from which it pulled all the numbers.

Example Solution: - Dedicated Telegram Bot API intake bot with editorial triage webhook (implementation task).

This task is an implementation task that has a clear description, Impact, scope, and Risk labeled.

Users can start the task right from this page to begin solution development via Gemini.

When the task is done, users can review its progress and status and monitor its impact on production by pulling updated metrics and KPIs after the release.

What does all this mean? 🤯

Loop follows how "Product work" is done at Google, a model many other companies also use.

Every Workspace in Loop is equivalent to a scope that is normally handled by a complete product engineering team.

It is no longer a place where users play the role of engineering lead and product lead, orchestrating AI agents.

It is a place where the user plays the role of a senior manager managing several engineering teams, which is a big shift on its own.

We are slowly moving towards autonomous AI organizations. One management layer at a time.

I expect it will still take until 2027 for labs to develop the products and models needed to make substantial progress in this area (assuming AI continues to advance in a semi-regulated format as it is now).

Monitoring 🍿

产业坐标与信源核验

本条情报归属 AITOP「产品」核心栏目,重点聚焦北美前沿实验室与硅谷科技巨头。在跨区域产业观察坐标中,该动态直接关联「AI 开发者工具链、Coding Agent 与工程化实践」「中美大模型技术代差与商业化对照」研究主线,反映出当前技术演进与商业落地的最新风向。涉及核心实体与技术议题包括:Google、Loop、Gemini、Jules,读者可通过下方标签进入对应专题页查阅历史脉络与关联对比。

信源核验说明:本文原始线索采编自「TestingCatalog」(@testingcatalog),经 AITOP 多维评分管线结构化提炼。