Skip to main content
Introducing TSK-1Introducing TSK-1·Taskade's intelligence layer.
taskade
Create
Connect
Clone
PricingHelpDashboard →Dashboard →
PricingLoginSign up for free →Sign up for free →
Dashboard →Dashboard →
Sign up for free →Sign up for free →
Loved by 1M+ users·Hosting 150,000+ apps·Deploying 500K+ AI agents·Running 1M+ automations·Backed by Y Combinator·Powered by TSK-1
Taskade
AppsTSK-1AI ModelsBuilderPricingFeatures
See all▾
Contact usIntegrationsMCP ServerAgent skillllms.txtPressAboutConnectProductivityVideosReviewsFAQ
Learn
Taskade GenesisProjectsAI AgentsAutomationConnectorsVideo Tutorials
See all▾
Import & ExportSearch ArticlesAccount & Billing
App Factory
FeaturedDashboardsOperations
See all▾
CommerceFinanceSalesCRMsInventoryPortalsInvoicesBookingToolsCreators
Downloads
Mobile appsDesktop appsAndroid
See all▾
iOSMacWindowsChromeFirefoxEdge
Compare
vs Cursorvs Boltvs Lovable
See all▾
vs V0vs Windsurfvs Replitvs Emergentvs Devinvs Claude Codevs ChatGPTvs Claudevs Perplexityvs GitHub Copilotvs Figma AIvs Notionvs ClickUpvs Asanavs Mondayvs Trellovs Jiravs Linearvs Todoistvs Evernotevs Obsidianvs Airtablevs Basecampvs Mirovs Slackvs Bubblevs Retoolvs Webflowvs Framervs Softrvs Glidevs FlutterFlowvs Base44vs Adalovs Durablevs Gammavs Squarespacevs WordPressvs UI Bakeryvs Zapiervs Makevs n8nvs Jaspervs Copy.aivs Writervs Rytrvs Manusvs Crewvs Lindyvs Relevance AIvs Wrikevs Smartsheetvs Monday Magicvs Codavs TickTickvs Any.dovs Thingsvs OmniFocusvs MeisterTaskvs Teamworkvs Workfrontvs Bitrix24vs Process Streetvs Toggl Planvs Motionvs Momentumvs Habiticavs Zenkitvs Google Docsvs Google Keepvs Google Tasksvs Microsoft Teamsvs Dropbox Papervs Quipvs Roam Researchvs Logseqvs Memvs WorkFlowyvs Dynalistvs XMindvs Whimsicalvs Zoomvs Remember The Milkvs Wunderlist
AI Agents
FeaturedProject ManagementProductivity
See all▾
MarketingTranslatorContentWorkflowResearchPersonalOperations IntelligenceSalesSocial MediaTo-Do ListCRMTask AutomationCoachingCreativityTask ManagementBrandingFinanceLearning and DevelopmentBusinessCommunity ManagementMeetingsAnalyticsDigital AdvertisingContent CurationKnowledge ManagementProduct DevelopmentPublic RelationsProgrammingHuman ResourcesE-CommerceEducationLegalEmailSEODeveloperVideo ProductionDesignFlowchartDataPromptNonprofitAssistantsTeamsCustomer ServiceTrainingTravel PlanningUML DiagramER DiagramMath TutorLanguage LearningCode ReviewerLogo DesignerUI WireframeFitness CoachLead EnrichmentFounder OSSales DevelopmentBookkeepingRecruitingWebsite MonitoringField ServiceLicensingAll Categories
Automations
FeaturedAI Workflow AutomationLogic Automations
See all▾
AI Agent AutomationTrigger AutomationsAgentic Process AutomationAction AutomationsAI Models in WorkflowsAgentic AutomationMulti-Agent AutomationSocial MediaBusiness-in-a-BoxOperations IntelligenceInvestor OperationsEducation & LearningHealthcare & ClinicsReal EstateStripeSalesHR & People OpsField Service & DispatchRenewals & LicensesE-commerceContentMarketingEmailCustomer SupportHubSpotProject ManagementAgentic WorkflowsAppointment SchedulingCalendarReportsSlackWebsiteFormTaskWeb ScrapingWeb SearchChatGPTText to ActionYouTubeLinkedInX (Twitter)GitHubDiscordMicrosoft TeamsWebflowIndustry News & RSS FeedsGoogle WorkspaceManufacturing & OperationsAI Agent TeamsNotion AutomationsProposalBookkeeping & ExpensesClient OnboardingGoogle SheetsGoogle DriveGoogle CalendarGoogle FormsShopifyAsanaAirtableTrelloTodoistMailchimpClickUpGoogle DocsGmailGoogle TasksJiraLinearMicrosoft OutlookTelegramCalendlyTypeformSalesforceMonday.comTwilioWhatsApp BusinessWordPressZoomHTTP and WebhooksMCP AutomationFacebook PagesRedditApolloPipedriveFigmaAttioBrevoCal.comConfluenceHighLeveliCal FeedJotformOutlook CalendarMicrosoft To DoPushoverResendSendGridSMTPSupabaseTallyAll Categories
Prompts
Client PortalsDocument IntakeField Service
See all▾
Operations IntelligenceCRMAdvertisingDesignInvoicing and PaymentsSocial MediaQuotes and EstimatesCalculatorsCodingBooking and SchedulingConsultingCustomer SupportComplianceTime TrackingRetail OperationsSaaS and SubscriptionsInsuranceGovernance and OversightNonprofitPatient IntakeBlog WritingBrandingPersonal FinanceHuman ResourcesPublic RelationsTeam CollaborationProduct ManagementSupportAgencyReal EstateMarketingResearchSalesCopywritingContentProject ManagementWebsite CreationStrategyE-commerceEngineeringSEOEducationEmail MarketingUX/UIProductivityInfluencer MarketingAnalyticsEntrepreneurshipLegalVibe CodingRecruitingAll Categories
Templates
FeaturedChatGPTTable
See all▾
PersonalProject ManagementSalesFlowchartTask ManagementEngineeringOperations IntelligenceInventory ManagementEducationDesignTo-Do ListMarketingMind MapGantt ChartOrganizationalPlanningMeetingsTeam ManagementStrategyGamingProductionProduct ManagementStartupRemote WorkY CombinatorRoadmapCustomer ServiceLegalEmailBudgetsContentConsultingE-CommerceStandard Operating Procedure (SOP)Human ResourcesProgrammingMaintenanceCoachingSocial MediaHow-TosResearchMusicTrip PlanningCRMClient OnboardingEmployee OnboardingSOPBug TrackerRecruitment TrackerFormSales PipelineContent CalendarMarketing PlanProduct RoadmapBusiness PlanSWOT Analysis30-60-90 Day PlanInterviewNotion AlternativeKPIStrategic PlanMeeting AgendaInvoiceRisk RegisterIT Asset ManagementKanban BoardChange ManagementCommunication PlanRFPScope of WorkStatement of WorkHelpdeskKnowledge BaseCreative BriefGoal SettingExecutive SummaryGap AnalysisBooking SystemEvent ManagementPortfolio TrackerCustomer Onboarding PortalsClient PortalAgency OperationsFinance TrackingAll Categories
Generators
AI SoftwareNo-Code AI AppAI App
See all▾
AI WebsiteAI DashboardAI FinanceAI Operations IntelligenceAI FormAI AgentAI Client Portal BuilderAI WorkspaceAI ProductivityAI To-Do ListAI WorkflowsAI EducationAI Mind MapsAI FlowchartAI Scrum Project ManagementAI Agile Project ManagementAI MarketingAI Project ManagementAI Social Media ManagementAI BloggingAI Agency WorkflowsAI ContentAI Software DevelopmentAI MeetingAI PersonasAI Outline GeneratorAI SalesAI ProgrammingAI DesignAI FreelancingAI ResumeAI Human ResourceAI SOPAI E-CommerceAI EmailAI Public RelationsAI InfluencersAI Content CreatorsAI Customer ServiceAI BusinessAI PromptsAI Tool BuilderAI SEOAI Gantt ChartAI CalendarsAI BoardAI TableAI ResearchAI LegalAI ProposalAI Video ProductionAI Health and WellnessAI WritingAI PublishingAI NonprofitAI DataAI Event PlanningAI Game DevelopmentAI Project Management AgentAI Productivity AgentAI Marketing AgentAI Personal AgentAI Business and Work AgentAI Education and Learning AgentAI Task Management AgentAI Customer Relations AgentAI Programming AgentAI SchemaAI Business PlanAI Pitch DeckAI InvoiceAI Lesson PlanAI Social Media CalendarAI API DocumentationAI Database SchemaAI Marketing PlanAI Sales Pipeline GeneratorAI Course BuilderInternal ToolsBooking SystemReal Estate CRMInventory ManagementAI CRM BuilderAI TimesheetAI DispatchAI NewsletterAI Clinic OperationsAI Directory BuilderAll Categories
Taskade AI
Video GuideAI App BuilderVibe Coding
See all▾
Agent BuilderDashboard BuilderCRM BuilderWebsite BuilderForm BuilderWorkflow AutomationWorkflow BuilderBusiness-in-a-BoxAI for MarketingAI for Developers
Converters
AI Featured ConvertersAI PDF ConvertersAI CSV Converters
See all▾
AI Markdown ConvertersAI Prompt to App ConvertersAI Data to Dashboard ConvertersAI Workflow to App ConvertersAI Idea to App ConvertersAI Flowcharts ConvertersAI Mind Map ConvertersAI Text ConvertersAI YouTube ConvertersAI Knowledge ConvertersAI Spreadsheet ConvertersAI Email ConvertersAI Web Page ConvertersAI Video ConvertersAI Coding ConvertersAI Task ConvertersAI Kanban Board ConvertersAI Notes ConvertersAI Education ConvertersAI Language TranslatorsAI Business → Backend App ConvertersAI File → App ConvertersAI SOP → Workflow App ConvertersAI Portal → App ConvertersAI Form → App ConvertersAI Schedule → Booking App ConvertersAI Metrics → Dashboard ConvertersAI Game → Playable App ConvertersAI Catalog → Directory App ConvertersAI Creative → Studio App ConvertersAI Agent → Agent App ConvertersAI Audio ConvertersAI DOCX ConvertersAI EPUB ConvertersAI Image ConvertersAI Resume & Career ConvertersAI Presentation ConvertersAI PDF to Spreadsheet ConvertersAI PDF to Database ConvertersAI PDF to Quiz ConvertersAI Image to Notes ConvertersAI Audio to Notes ConvertersAI Email to Tasks ConvertersAI CSV to Dashboard ConvertersAI YouTube to Flashcards ConvertersURL to NotesVideo → SummaryAI Receipts to Expense Tracker ConvertersAI Docs to Knowledge Base ConvertersAI Form to Client Portal ConvertersSpreadsheet to CRMAll Categories
Wiki
AI Agent ExamplesLiving DNAAutonomous Workspaces, Agents & Apps
See all▾
Taskade GenesisAI AgentsAutomationProjectsQuantum AI & Taskade Genesis QuantumFoundations: The Theory Under Modern AICognitive Science: Mind, Brain and AIPlatformAI InfrastructureIntegrationsProductivityMethodsProject ManagementAgileScrumAI ConceptsCommunityTerminologyFeatures
Docs
Getting StartedREST APIAction API
See all▾
MCP ServersGuides & SDKModels
Blog
Introducing Taskade App Factory (November 2026)What Is an AI Employee? Roles, Costs, Risks and How to Hire Your First One (2026)How to Build an AI Support Agent for Your Website (2026)
See all▾
Residual Connections Explained: How ResNet's Skip Connections Made Deep Learning Deep (2026)AI Typography Tools 2026: 14 Font, Pairing and CSS ToolsWhy AI Agents Need an Ontology: The Write Path Nobody Talks About (2026)Browser Agents Explained: How AI Agents Use the Web in 2026Your Business. Your Software. (November 2026)Open Knowledge Format (OKF) Explained (2026): Every Rule in Google's Spec for Agent-Readable KnowledgeHistory of Microsoft Copilot: Clippy to Agents (2026)Is Taste the New Moat? What Still Defends Software When AI Builds Everything (2026)How to Build a Safety and Compliance Tracker Without Code (2026)History of Clay.com: From a Spreadsheet to a $7.1B GTM Platform (2017 to 2026)What Is x402? The HTTP 402 Payment Protocol for AI Agents, Explained (2026)How to Build an AI Lead Qualification Agent (No Code, 2026)LLM Wiki Explained (2026): Karpathy's Pattern, Google's OKF, and When a Folder Beats RAGWhat Is Spec-Driven Development? Tools and Evidence (2026)The Workspace Is the Runtime: What AI Agents Need After the Prompt (2026)Best AI Story Games 2026: 20 Tools to Play, Write, BuildIntroducing Taskade TSK-1: The System Kernel Behind Every App (2026)Run Your Whole Business in One App with Taskade Genesis (June 2026)
AIAutomationProductivityProject ManagementRemote WorkStartupsKnowledge ManagementCollaborative WorkUpdates
Changelog
New Automation Triggers & Row Totals in Taskade EVE (Nov 16, 2026)Read PDFs in Taskade & File Previews in Chat (Nov 14, 2026)Approve From Activity & Steadier App Kit Copies (Nov 13, 2026)
See all▾
Locked List Alerts & Safer Published Apps (Nov 12, 2026)Automation Setup Checklist & PayPal Signature Checks (Nov 11, 2026)One-Click App Connections & Date Fields Over MCP (Nov 10, 2026)Public Agent Chat Privacy & Cleaner Kit Copies (Nov 9, 2026)
Integrations
Slack AutomationGmail AutomationGoogle Sheets Automation
See all▾
Google Calendar AutomationGoogle Drive AutomationHubSpot AutomationStripe AutomationDiscord AutomationGitHub AutomationNotionYouTube AutomationZapier
© 2026 TASKCADE INC.
PrivacyTermsSecurity
Made withTaskade AIforBuilders
BlogAITasks That Cascade: Ten Years…

