Asana tracks the work. Cedric keeps it current.

Cedric is your Asana AI agent. He checks in with the people the tasks are assigned to, updates Asana from their answers, and tells you what changed before every meeting.

Works in

No credit card required. Every change to Asana follows a yes.

Created and used by people from

DeskimoAmazonMicrosoftGoldman SachsUBSY CombinatorRocket InternetETH ZürichEPFLCartierfoodpandaLazadaUniversity of St. Gallen

The work gets done. Asana doesn't hear about it.

Tasks are finished in a doc, a call or a pull request, and nobody goes back to tick them. Due dates pass quietly. Soon the project view says one thing and the team says another. Cedric makes the updating his job.

Asana

Asana tracks the work.

Cedric

Cedric keeps it current.

How Asana stays current.

1. Connect Asana and name your projects

CedricAPP8:40

Asana is connected. Which project should I keep current?

Launch planWebsite redesignHiring

22 tasks, 5 assignees. First check-in tomorrow at 9:00.

One click connects Asana. Cedric reads the project you name and learns who is assigned what.

2. Cedric checks in with the assignees

CedricAPP9:02

The app store screenshots were due yesterday. What's the status?

CompletedRunning late
CedricAPP9:02

Thanks. Marked complete in Asana.

A direct message with one-tap answers, when a due date passes or a task goes quiet.

3. Review the suggested changes

CedricAPP9:10

Three things in Launch plan no longer match this week's threads.

AsanaRelease notes to completeApproveEditReject
AsanaPricing page copy, due ThursdayApproveEditReject
AsanaSupport macros, assign FelixApproveEditReject

What Cedric infers from threads and calls comes to you first. Approve, edit or reject each change.

4. Asana is current, and the team is briefed

CedricAPP10:30

Launch sync in 30 minutes. Since last week:

AsanaFour tasks changedupdated
AsanaBeta invite emailsblocked on the list
AsanaSupport macrosno answer

Before the meeting, everyone gets what changed, what is blocked and what is still open.

Skip the status round.

On Monday morning Cedric asks each assignee about their open tasks. Their answers update Asana, and the brief lands in the channel before the sync: what changed, what is blocked, who has not answered.

The meeting starts at the decisions, with a project view everyone believes.

What Cedric does in Asana.

Ask the assignee, update the task

When a task passes its due date, Cedric asks the person it is assigned to. One tap answers, and Asana changes to match.

  • Spot overdue tasks
  • Spot tasks with no activity
  • Message the assignee directly
  • Answers in one tap
  • Mark complete, or reschedule
  • Run every morning, or before a meeting

@Cedric Every morning, check with assignees on anything overdue in Launch plan and update it.

CedricAPP9:02

Pricing page copy is due today. What's the status?

CompletedRunning late

New date?

TomorrowThursdayNext week

Rescheduled to Thursday in Asana. Hannah will see it in the brief.

Suggested changes, one review

Cedric reads the channel, the calls and the answers, and proposes the edits your project is missing.

  • Tasks that are already done
  • New due dates
  • Tasks with no assignee
  • Tasks nobody created
  • Custom fields that went stale
  • Approve one, or all at once

@Cedric What in Launch plan no longer matches what we said this week?

Launch plan
ListBoardTimelineCalendar
Task nameDue dateStatus
Release notes
Sep 15Done
Pricing page copy
Sep 24In progress
Support macros
Sep 26Not started

Was In progress and Sep 21. Also: Felix as assignee of the macros.

Apply all three?ApplyEdit

Know what changed before you sit down

Thirty minutes before the meeting, Cedric posts what changed in the project since last time, what is blocked, and who has not answered.

  • What changed since the last meeting
  • What is blocked, and on whom
  • Overdue tasks, with assignees
  • Tasks with nobody on them
  • Posted where the team reads
  • On the calendar's schedule

@Cedric Before every Monday launch sync, post what changed in Launch plan and what is blocked.

Cedric
Launch sync, the briefPosted in #launch · 10:30
In 30 min

Changed

DoneApp store screenshots
ThuPricing page copy, moved from Mon

Blocked

ListBeta invite emails

Tasks created when the work is agreed

Work agreed in a call or a thread becomes a task with an assignee, a due date and its subtasks, in the right project and section.

  • Create tasks from a call
  • Create tasks from a thread
  • Assignee and due date filled in
  • Subtasks for the steps
  • In the right project and section
  • Proposed first, saved on your yes

@Cedric Create a task in Launch plan for the pricing page copy, for Nadia, due Wednesday, with a draft and a review.

Mark complete

Pricing page copy

Assignee
Nadia Haddad
Due date
Sep 23
Projects
Launch plan · Content

Subtasks

Draft
Review

From today's planning call.

Create this task?CreateEdit

Work moves when someone is away

When someone is out, their due tasks do not wait. Cedric looks up the team, proposes who takes what, and reassigns on your yes.

  • Find tasks due while someone is out
  • Look up teammates and teams
  • Propose a new assignee
  • Reschedule instead, if you prefer
  • Comment with the handover
  • Add followers so nobody is surprised

@Cedric Kevin is out next week. Who can take his tasks that are due before he is back?

