swyx 转发 Devin 团队 @stevenkplus1 关于 Devin Bots 的技术细节,称其解决了跨会话上下文丢失问题。每个 Bot 拥有独立的记忆库和长期身份,不同 Bot 之间可按需通信,团队可为不同项目创建专属 Bot。作者称这是 Devin 发布两年来最大的工作方式变化,用户从委派任务转向委派目标与职责,并认为这几乎完全是编排层面的改动。
Devin 团队披露 Bots 的架构变化,读者可了解持久化记忆如何改变编码智能体的使用方式。
technical details:
inter-session context is surfaced by default. Teams now create dedicated bots for different projects; while these different devins can talk to each other when necessary, they each have their own individual memory bank and goals. Each bot now has its own, long lived identity. The transition from "Devin is a swarm of ephemeral agents" to "Devin is a collection of bots, each with their own persistent identity and memory" is changing how people use and prompt Devin.
https://x.com/stevenkplus1/status/2122761055588012112
【引用 @stevenkplus1】Bots are super cool and if you haven't used them yet, you absolutely must try them. Create a bot to manage a goal or a project that you'll work on across multiple sessions and days.
Some technical tidbits about the architecture and design:
Devin used to have a major UX problem: a session today doesn't remember exactly what happened in a session from a few days ago. It only has vague awareness of those previous sessions, and recalls only the nuggets of information that were explicitly persisted. This is because each new Devin was essentially an ephemeral clone of a base template. One symptom of this problem is that our users would reuse the same session instead of starting new ones, since they didn't want to lose context, and end up with tens or hundreds of PRs from a single session.
Bots almost completely solves this problem of context being lost between sessions, because now inter-session context is surfaced by default. Teams now create dedicated bots for different projects; while these different devins can talk to each other when necessary, they each have their own individual memory bank and goals. Each bot now has its own, long lived identity.
The transition from "Devin is a swarm of ephemeral agents" to "Devin is a collection of bots, each with their own persistent identity and memory" is changing how people use and prompt Devin. I see people investing much more in providing high level project context to their bot, and requiring fewer messages for each additional task since it already has a ton of background context on the project.
This is the most significant change to how Devin works since our original launch 2 years ago. And it in turn changes how you use Devin too: instead of delegating tasks, you should delegate goals and responsibilities to Devin.
It's crazy to think that all this happened because we changed how memories get persisted and retrieved. With each bot having its own memory bank, and a given org having hundreds or thousands of bots, we can now be much more aggressive in surfacing memories without worrying about polluting the agent's context with irrelevant memories. The even crazier part is that this is almost entirely an orchestration change, and that while model improvements played a role, we probably could've implemented this a year ago and observed similar effects.
Anyway -- we've come a long way from the retrieval and reranking strategies of 2024, and the result is Devin Bots -- probably the most ergonomic and futuristic UX for coding agents I've ever used.
Bots are super cool and if you haven't used them yet, you absolutely must try them. Create a bot to manage a goal or a project that you'll work on across multiple sessions and days. Some technical tidbits about the architecture and design: Devin used to have a major UX problem: a session today doesn't remember exactly what happened in a session from a few days ago. It only has vague awareness of those previous sessions, and recalls only the nuggets of information that were explicitly persisted. This is because each new Devin was essentially an ephemeral clone of a base template. One symptom of this problem is that our users would reuse the same session instead of starting new ones, since they didn't want to lose context, and end up with tens or hundreds of PRs from a single session. Bots almost completely solves this problem of context being lost between sessions, because now inter-session context is surfaced by default. Teams now create dedicated bots for different projects; while these different devins can talk to each other when necessary, they each have their own individual memory bank and goals. Each bot now has its own, long lived identity. The transition from "Devin is a swarm of ephemeral agents" to "Devin is a collection of bots, each with their own persistent identity and memory" is changing how people use and prompt Devin. I see people investing much more in providing high level project context to their bot, and requiring fewer messages for each additional task since it already has a ton of background context on the project. This is the most significant change to how Devin works since our original launch 2 years ago. And it in turn changes how you use Devin too: instead of delegating tasks, you should delegate goals and responsibilities to Devin. It's crazy to think that all this happened because we changed how memories get persisted and retrieved. With each bot having its own memory bank, and a given org having hundreds or thousands of bots, we can now be much more aggressive in surfacing memories without worrying about polluting the agent's context with irrelevant memories. The even crazier part is that this is almost entirely an orchestration change, and that while model improvements played a role, we probably could've implemented this a year ago and observed similar effects. Anyway -- we've come a long way from the retrieval and reranking strategies of 2024, and the result is Devin Bots -- probably the most ergonomic and futuristic UX for coding agents I've ever used.在 X 查看被引用的帖子
来源:swyx · x.com