Adoption and productivity
User reports of adoption, productivity gains, shipped projects, cloud-agent usage, and changing engineers from coders into delegators and reviewers.
36.4%
Best tweets about Devin
Discover the best tweets about Devin AI, including software engineering tasks, coding workflows, benchmarks, product updates, team adoption, and limitations.
Cognition Devin software engineering agent capabilities, coding tasks, benchmarks, releases, adoption, reliability, limitations, and user evidence.
Original Xholic analysis
The supplied conversation presents Devin as a cloud-based engineering agent used for delegated implementation, testing, PR workflows, review, and multi-agent coordination. User reports are often positive, but the evidence also identifies setup demands, verification and review requirements, uneven task persistence, usage limits, and token-cost concerns. The supplied engagement outliers are concentrated in workflow, cloud-agent, and review/security posts.
66.7% of posts
All-time engagement
36.4% of posts
Published in 90 days
Conversation map
User reports of adoption, productivity gains, shipped projects, cloud-agent usage, and changing engineers from coders into delegators and reviewers.
36.4%
Reliability, autonomy, and agent-quality assessments, including persistence, self-verification, UX, responsiveness, and limitations.
30.3%
End-to-end implementation workflows: scoped tasks, coding, browser or device testing, CI, PR creation, merging, and delivery artifacts.
21.2%
Developer integrations and operating workflows spanning Linear, Slack, GitHub, MCPs, Playbooks, and agent management surfaces.
21.2%
Cloud-hosted Devin agents, including macOS environments, remote execution, private-network deployment, and cloud-first development workflows.
12.1%
Devin-assisted code review, security scanning, dependency-risk detection, GitHub-thread participation, and catching edge cases.
12.1%
Model, harness, and performance discussion, including SWE releases, inference speed, model comparisons, token limits, and context management.
12.1%
Multi-agent software factories where Devin orchestrates subagents, plans work from issue trackers, and executes parallel long-running tasks.
12.1%
Tone and stance
Performance benchmark
Posts with media make up 57.6% of this collection. Their median all-time score is 12.7, compared with 2.37 for text-only posts.
Format mix
Consensus and debate
Shared view
Posts describe end-to-end engineering workflows that combine implementation with testing, review artifacts, and PR-oriented completion criteria. Examples include browser testing and CI-gated merging, iOS testing with a recording and test report, and a multi-agent workflow requiring review, bug-bot checks, and recordings.
Shared view
Users and company posts present Devin as a review or defensive layer: reports cite edge cases, multi-file logic issues, and, in Cognition’s account, detection of the axios supply-chain attack for some customers before it was public.
Open debate
Assessments of reliability vary. One user praises Devin’s UX, another reports that it finds edge cases missed in review, while a third says the harness is not yet tenacious enough to inspire confidence that it will finish a task.
Open debate
Posts express both enthusiasm and concern about usage constraints. One user praises the removal of five-hour limits, another reports hitting GPT-5.5 limits in Devin Desktop, and a satirical post depicts a small feature consuming extensive agent and token usage.
What performs
The five supplied engagement outliers cover multi-agent orchestration, macOS cloud agents, security review, browser-testing delivery, and reflections on cloud-agent adoption. Their all-time scores range from 127.77 to 350.4, versus a supplied corpus median of 9.629.
According to the supplied analytics, 19 of 33 posts included media (57.6%). Their median all-time score was 12.671, compared with 2.37 for text-only posts.
Statistical standouts
Creator landscape
The five most represented creators account for 30.3% of the selected posts.
1. nader dabit
@dabit3
2 posts
2. Nicholas Charriere
@nichochar
2 posts
3. Ryan Carson
@ryancarson
2 posts
4. Scott Wu
@ScottWu46
2 posts
5. Vincent van der Meulen
@vinvan
2 posts
6. Walden
@walden_yan
2 posts
Ryan Carson describes running startup work through cloud agents, Slack, Linear, browser testing, CI, and merging. He argues that a pre-built orchestration product can provide most of the value for a startup without building an in-house agent platform.
Vincent van der Meulen describes a manager-agent pattern in which planned Linear work is dispatched to cloud subagents, with tests, review, recordings, and status updates used as completion checks. He also notes that this setup can create a review bottleneck.
Themes, sentiment, stance, and post format are classified per tweet. All counts, shares, medians, creator concentration, freshness, and performance comparisons are then calculated directly from the published snapshot.
Xholic's all-time score compares engagement while accounting for reach, post age, and creator consistency. It is used for relative comparisons within this collection.
This report analyzes the exact 33-post snapshot shown below. AI identifies editorial categories and drafts explanations; all statistics are calculated from the snapshot, and every narrative claim is checked against cited posts before publication.
Best Devin tweets
Ranked 01–33
@vinvan ·
fable produced 60+ (!) ready to merge prs for @mainframe overnight. here's how you can set up a software factory using fable as an orchestrator. prompt included! 1. narrate your *entire* todo list — everything that's top of mind — using dictation. i used @usemonologue and my prompt was ~10K words! you have to use voice because we want excruciating levels of detail. 2. locally, tell fable to plan all the work and put it in @linear. the goal is to make it such that a dumb model dropped in linear knows *exactly* what to do. aka all issues should have a clear DAG, plan, and optimize for max. parallelizability. i recommend running fable on high and having it fan out to codex subagents on xhigh (using the cc codex plugin.) to save usage. just make sure that fable itself is doing the architecture for the hardest issues! 3. now switch to @DevinAI. we'll use devin to run our factory because our orchestrator needs to be a cloud agent (it's going to run for a long time!), and be able to spin up other cloud subagents. 4. hook up the @linear @SlackHQ mcps. this will let your agents read the fable planned work, and communicate with you/your teammates. e.g. it can talk to your coworkers to make sure it's not stepping on anyone's feet! 5. a good feedback loop is *crucial.* before starting, make sure you have a bug bot (we use @cursor_ai.) and that your agents can test all its changes. e.g. we use the fantastic @limrun to make sure our agents can do ios development e2e. 6. create a devin ultra (fable) agent — this will be your orchestrator or 'middle manager.' we're going to tell it to look at linear and dispatch subagents for all tasks. the middle manager's goal is to keep spinning up subagents with the right level of intelligence until all the work is done. and keep all agents unblocked while you're sleeping, hanging out in the park, whatever! the reason the middle manager is able to orchestrate all of this is because fable planned everything in linear. and because the middle manager itself is also fable (contrary to most of its subagents.) 7. to prompt your middle manager, attach the middle manager prompt i'll post in the comments, modified for your repo. it's important that we *attach* the middle manager's prompt to our conversation vs. typing it out, so it never gets compacted. the middle manager's context window is holy. so our prompt tells it to spin up subagents — instead of doing things itself — for pretty much everything. 8. the prompt has some other cool, non-obvious details. firstly, every agent is told to keep working until it's met the burden of proof. in our case that's a (self)-review, bug bot being green, bug bot fixes being elegant, and a recording. we tell our middle manager to enforce this. secondly, we ask the middle manager to make sure linear stays up to date and communicate via the slack mcp. specifically, it should tag coworkers in slack whenever it has a question and post heartbeat updates in the eng channel. 9. your software factory is ready to go! in our case, it worked for 12+ hours without getting blocked. and produced extremely high quality prs. addendum: all of this is possible because with @AnthropicAI fable, models are finally smart enough to orchestrate/navigate large sets of work and their dependencies. and fable is a great software architect! now of course the 'downside' is that you're now review bottlenecked. we have 60+ PRs to review! but i think as an industry we should be able to come up with some innovation there. we'll certainly try our best to help here with @mainframe too! hope this is helpful! happy to answer any qs.
@dabit3 ·
You can't build iOS apps without a Mac, so we gave Devin one. Devin Cloud Agents now run macOS, with Xcode, iOS simulator, and your signing setup, all in a real macOS environment (with full computer use). In this demo, Devin builds a native iOS game, then plays and tests it with computer use. Devin then sends a screen recording of the gameplay along with a test report for my review. With @namespacelabs you get as many macOS environments as you'd like, configurable with many major versions of macOS operating system and Xcode.
@ScottWu46 ·
Devin Review caught the axios supply chain attack for multiple Cognition customers before the attack was publicly known. These attacks will be 10x more frequent in the age of AI; it is critical that repo maintainers start using AI for defense as well. (showing one example below where Devin Review caught the attack within an hour of its release - text minorly edited for anonymization)
@ryancarson ·
This is how I’m currently running my startup with @DevinAI + @openclaw The browser testing in Devin is mind-blowing. I was trying to duct tape and jerry-rig all this stuff together with Playwright + uploading videos to PRs and all sorts of stuff and Devin just does it all e2e. Wild. I didn't show how I'm using @linear, which I am using for issue tracking. I have a "land" skill that I tell Devin to use whenever all the browser testing is done and all the CI goes green and it just merges the PR
@vinvan ·
some reflections from solely using cloud agents this year: 1. every engineer should default to cloud. it completely changes how you view and use agents. if you run a company, it might be worth mandating everyone starts in cloud 2. cloud agent adoption has been much slower than i expected— e.g. looking at a ton of cursor profiles it’s clear majority cloud usage is still rare 3. getting your dx cloud agent ready still requires creative jiu jitsu. dev infra docs could be much better — “this is how to make our stuff accessible to agents/parallelizable.” luckily investments also benefit humans 4. it’s still a PITA to setup & manage cloud envs across cursor/devin etc. but i assume it’ll get bitter lessoned and we don’t need conventions for setup scripts etc. 5. where are the labs?! would love to see codex et al. invest more in their cloud experience. i know they can do it :) 6. it’s strange that cursor/devin’s investment in mobile apps lags behind their investment in cloud agents. they should go hand in hand. the ability to start agents from slack mobile isn’t enough! 7. a cloud agent spinning up other cloud agents (middle manager pattern) is goated. e.g. nice to go for a run, yap for twenty minutes, and end up with parallel agents. only devin supports this well 8. the uis of ADEs have somewhat adapted for cloud agents. but ui patterns for upcoming long running *and* proactive agents are understudied. super excited to see more experiments here (and will contribute) overall: i freaking love cloud agents. you’ll dissappoint me personally if next month you still spin up more local agents than cloud. very grateful for cursor and devin for making this technology so easy to use!
@cognition ·
Introducing Devin Outposts: run Devin on any machine. Your Mac mini, a GPU box in your lab, a VM inside your private network, or a Kubernetes cluster next to your internal services.
@ryancarson ·
I haven't typed `npm run dev` on my local machine for three days now and it's absolute bliss. Having my agents 100% in the cloud is a massive unlock. (One of those agents is openclaw, which is technically on my mbp in my office, but the only way I interact with it is via email/slack so it “feels” cloud) I'm able to run all the engineering and marketing for my startup through Slack and Linear and because of this the work product that I'm shipping has increased dramatically. I know all of us devs love creating our own custom solutions to this stuff but the truth is that creating an agent orchestration layer for your company or startup is a full-time job. Our job as startup founders is to be growing the company, not to be building out an agent orchestration custom platform. I think if you have a larger engineering team like Ramp, then it does make sense to build an entire layer like Inspect agent. However, I would venture to say that I'm getting most of the value by simply paying for a pre-built, battle-hardened solution like Devin. Again to be clear I'm not being paid by Devin or anybody to say these things, just my real-world experience using this stuff.
@AmOptimistShow ·
EPISODE 147: The New Era of Software Abundance @JTLonsdale visits @ScottWu46 & @russelljkaplan at @cognition HQ 00:00 Episode intro 01:35 Why technical talent & execution matters in AI 06:10 Do young people have an edge in the AI era? 08:26 Cognition's rapid growth 11:55 The new era of software abundance 14:30 Cognition engineers don't type code anymore 19:20 "Never sleep while Devin is idling" 21:25 The case for AI disinflation 23:50 How Devin generates 12X productivity gains 28:25 Cognition for government / taking on complex, broken systems 36:40 The AI race / competition with Anthropic 39:00 Forward deployed engineers? 43:40 How fast are LLMs improving? 47:10 The AI-led small business explosion
@dabit3 ·
New video — Devin in 8 Minutes Everything you need to know to integrate and build with @DevinAI remote agents. From creating and automating sessions to autofixing bugs, autoreviewing PRs, and connecting with Slack. Also covers: DeepWiki, Playbooks, and the MCP Marketplace.
@MollySOShea ·
BREAKING: Devin now writes ~95% of Devin's code Scott Wu (@ScottWu46), CEO of @cognition says the abundance era of AI is real & coming soon.. FULL INTERVIEW Cog Stats: › $2.5B raised, $26B valuation › $500M+ run rate, up from $37M LY › Customer usage is up 11x-12x in 6 months › Total code shipped inside Cognition has grown 7x › Devin writes ~95% of Cog's code, up from 89% at May Series D › The entire Windsurf acquisition was negotiated over 1 weekend, ~40 people buying a 200 person company with $82M of ARR › Goldman Sachs, Mercedes-Benz, Citi, Dell, Santander, NASA, the US Navy & the US Army all run Devin R I P : "The tokenmaxx era lasted from January to May of 2026, roughly." "I'm excited to have AI that allows me to spend all of my time & focus on the things that I care about & take care of the rest. I think the abundance era is real, & I think we'll be there pretty soon." Recorded 7 July 2026. On 23 July 2026 Cognition acquired Poke maker The Interaction Company 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) Scott Wu, Co-Founder & CEO at Cognition (01:00) The Identity crisis of building Devin (01:42) How Cognition 7X-ed its output in 6 months (02:55) The Metric every AI company gets wrong (04:18) Cognition's 12x growth curve (07:46) The Windsurf acquisition (13:26) Scaling overnight: Cognition's hardest week (15:11) The strategy behind the integration of Cognition products (17:23) Cognition's M&A playbook (20:01) Why the DMV is Cognition's next big target (22:59) Why Cognition bet against AI centralization (25:09) Why enterprises refuse to bet on a single AI lab (28:32) Scott's honest take on Superintelligence (32:36) Is Silicon Valley losing its mind over the AI gold rush? (33:26) Devin's origin story (37:17) The question Scott thinks nobody's asking yet (39:59) Poker with Peter Thiel & Napoleon ? (41:24) Scott's vision for the next year
@petergyang ·
"If you want to build great agents, you have to let the model cook." Here’s my new episode with @imjaredz (Builder in Residence at @cognition), where he shared what he learned from watching the best engineers build with AI agents, including: → Why fewer rules make agents work better → How to get agents to check their own work → Live demo: Build one agent to manage an agent team Some quotes from Jared: “Our goal is not for you to token max. Our goal is for you to ROI max.” “The trick is to break up the work to keep the context window small for each sub-agent.” “More Devin sessions now start from other Devins than directly from humans.” 📌 Watch now: https://t.co/jP1GoKtMnX Thanks to our sponsors: @RiversidedotFM: All-in-one AI studio for podcasts and video https://t.co/uWnS6aiMPE @WisprFlow: 4x faster than typing with your voice https://t.co/oqHJ8bN3ll
@andrewdfeldman ·
Developers deserve AI tools that don't make them wait. Cognition delivered just that. Congrats to @ScottWu46 and the entire @cognition team on the release of SWE-1.6. They both reduced bad model behaviors and dramatically increased good behaviors. Developers now stay in flow. With no waiting and no friction. Cognition were one of the first to see how important fast and frictionless inference would be for coding agents. We're proud to power SWE-1.6 together at 950 tokens per second on @cerebras. Programming at the speed of thought.
@peer_rich ·
at the start of this year i made a prediction: by the end of 2026 i wont be writing code by hand im already at 80% the remaining 20% feels more like habit than necessity the way i use AI for coding now is less like autocomplete and more like delegation i describe what i want, claude code or devin handles the implementation, i review that fundamentally changes what the job actually is the engineers who will be most valuable in 2 years will be the ones who think clearly about systems, catch bad output fast, and know when the AI is confidently wrong
@markfenner ·
Someone asked why I use both Hermes and Devin. Fair question. They don’t do the same job. Hermes is my daily driver. It runs the cron jobs, business ops, content workflows, study material, and all the work that needs to keep moving whether I’m at my desk or not. It’s the operating layer. @DevinAI is where the building happens. Repos, features, PRs, security scans. When something needs to be engineered, scoped, and shipped, that’s Devin’s lane. Hermes runs the operation. Devin handles the engineering. Beyond that, I’m just a tech kinda guy. I’ll use Codex, run local models, and test whatever interesting tool dropped that week. Could I force one tool to do everything? For sure . But, I don’t need to. I’ve tuned this setup around how I work, I enjoy using it, and it’s the most efficient version of my day I’ve found. I’m always curious how other people split this work. What does your setup look like?
@CodeByNZ ·
👀 Someone ran a head-to-head between GPT-5.6 Sol and Fable 5 on the same reasoning task. Both models were given the identical prompt: > GPT-5.6 Sol completed everything in 70 minutes (using Devin). > Fable 5 completed everything in 90 minutes (using Claude Code). Sol was noticeably faster in this test. The results have been getting some attention. Which model do you think performed better?
@ChaiWithJai ·
When I use Claude Code and Codex, its like I'm working for them because of so much steering needed. Devin feels like the first coding agent that works for me. Yesterday, I set up the sandbox environment and went to the beach and it knocked out 2 important design engineering challenges: 1. Bringing a semi-complex AI harness to life I teach critical thinking and AI skills to first-time entrepreneurs. And I want my learners to use a whiteboard to scaffold their thinking BEFORE and AFTER each AI session. My goal when teaching cognitive strategies is to allow my learners to walk away with a model of reality (i.e. mental model) that they continually test and update until it predictively explains and reconciles reality. 2. Re-design the homepage and get the core JTBD done working to onboard my first 10 users. Devin worked from 2 PM until 3 AM last night and I'm going to plan a longer retro to understand what I can rely on Devin for and what work I need to have ready for it for the application to go live. Today, I'm going to continue working on this first milestone of getting my first 10 users. My milestones are: a. Get 10 users b. Ensure the JTBD is complete for my AI World Cup Challenge c. Extend the web application into a mobile application and publish before NYC Tech Week (bonus): raise a round of funding so I can build Khan Academy for Adults I'm so happy to welcome Devin onboard to our team so I can fire myself as our engineer and get back to doing what I love, teaching. Teaching is the love of my life. @dabit3 and @cognition thank you, thank you, thank you so much. I really feel like my dreams are in reach. Its been less than 24 hours. And I want to wait to experiment more and distill why this feels so different. Stay tuned! Life is so rich, Jai P.S. I'm excited that I might have free time again! In which case, I'll be vlogging my experience trying to bring my dreams to life. What's your dogged pursuit?
@theinformation ·
Cognition is overhauling Windsurf into Devin Desktop, a hub where developers can manage AI coding agents from OpenAI, Anthropic and others. The strategy positions Cognition as a neutral platform in a market increasingly dominated by model providers. Full story: https://t.co/ZmPZ4t1PKJ
@boyuan_chen ·
Return on tokens is becoming a real product surface. Cognition says its typical customer saw agent usage grow 1000% in the last few months. It also announced an AI Productivity Guarantee, covering up to $10M in Devin usage if it does not deliver positive ROI. That framing is more interesting than the guarantee itself. Once agents move from experiment to daily engineering habit, the buyer starts asking different questions: How much token spend produced accepted work? How many retries were waste? Which tasks should use a cheaper model? How much human review was saved or added? Which failures created rollback risk? How do you convert time saved into dollars without lying to yourself? The winning coding-agent product has to run, explain, and account for the work. For enterprise agents, observability, evals, cost attribution, and reviewer trust are becoming the same system.
@ttunguz ·
For the last decade, the biggest line item in any startup’s R&D budget was predictable talent. But AI is pushing its way onto the P&L. How much should a startup spend on AI as a percentage of its research and development spend? 10%? 30%? 60? There are three factors to consider. First, the average salary for a software engineer in Silicon Valley. Second is the total cost of AI used by that engineer. Cursor is now at $200 per month for their Ultra Plan & reviews of Devin suggest $500 per month. Third, the number of agents an engineer can manage. A first pass : (first image) But the subscription costs are probably low. Over the last few days I’ve been playing around extensively with AI coding agents and I racked up a bill of $1,000 within the span of five days! 😳😅 So let’s update the table and assume another $1000 per month per engineer. So for a typical startup, an estimate of 10 to 15% of total R&D expense today might conceivably be used for AI. The variants will be much broader in practice as we all learn to use AI better and it penetrates more of the organization. Smaller companies that are AI native from the outset are likely to have significantly higher ratios. If you’re interested to participate in an anonymous survey, I will be publishing the results if the sample size is sufficiently large to have a statistically significant result. Survey is here : https://t.co/qeadHNSbMp This is a grossly simplified model where we are only reviewing salaries, not including benefits, hardware, dev & test infrastructure, etc. This is an estimate based on discounted personal experience vibe coding. https://t.co/tbC0lb0Qe2
Watch video
@nichochar ·
> need to build tiny feature (15 LOC) > ask Devin, gets to work > spins up a whole computer to test it with browser use, 500M tokens burned > works, submits to github > 5 other agents (codex, devin, cursor bugbot, etc...) all perform a review > for each comment, each bot polls and responds > small improvement found, Devin fixes it > round 2 of the five agents reviewing > tokens go brrrr > LGTM, merge > 2h, 1B tokens later, tiny feature shipped. is this agi?
@rwdaigle ·
If it's not clear from the recent slate of product announcements from Devin, Cursor, and Claude, the future of software development is: * Creating build loops * That can be run remotely and in parallel and * Automatically verified, reviewed, and summarized by agents You, the human engineer, must properly set up this loop and review high-level deliverables presented as screenshots, videos, and live URLs Notice that code is not part of this loop
@tristanbob ·
It's been a few months since I last used @DevinAI Desktop (formerly Windsurf). I'm using the "Adaptive" mode because I want my credits to be used as efficiently as possible. (BTW, I'm still using the grandfathered original plan from when Windsurf first became available!) First observation, it produces incredibly verbose thinking output. I love reading thinking about, but this was too much. You can see it repeating things, checking rules, correcting itself, etc. Second observation, it worked great! It pushed two PRs to an open source project after testing them locally. Have you tried Devin recently?
Best Tweets by Topic