Tasks That Cascade: Ten Years of Building a To-Do List

The commit that made our to-do list work was titled "Able to recursively render nodes." A short history of the to-do list, and ten years of building one.

Katsushika Hokusai's Kirifuri Waterfall at Kurokami Mountain, about 1832: one source splitting into dozens of streams as pilgrims watch from below. The Metropolitan Museum of Art, public domain (CC0)
October 7, 2026Updated October 16, 202616 min readJohn XieAI#taskade-history#task-management#history-of-to-do-lists
On this page (12)
The cascade was the data structureA short history of the to-do listEvery homepage is a betTen years in five erasWhat "execution" means nowMeasuring what finishesWhat Bill Atkinson taught usWhat we got wrong, and what is still openTen years in numbersThe bottom of the cascadeDates and sourcesFrequently Asked Questions

In October 2016, the commit that made our to-do list work was titled "Able to recursively render nodes." A task was a node. A node could hold more nodes. The editor drew the list by calling itself, one level at a time, until it reached the thing you were supposed to do next.

We called the project Taskcade: tasks that cascade. Three months later a search-and-replace dropped the "c," and the product became Taskade. The company never changed its papers, so the legal entity is still TASKCADE INC.

This is a look back at ten years of building that tree, and at the two and a half centuries of to-do lists that came before it. The short version: nearly every task tool ever made, from Benjamin Franklin's daily schedule to the cloud apps of the 2010s, solved the same half of the problem. They helped a person decide what to do. Then the person did it. What changed in the last three years is that software can now do some of the second half. What has not changed enough is how often it gets that half wrong, and I will try to be specific about that too.

