Ship the work. Cedric does the follow-ups.
Say it once from Claude Code. Cedric finds who asked, answers them in their thread, updates Notion or Linear, drafts the email to the customer and checks back later. He knows who you mean, because he knows your company.
Works in
$50 in free credits. No card required. Every send waits for your yes.
⏺cedric · search_workspace ("SSO for Halcyon")
⎿Asked by Nadja in #sales, Tuesday. On Reto's roadmap.
⏺cedric · send_channel_message (#sales)
⎿Reply to Nadja, waiting for your yes
⏺cedric · notion (Halcyon roadmap)
⎿SSO for Halcyon: Done
⏺cedric · schedule_task (Thursday 10:00)
⎿Ask Dana if sign-in works
Nadja, in the #sales threadwaitingposted
SSO for Halcyon on the roadmapwaitingdone
Dana at Halcyon, SSO is readywaitingdrafted
Check in with Dana, ThursdaywaitingscheduledCreated and used by people from
The fix took an hour. The follow-up took the afternoon.
Every change leaves a trail of small jobs in other apps. Don't waste your time on follow-ups anymore. Let Cedric do them.
Find who asked for itby handReply in their threadby handMove the roadmap cardby hand
Close the issueby handTell the customerby handCheck back ThursdayforgottenBack to the code, and someone asks "is it live yet?"
⏺cedric · ask_cedric
⎿Six follow-ups, four waiting for your yes
Nadja told in her threadRoadmap card moved to DoneHAL-212 closed with the PR linkEmail to Dana draftedCheck-in Thursday, scheduledAnd when someone asks "is it live yet?", Cedric answers.
From the request to the reply, without leaving the terminal.
Cedric reads what was asked, wherever it was asked. You fix it. He tells the person once it is live, at the time you choose.
⏺cedric · read_channel (#marketing)
⎿7 notes from Nadja, 2 screenshots
⏺Update (pricing/page.tsx)
⎿7 changes, pushed to staging
⏺cedric · schedule_task (tomorrow 09:00)
⎿Checks the page is up, then posts in #marketing
# marketing
Seven notes on the pricing page, screenshots attached.
@Nadja all seven notes are in, live on the pricing page.
checked live at 08:59Everyone hears about it, the way they want it.
One change, four people who care. Cedric tells each of them in their own place and their own words, so nobody has to ask what happened.
SSO for Halcyon, mergedher #sales threadposted
his roadmapHalcyon roadmap
#support, in plain wordsposted
email, from NadjaHi Dana, your team can sign in with Okta from today.
waiting for Nadja's yesEvery push, told to the team.
Point GitHub at Cedric once. Every push and every Actions run becomes a short post in plain words, in the channel the team reads. When someone asks what's new, he already knows.
1. Ask once
# product
@Cedric post what's new here every time we push to main. Plain words, skip the chores.
Done. Paste this address in GitHub, under Settings, Webhooks.
app.meet-cedric.com/api/hooks/…One sentence sets the rule. The posts land in this channel.
2. You push
halcyon-apppush to maina41f9c2feat: Okta sign-in for team workspaces7d03e11perf: stream rows in invoice exportc9b2a08fix: pricing toggle on Safarie11d4f0chore: bump dependenciesGitHub sends the push and the Actions run to Cedric.
3. The team reads it
# productNew in the app today:
- Teams can sign in with Okta.
- Invoice exports are much faster.
- The pricing toggle works on Safari again.
3 changes, deploy passedNo commit hashes, no chores. What changed for the people using it.
@Cedric what's new in the app this week?
Three things shipped: Okta sign-in on Tuesday, faster invoice exports and the Safari fix on Wednesday. Thursday's deploy failed once and was fixed within the hour.
from 9 pushes and 11 Actions runsHe knows who you mean.
Cedric keeps one memory of your company: the people, the customers, the channels, who asked for what. So you can talk to him the way you talk to a colleague.
tell whoever asked
Slacklet Dana know
Memoryclose it on the roadmap
NotionQuestions go to Cedric, not to you.
When the team needs an answer, they ask him in Slack. He checks the source and replies, and you stay in the code.
# productLucia is heads-down@Cedric is the SSO fix live yet?
Yes. Merged Tuesday 16:40, deployed at 16:52.
GitHub@Cedric how many sign-ups since the launch?
214 since Monday, 38 of them from the pricing page.
PostHog@Cedric when is the next Halcyon call?
Thursday 10:00. I put the SSO check on the agenda.
Google CalendarSet up in a minute.
1. Add Cedric to Claude Code
⏺/mcp · cedric · Authenticate
⎿Signed in to your workspace
One line, one sign-in. Claude, ChatGPT and Cursor connect the same way.
2. Connect the team's tools
SlackconnectedNotionconnectedLinearconnectedGitHubconnectedGmailconnectedConnected once for the whole team. Read-only where the tool allows it.
3. Say it once, approve the sends
@Nadja SSO is live for Halcyon. Dana can sign in with Okta today.
Anything that sends or changes waits for a yes. A scheduled follow-up is approved by scheduling it.
And the rest of the team's work.
The same Cedric takes the meeting notes, shares the tools and writes the weekly report.
Takes the notes, then does the follow-ups.
See the use case →
Connect a tool once. The whole team uses it.
See the use case →Tells you what happened while you were out.
See the use case →
Plans the project, chases the tasks, sends the report.
See the use case →
Sends the weekly report every Monday morning.
See the use case →Briefs you an hour before the meeting.
See the use case →Private, in your control,
and Swiss based.
Private.
In your control.
Swiss based.
Questions about Cedric for developers
One line in the terminal: claude mcp add --transport http cedric https://app.meet-cedric.com/api/v1/mcp. Then type /mcp, pick cedric and sign in once. Claude, ChatGPT and Cursor connect from the same address. The setup, step by step.
By default Cedric drafts every reply, email and post, and sends it once you say yes. Updating a ticket or a roadmap page waits for the same yes. Schedule a follow-up and scheduling it is the approval. An admin can mint a key that runs sends straight away, for the people who want that. How approvals work.
He keeps one memory for the workspace: who your teammates and customers are, where each of them wants updates, which channel a request came from. He also searches Slack, the mail and your connected tools before he answers, so "whoever asked" becomes a name and a thread.
Any tool connected to the workspace: Notion, Linear, Jira, GitHub, Slack, Gmail, the calendar, the CRM, and 3,000 more apps in the catalog. See all integrations.
Yes. Ask him in the channel where the notes should go, and he gives you a webhook address. Paste it into GitHub under Settings, Webhooks. From then on every push and every Actions run becomes a short post in plain words, following the instructions you gave, like "skip the chores" or "only tell us about failed deploys".
Yes. Mention him in Slack, Telegram or Discord. He answers from the same connections and the same memory you use, and tells you only when something needs you.
No. Your coding agent writes the code. Cedric is the teammate around it: he finds what was asked, tells the people waiting, updates the tracker and follows up later.
A workspace starts with $50 in free credits, no card. Plans start at $19 a month for the whole team, with no price per seat. See the plans.
Stop chasing follow-ups. Let Cedric do them.
Hand over your follow-ups$50 in free credits. No card required. No price per seat.