Launch plan
ListBoardTimelineCalendar
Task nameAssigneeDue date
Store listing text
Sam OkonkwoSep 23
Promo video export
Felix AnderssonSep 25
Pricing page copy
Nadia HaddadSep 24

Both were Kevin Zhou, out Sep 21 to 28.

Reassign both?ReassignEdit

Ask how the project is going

Cedric reads the tasks, the status updates and the activity, and answers in the channel. Ask about one project or a whole portfolio.

  • What is overdue, and whose it is
  • What changed this week
  • Filter by assignee or due date
  • Read project status updates
  • Summarize a portfolio
  • Alerts when a project you named changes

@Cedric Is the launch on track? What is behind, and who is holding it?

Cedric
Launch plan, this weekRead from Asana just now
From Asana
9tasks completed since Monday
ThuPricing page copy, Nadia, was Monday

Behind

SamBeta invite emails, waiting on the list

Tasks move when the work lands

When the pull request merges or the file arrives, Cedric proposes the move. The board shows where the work is, without anyone dragging.

  • Move tasks between sections
  • Mark complete when it ships
  • Change a custom field
  • Comment with what landed
  • Attach the file or the link
  • Your Asana rules keep running

@Cedric Move App store screenshots to In review and mark Release notes complete.

Launch plan
ListBoardTimelineCalendar

In review2

App store screenshots
Today4
Pricing page copy
Sep 242

+ Add task

Complete2

Release notes
Sep 15
Beta signup form
Sep 12

+ Add task

Stop chasing your team. Let Cedric do it for you.

One message to Cedric becomes every follow-up, every week. He asks the assignee, records the answer and updates the task, and you stop being the person who chases.

You say it once
Hannah BergMon 3 Aug

@Cedric follow up with assignees on anything overdue in Launch plan, and keep it updated.

CedricAPPMon 3 Aug

On it, every weekday at 9:00. You get the summary before Monday's sync.

Cedric's messages this week16 follow-ups

To Kevin ZhouMon 9:00

The app store screenshots were due Friday. What's the status?

CompletedRunning late

To Nadia HaddadMon 9:00

Pricing page copy is due today. Still on track?

On trackRunning lateNew date: Thursday

To Sam OkonkwoTue 9:00

Beta invite emails has had no activity for five days. Is something blocking it?

All goodBlockedWaiting on the list

To Felix AnderssonWed 9:00

Asking again: can you take the support macros, due Friday?

Yes, mineNot meNo answer yet

And twelve more like these. From you this week: none.

Updates from everywhere the work happens.

A task ships in a pull request, a decision lands in a call, a date slips in a thread. Cedric reads those tools too, so Asana hears about it.

Plus a catalog of 3,200 more apps. See all integrations →

You remain in control.

You choose which projects Cedric works on, and no task changes without a person's yes.

You name the projects

Cedric checks in only on the projects you point him at, with the Asana account you connect.

Every change follows a yes

An assignee's tap updates their own task. Anything Cedric infers waits for approval.

See the change first

Each suggestion shows the task, the old value and the new one. Edit it in the same reply.

A clear activity history

What was asked, who answered, and what changed in Asana, in one view.

Your rhythm

Check-ins run when you say: every morning, before a meeting, or only when asked.

Deleting is confirmed

Cedric completes and moves tasks. Deleting a task or a project is confirmed every time.

Cedric remembers who owns what and how your team works, so the right person gets the question. How approvals work →

Private, in your control,
and Swiss based.

Private.

Your data is never sold to anyone
Your data is never used to train models

In your control.

Privacy between channels
DMs and personal context stay yours

Swiss based.

Built in Zurich, Switzerland
GDPR compliant

Asana AI agent, answered

An assistant that works in your Asana workspace on your behalf. Cedric searches tasks, projects and portfolios, creates and updates tasks, reassigns and reschedules them, and keeps projects current by asking the people the work is assigned to.

He reads the project on a schedule you set, finds tasks that are overdue or have gone quiet, and asks the assignee in a direct message with one-tap answers. The answer completes the task or sets the new date. Changes he infers from threads and calls come to you as suggestions first.

No. Every change follows a yes. When an assignee taps Completed, that tap is the yes for their own task. Anything Cedric infers on his own is proposed and waits. How approvals work has the rule.

No. Rules you set up in Asana keep running on every change. Cedric creates and updates tasks the way a teammate would, and your rules react to those saves as they normally do.

Yes. Ask once and he posts the brief before every occurrence: what changed in the project since the last meeting, what is blocked, and who has not answered. See meeting prep.

The task stays as it is. Cedric asks once more, then lists the task as unanswered in the brief, so the question gets asked in the room.

Yes. He reads the project's status updates and the activity on its tasks, and summarizes what moved, what is overdue and who is holding what. Ask for one project or a portfolio, and for a window like this week.

He can, and he shows exactly what he will remove and waits for your confirmation every time. Marking complete or moving to a section is the usual path. A summary across many projects takes longer than one project, because Asana limits how fast any app can read.

Stop asking whether Asana is up to date.

Connect Asana to Cedric, set up your Asana AI agent in minutes, and let the check-ins, the task updates and the pre-meeting brief run on their own.

Connect Asana to Cedric

No credit card required. Every change to Asana follows a yes.