Katsushika Hokusai, Kirifuri Waterfall at Kurokami Mountain in Shimotsuke, about 1832, woodblock print with one waterfall branching into many streams above three pilgrims
Katsushika Hokusai, Kirifuri Waterfall at Kurokami Mountain in Shimotsuke, about 1832. The Metropolitan Museum of Art, via Wikimedia Commons, public domain (CC0).

The print above is the picture I had in my head. One source at the top breaks into dozens of streams, and at the bottom three travelers stand and watch the water arrive. That is a task list in 2016: a beautiful structure, with people at the bottom doing the walking.

The cascade was the data structure

The name was never a metaphor we added later. The first commit landed on September 26, 2016, a Redux starter project from my co-founder Dionis Loire. On October 6, Dionis titled the README "Taskcade." The early commits read like a spec: "An initial implementation of the data structure," then, on October 24, "Able to recursively render nodes." Dionis and our third co-founder, Stan Chang, wrote all of the first few hundred commits.

In January 2017 the site title read "Taskcade: Free To Do List and Task Manager." On January 24 it became Taskade. Why drop the "c"? The honest answer is the boring one: Taskade was easier to say, easier to spell, and easier to find.

Five months later, someone else arrived at the same word on his own. Sam Rebelsky, who teaches computer science at Grinnell College, wrote a blog post about his Sunday afternoon: each task "leads to another task, which leads to another task. It's a cascade of tasks, or a taskcade, as I've come to call them." In a footnote he searched the word, found us, noted that we also own taskcade.com, and decided that his meaning was different from ours. (Rebelsky, 2017). He went on to use it as a verb: "My work is taskcading!"

