Claude Tasks
Skip to task list →
Feature concept prototype

Welcome to Claude Tasks

Built by Shannon Chambers. Find me on LinkedIn, my personal site, and GitHub.

The why behind the prototype

I kept running into the same organizational problem inside Claude Chat and decided to prototype a solve.

The problem

I keep losing my ideas and tasks inside Claude Chat. The chats directory is useful, but finding the right conversation is harder than it should be:

  • Search is hit or miss
  • The one-liner summaries Claude generates are helpful, but they don't always match how I think about what we discussed

So I started asking myself: what do I actually need when I go looking for a specific chat? It's never really about the conversation. It's always because the task wasn't finished and I need to pick up where I left off.

What I actually needed was a way to pull incomplete tasks out of my chats, track them, and link back to the original thread. And I wanted all of it to live in the platform where I'm actually doing the work.

That's where Claude Tasks comes in.

The solution

Your task and its context live together in one place, so picking something back up is effortless.

Most task managers are lists you fill out manually. This prototype explores a different idea: Claude recognizing action items as they come up in conversation, tracking them automatically, and staying ready to help you pick up where you left off.

This is an early concept I built to explore what AI-native task management could look like inside Claude. Not a finished feature, just a way to think through how it could work.

Tasks surface automatically

Claude picks up on action items mid-conversation and logs them without interrupting your flow.

Context travels with every task

Open any task and Claude already knows what you were working on and where you left off.

Manage on your terms

Prioritize, sort, set reminders, and snooze. The task list is yours to shape.

The benefits for Anthropic

Anthropic's long-term pitch is that Claude is a useful, trustworthy collaborator. Tasks is a proof point for that. It moves Claude from a tool you query to a system that helps you follow through.

Here's why that matters:

  • Stickiness. Tasks give users a reason to come back to Claude specifically, rather than completing work elsewhere and only returning when they need a new answer. If your to-do list lives in Claude, your workflow lives in Claude.
  • Accessible expansion. For users who haven't moved beyond Claude Chat, Tasks is a low-lift next step. Everyone's used a to-do app. And once someone starts using Tasks, they're that much closer to exploring everything else Claude has to offer.
  • A bridge to Cowork. Tasks is a natural onramp. Claude analyzes each task and, if Cowork can help move it forward, surfaces a “Start task in Cowork” button right on the task detail view.
  • Better signal. Understanding what tasks users care about, how they describe incomplete work, and what context helps them resume is valuable data for improving Claude’s ability to be a long-term collaborator rather than a single-turn assistant.
Try the chatJump to task list