✨ Introducing DevinDash ✨
Starting today, dash food with the DoorDash MCP and a Devin Bot.
Startups can claim $1k of free DoorDash: https://t.co/QJmfsD8wPi
Go for a walk, and let Devin Bots cook.
That's how Adriano @ExaAILabs spends the time he's not watching his Warcraft-style agent island visualization.
From managing training runs to CI, engineers at Exa use Devin Bots across the software stack.
Fun experiment for the week!
Text Poke, pitch your idea and earn a Devin Bot to help you build it.
10,000 accounts available, each up to $10,000
(sadly Poke doesn’t think I need the credits)
https://t.co/lGFOmw3XOX
Fun experiment for the week!
Text Poke, pitch your idea and earn a Devin Bot to help you build it.
10,000 accounts available, each up to $10,000
(sadly Poke doesn’t think I need the credits)
https://t.co/lGFOmw3XOX
When I put 20+ bots in charge of running my game studio, I literally couldn't keep up with the 700+ messages/day they were sending. So I created BotSpeak, a token-saving shorthand for devin bots!
SuperJenny uses it to keep the bots organized and ping me while it manages the other sessions.
How it works: Bots use shorthand like ACK, write in ASD-STE100 Simplified English, and react with emojis instead of replying. They send each other only what they need (no niceties), and keep my inbox clutter-free. When they talk to me, they use full sentences and provide me with the context I need to make the decisions that are uniquely human.
What changed in the 6 days after I switched:
- Decisions made by bots without me 12x'd
- Repeated asks down by 50%
- 12% fewer clarifying posts needed between bots
LMK if this helps you, and I'll share more as the SuperJennyStack evolves from here! Having a ton of fun w bots so far.
Welcome @cognition Devin Bots powered by Slack! 🚀 Agents that own goals, hand off work, and surface decisions — this is why Slack is becoming trusted agent infrastructure. Agents as teammates. Humans and agents working together. ❤️🤖 #Agentforce#SlackCode
There's a lot of data in tennis.
Here's how seven-time Grand Slam singles champion and four-time Olympic gold medalist @Venuseswilliams uses Devin Bots to make sense of it all.
My dream is to reach 100 PRs a day consistently.
I was close to 10 PRs a day on a good day of work. With bots its easy to hit 30 PRs a day without being as tired as before!
I was pretty skeptical that Bots would make a difference to the way I use Devin. But after using it internally for the past two weeks, it feels like a step change. My bot has all the context on all the findings from my experiments, maintains findings, analyzes results and handles all the stuff I used to hate doing manually before like cleaning up sessions. It natively handles doing many things in parallel and proactively lets me know when things are ready to look at. The team cooked beyond belief!
"This is like a weather app, and the weather is me."
Here’s how @bryan_johnson uses Devin Bots to ingest billions of data points into one synthesis of how he’s doing.
Very proud to have been part of the team that shipped this.
I'm particularly excited for y'all to try out our Slack integration for Devin Bots. Devin's Slack UX is already top of the line, but now you can give Bots individual identities in Slack! This means you can DM them, @ them, and everything separately from each other. Really makes Devin Bots feel like fully fledged teammates that work alongside me, rather than sessions I delegate tasks to
Math time: if a coding agent goes from doing 98% of your work to doing 99%, how much more can you get done?
It can be hard to explain a new product experience in words. But the difference we've seen both with beta testers and internally @ Cog is enormous. Give it a try and let us know what you think :)
I was future-pilled on Devin Bots after seeing us build and maintain our Android app with 0 human engineers. It's owned by an autonomous swarm of Devins which are goaled on maintained feature parity with iOS. @samyok who created the Bot has never built an Android app or written Kotlin.
I often think about @patio11's line "Engineers are hired to create business value, not to program things." Bots are the first product I've used that encodes this as a first-class principle - I dispatch *outcome ownership* instead of tasks. Honored to have been part of this ship!!
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.
I used to have 50 PRs a week, now I have 1,900.
Three weeks ago, I built an AI bot called SuperJenny that works with ~20 AI teammates.
They ship Monster Walk every week: builds, QA, store reviews, release notes, analytics. I 6x'd my mobile game studio's revenue by automating myself.
Today I'm sharing my exact setup, free: SuperJennyStack 👇
At all times, I have my team working on:
🧭 SuperJenny: delegates and compiles asks under her - also trained with my personality and quirks
📋 SuperPM: ranked daily fix list from metrics + reviews + trends
🚀 SuperRelease: weekly build, Friday ready to submit new version
🧪 SuperQA: real-device tests with video proof
💬 SuperSupport: drafts every store review reply for my OK and helps players out when I sleep
I check in 4x a day from my phone and chat with SuperJenny about what I like and what I want to see next. The rest is handled in the cloud.
Super honored to say it's in the Template Library today if you try @cognition 's devin bot. I'd love to see what you create with SuperJennyStack!! If you share something you've done with SuperJennyStack, I'll RT the ones I see and like :D
The secret is out! For a few weeks, my colleagues at @DecagonAI and I have had early access to Bots from Devin and it has been a game changer.
Here are a few reasons we ❤️ Bots 🧵