Here is roughly what the tree looked like in our own workspace that year:

[ ] Launch Taskade
  ├─ [ ] Build the outline editor
  │    ├─ [x] Store tasks as a tree of nodes
  │    ├─ [x] Render nodes recursively
  │    └─ [ ] Sync edits between people live
  ├─ [ ] Ship the open beta
  │    └─ [ ] Write "Taskade is coming!"
  └─ [ ] Talk to every early user

An early Taskade document editor, a nested list of tasks that several people could edit at once

The tree had one property we cared about more than any other: several people could edit it at the same time. The three of us had worked remotely across time zones for years, and our tasks lived in five apps. We wanted one tree that everyone could see and change at once. The open beta was announced on December 5, 2017.

A short history of the to-do list

Task management is much older than software, and its history splits along two threads. The first is structure: how to break work into pieces and order them. The second is who does the work. Almost every tool on the list below improved the first thread and left the second one alone.

Year Milestone What it added What it left unsolved
1784 Franklin writes up his daily "Scheme of Employment" in his Autobiography (Project Gutenberg) A plan for every hour, opened with "What good shall I do this day?" Paper does not remind you
~1918 The Ivy Lee method (James Clear) Six tasks a day, ranked Priorities, but no structure
1954 Eisenhower on the urgent and the important (UCSB) A way to choose Still on paper
1968 Engelbart's NLS demo (Wikipedia) Lists that expand and collapse on a screen One lab, one machine
1983 Dave Winer's ThinkTank outliner (Wikipedia) Hierarchy on a personal computer Single user
1987 HyperCard by Bill Atkinson (our history) Anyone can build software Local, not networked
1988 Lotus Agenda (Wikipedia) Free-form personal data Hard to learn
2001 Getting Things Done by David Allen (our notes) Next actions and contexts A method, not a machine
2005–2011 Remember The Milk, Todoist, Asana, Trello Lists in the cloud, for teams People still do every step
2016 Notion 1.0, and our first Taskcade commit Blocks and live trees Structure without action
2022 ChatGPT (our history) Language as an interface Answers, not actions
2023 AutoGPT and the first agent loops (our history) Goals split into subtasks Unreliable on their own

