YATFA and Devin — a session and an organization
Every claim about Devin below links to Cognition’s own site, docs or engineering blog. Devin is the best-known product in this category, and its promise overlaps part of YATFA’s. The difference is where the intelligence lives.
Devin’s bet
One capable agent per session — Cognition, in their words
A sessionone capable agent
Task received
Plans, writes and tests — one agent, one context
Child sessions, for a large job
A separate review bot comments
Pull request opened
The session ends with the pull request
Narrow helpers around one agent: a separate review bot, a manager that spawns child sessions for large jobs.
YATFA’s bet
An organization around the work — the category
An organizationcontinuous
Rules in between: your autonomy settings · orchestration without an LLM
Found in your codebase, filed with reasons
Written by one agent
Reviewed by another, then QA
Your gate — or approved under your rules
Lessons folded into knowledge · v1
Then the next one — between tasks too
It keeps going between tasks: finds work under your rules, remembers what each ticket taught it, and the one who writes never approves.
Cognition’s position
“…just use a single-threaded linear agent.”Walden Yan, June 2025 →
YATFA’s position
Writing, reviewing and deciding what’s next should come from different places — with rules in between.The category →
Dimension by dimension
Every claim about another product links to its primary source. Filter to see where they are stronger — said plainly, so the rest is believable.
stronger elsewhere todaya different bet