Two caveats for the careful reader. The Ivy Lee method comes with a famous story, a consultant paid $25,000 by Charles Schwab after three months, and the story has probably been polished in the retelling. And Engelbart's demo was a lab system on a shared machine, not a product anyone could buy. Its outline editor still looks modern.

Read the right-hand column top to bottom and the pattern is plain. Each generation made the list better at telling you what to do next. None of them did it. Our longer histories of the to-do list and outliners trace the structure thread on its own.

Every homepage is a bet

The earliest tagline in our records is "Taskade - Get things done." from January 2017. The line I remember from our scratch pad went further: "from ideas to action, tasks to execution." No document from that time survives with it, so take it as my recollection, not a record.

The first half reached the homepage on August 19, 2020. The second half stayed a promise for years, because in 2016 software could hold a task but could not carry it out. You can watch that change in our homepage headline, which we rewrote at least eleven times:

Year Homepage headline What it promised
Jan 2017 "Taskcade: Free To Do List and Task Manager" A list
Feb 2017 "The easiest way to share your notes, ideas, and daily tasks" (Wayback) A shared list
Jan 2018 "Checklist, Outliner, Notepad, Free Online Live Editor" A live, multiplayer tree
2019 "The Unified Workspace" One place for team work
Aug 2020 "Map out your workflow, from ideas to action." (Wayback) Ideas become action
2021 "All-in-One Collaboration. Remote Team Workspace." Remote teams
Feb 2023 "A Second Brain for Your Teams" AI memory
May 2024 "Build Your AI Agent Workforce" Agents do steps
Oct 2025 "Your Second Brain, Alive." Memory that acts
May 2026 "The Execution Layer for Living Software" Tasks become results
Jun 2026 "Turn Business Processes Into Live Apps" A process becomes an app

Eleven headlines in ten years is not a sign of a team that knew exactly what it was building. Each one was a bet about what the product was, made with the information we had that year. Read in order, though, they drift in one direction: from a list, to a shared list, to a place, to ideas becoming action, to steps done by software.

Ten years in five eras

2016 to 2019: a live tree. The product was a shared tree of tasks. Our earliest archived newsletter, on August 7, 2018, shipped uploads, video and voice calls, due dates, and comments, because work was never only a list. Taskade 2.0 shipped on January 22, 2019. A month later, on February 19, you could switch the same tree between views, such as a list, an action view, and a mind map.

2019 to 2021: one workspace for remote teams. We joined Y Combinator in the Summer 2019 batch and announced a $5M seed round from Grishin Robotics and Y Combinator that October. TechCrunch called us "the love child of Notion, Slack and Asana," which was more colorful than our own pitch. In a March 31, 2020 newsletter, as offices closed, I wrote: "Despite our experience working remotely, we were frustrated about having to hack together multiple tools in order to get things done." On August 25, 2020, the Free plan dropped its project and collaborator limits. In 2021 "action" still meant people. The workspace got a team on the same page, and the team did every step.

2022 to 2024: a second pair of hands. Taskade AI launched on December 12, 2022, with commands like expand, rewrite, and summarize. AI agents entered beta in May 2023, and automations went live on January 29, 2024. This was the first time the bottom of the cascade changed. A task could be handed to something that was not a person. The hand-offs started small (draft this, summarize that) and grew (research this topic, sort these leads, send this update every Monday).

2025: the pieces connect. We had shipped projects, agents, and automations as separate tools, and users had to wire them together by hand. Taskade Genesis builds all of it from one prompt: the projects that hold the data, the agents that reason over it, the automations that act, and the interface people use. Taskade EVE, the builder agent, does the assembly. The preview newsletter drew a line back to 1987: "In 1987, HyperCard let anyone build software. In 2025, Taskade Genesis lets anyone build intelligent, connected systems." Our year-end letter compressed the idea into five words: "The loop is the product." The longer story of those 110 days is in The Product We Didn't Know We Were Building.

2026: a kernel with memory. Workspace Memory arrived in May. On July 8 we introduced TSK-1, a coordination layer that, by default, picks a model for each step of a build and connects it to the workspace's projects, agents, and automations. In August we started publishing a benchmark, which is the part of this story I trust least and like most.

What "execution" means now

In 2016, a task had two states: open and done. Today the same task has a path, and most of the path can run without anyone touching it. Here is one task, followed through an app built this way. A visitor fills in a client sign-up form:

Submits the sign-up form Saves the new client row New row starts an automation Ask the agent to score the lead Score and a one-line reason Writes the score back to the row Emails you only for strong leads Visitor Your App Projects - Memory Automations - Execution Agent - Intelligence You
Submits the sign-up form Saves the new client row New row starts an automation Ask the agent to score the lead Score and a one-line reason Writes the score back to the row Emails you only for strong leads Visitor Your App Projects - Memory Automations - Execution Agent - Intelligence You

The architecture underneath is a loop more than a pipeline. Memory feeds reasoning, reasoning triggers an action, and the action writes new memory for the next run:

┌──────────────┐     ┌────────────────┐    ┌──────────────┐
│ MEMORY       │────▶│ INTELLIGENCE   │───▶│ EXECUTION    │
│ projects,    │     │ agents         │    │ automations, │
│ fields, files│     │                │    │ integrations │
└──────▲───────┘     └────────────────┘    └──────┬───────┘
       │                                          │
       └──────────── results become memory ◀──────┘

We call this Workspace DNA. The name matters less than the design choice behind it: the agent and the automation read and write the same rows a person sees. If the agent scores a lead wrong, you can open the row, see the score and the reason, and fix it. That choice came straight from the 2016 tree. Everything sits on one shared structure, so a person can always inspect what the system did.

Measuring what finishes

Most AI benchmarks test what a model knows. We wanted to test what it finishes. The TSK-1 Benchmark gives each model the same real app request inside Taskade Genesis, then uses the finished app like a customer would: add records, change a setting, ask for one more feature. Each build earns a tier on four axes (Interface, Task, Memory, Adapt), rolled into a score out of 100.

The method has limits, and they belong next to the numbers. We ran 37 tests between July 30 and September 30, 2026, with one to three builds per model per test, so read the scores as directional, not precise. The requests are real app shapes, not a fixed public suite. And we sell a product that runs these models, so you have every reason to discount our grading. That is why every test, including every miss, is public.

Model family TSK Score Best for
GPT 88 Long, detailed requests, done fast
Claude 75 Polished apps that keep improving
DeepSeek 75 Leads on design
Kimi 75 Rich apps that need patience
Grok 75 Follow-up edits that land
GLM 63 Good judgment when details are unclear
Qwen 50 Long, detailed forms
Gemini 44 A fast-improving Google model

Scores as of October 2026. Equal scores share a rank. Claude and Gemini run on your own API key in automations, and Claude also runs in custom agents on Pro and up.

The misses teach more than the scores. In our newest test, on September 30, several models built the same family intake form: parents fill it in on a phone and add two to four photos, and a teacher sees every family on one page. Some builds worked end to end. One build's public assistant told a visitor a child's name. One wrote no app page within the 15-minute test limit. A model can write a correct-looking app and still fail the one thing the person asking cared about. You only find that out by using the app.

What Bill Atkinson taught us

Bill Atkinson's HyperCard, released in 1987, let people who were not programmers build their own software. Teachers, doctors, and kids made stacks. It is the closest ancestor of what we build now, and when Atkinson died in June 2025 I reread what he had said about it.

In 2002 he told Wired: "I have realized over time that I missed the mark with HyperCard. I grew up in a box-centric culture at Apple. If I'd grown up in a network-centric culture, like Sun, HyperCard might have been the first Web browser." And then: "I thought everyone connected was a pipe dream. Boy, was I wrong." (Wired, 2002)

We started from the opposite end by accident. In 2016 our first goal was a tree that many people could edit at once, so the network came before everything else. Three lessons from Atkinson still shape how we work:

  1. Let anyone build. If an app needs a developer to finish it, the tool has not done its job.
  2. Put it on the network from day one. A stack on a floppy disk is a beautiful dead end. Software that lives in a shared workspace keeps working after you close the tab.
  3. Sweat the details people touch every day. Andy Hertzfeld's story "Round Rects Are Everywhere!" tells how Steve Jobs walked Atkinson around the block, pointing out rounded rectangles on signs and windows, until Atkinson went back and made them draw fast on the original Macintosh. That story is why our benchmark opens every app and uses it, instead of reading a score.

Our longer HyperCard history covers the rest.

What we got wrong, and what is still open

Ten years is enough time to be wrong in public a few times. A partial list:

  1. We shipped the easy half first, for a long time. Capture and structure, the "ideas to action" half, was solid by 2020. For most of the decade we could not do the other half.
  2. We changed our story eleven times. Some of those headlines were right for their year. Some followed the vocabulary of the moment. The tree under them barely changed, and in hindsight the tree was the part worth talking about.
  3. A better model was never the whole answer. The first agent loops of 2023 broke goals into subtasks and then wandered off. What has helped us since is less about any one model and more about two habits: keep every step on shared state that a person can open, and test results by using them.
  4. Our records undercount our own early years. Our public changelog lists only landmark releases before 2023, so the early bars in the chart below are a floor.

What is still open, as of October 2026:

  • Memory that gets measurably better with every run. Agents and automations share one memory today. Showing that the memory makes the next run better, with numbers, is not done.
  • Longer work with less supervision. Scheduled and triggered work runs while you are away. Long, multi-step agent work still needs a person to check it.
  • Honest measurement at scale. One to three builds per model per test is a start. It is not a benchmark anyone outside should rely on alone.

Ten years in numbers

We have published more than 690 release notes on our public changelog and sent more than 260 newsletters. The release pace jumped in 2023, when AI work turned weekly releases into the normal rhythm.

2021 2022 2023 2024 2025 2026 YTD 0 50 100 150 200 250 Year Release notes Release notes on taskade.com/changelog, by year
2021 2022 2023 2024 2025 2026 YTD 0 50 100 150 200 250 Year Release notes Release notes on taskade.com/changelog, by year

Counted from the public changelog through October 6, 2026. Before 2023 the changelog lists only landmark releases, so read the early bars as a floor.

The bottom of the cascade

Ten years ago, the bottom of our cascade was a person with a list. Today it is a person with a system that can do some of the walking. The person is still the point. You decide what matters, you approve what ships, and you check the work, because the system is still wrong often enough that checking matters.

The tree from 2016 is still there, under everything, at taskade.com. The benchmark, with every miss, is at taskade.com/tsk.

Dates and sources

Fact Detail Source
First commit September 26, 2016 Codebase history
Original name Taskcade, "tasks that cascade," README title on October 6, 2016 Codebase history
Renamed Taskade, January 24, 2017 Codebase history
Legal entity TASKCADE INC. App Store listing
Co-founders John Xie (CEO), Stan Chang, Dionis Loire About Taskade, 2019 seed announcement
Open beta December 5, 2017 Taskade is coming!
Accelerator Y Combinator, Summer 2019 YC company page
Seed round $5M from Grishin Robotics and Y Combinator, October 2019 TechCrunch
Taskade 2.0 January 22, 2019 Changelog
Taskade AI December 12, 2022 Introducing Taskade AI
Automations live January 29, 2024 Newsletter archive
Taskade Genesis launch October 10, 2025 Introducing Taskade Genesis
TSK-1 July 8, 2026 Introducing TSK-1
TSK-1 Benchmark Public since August 2026 The TSK-1 Benchmark

For the full company profile, read What Is Taskade? The Complete History.

Frequently Asked Questions

What does the name Taskade mean?

Taskade began as Taskcade, a name built from task and cascade: one idea branches into tasks, each task into smaller tasks, the way a waterfall splits into streams. The first named version of the code was called taskcade in October 2016, and the product was renamed Taskade on January 24, 2017. The legal entity is still TASKCADE INC.

What was Taskade's original slogan?

The earliest documented tagline is "Taskade - Get things done." from January 2017. Co-founder John Xie remembers an early scratch-pad line, "From ideas to action, tasks to execution." The first half reached the homepage in August 2020 as "Map out your workflow, from ideas to action." The second half describes Taskade in 2026, when agents and automations carry a task all the way to a finished result.

What is the history of task management?

Task management began on paper: Benjamin Franklin's daily scheme in his autobiography, the Ivy Lee six-task method, and the Eisenhower urgent-versus-important idea. Software arrived with Douglas Engelbart's 1968 demo of collapsible lists, then outliners like ThinkTank in 1983, HyperCard in 1987, and Lotus Agenda in 1988. Web apps such as Remember The Milk, Todoist, Asana, Trello, and Notion followed. Since 2023, AI agents and automations have started to do the tasks, not only track them.

What does tasks to execution mean?

Tasks to execution means the software does not stop at tracking a task. In 2016 a person read the list and did the work. In 2026 a Taskade workspace can hold the task as memory, let an AI agent reason about it, let an automation act on it through 100+ integrations, and write the result back, so the task reaches a finished result.

View this page as Markdown

0%

On this page

The cascade was the data structureA short history of the to-do listEvery homepage is a betTen years in five erasWhat "execution" means nowMeasuring what finishesWhat Bill Atkinson taught usWhat we got wrong, and what is still openTen years in numbersThe bottom of the cascadeDates and sourcesFrequently Asked Questions

Related Articles

Leonardo da Vinci's Codex on the Flight of Birds, around 1505, open to pages of mirror-written notes and bird sketches, illustrating ideas captured in memory long before they turned into action
October 30, 2026AI

From Ideas to Action: Second Brain vs. AI Agents (2026)

Second brains got very good at remembering. The work still waited for us. A founder's essay on why memory should lead to...

How Taskade became Taskade Genesis: the 2019 AI workspace primitives (Projects, AI, Workflows, Workspace) evolving into Memory, Agents, Automations, and Apps, converging into Taskade Genesis and TSK-1
September 30, 2026AI

The Product We Didn't Know We Were Building: How Taskade Became Taskade Genesis (2026)

Taskade joined Y Combinator in 2019 as a collaborative workspace. We kept building projects, AI agents, automations, and...

Workspace-as-Runtime: coding agents have the repo, dev environment, and CI; everyone else needs the workspace, where memory, agents, automations, and apps run as one AI agent runtime
November 13, 2026AI

The Workspace Is the Runtime: What AI Agents Need After the Prompt (2026)

Coding agents have repositories, development environments, and CI. What is the equivalent for everyone else? The app is ...

How to build an app factory: a cloned Taskade App Kit with its projects, AI agent and automations in the side panel, and Taskade EVE ready to make it your own
November 5, 2026AI

How to Build an App Factory Without Code: The 2026 Guide

An app factory gives you a few apps that work your way, with no build from scratch. Clone an App Kit, give it a brain, m...

Human computers at work in the NACA High-Speed Flight Station computer room in 1949, when computer was a job title. Photo by NACA and NASA, public domain, via Wikimedia Commons
November 19, 2026AI

What Is an AI Employee? Roles, Costs, Risks and How to Hire Your First One (2026)

An AI employee is an AI agent with a role, memory, a schedule and a manager. See what one does, what it costs, what goes...

How to build an AI support agent for your website: a row of Chesapeake and Potomac Telephone Company operators at a switchboard in 1927, an early human handoff desk. Photo: U.S. National Archives (NARA 522875) via Wikimedia Commons, public domain
November 19, 2026AI

How to Build an AI Support Agent for Your Website (2026)

Put an AI support agent on your website that answers from your docs, hands hard questions to a person, and logs each han...

View All Articles