Installed in seconds
Add him to your Slack and he is at work. No servers, no setup project, nothing for IT to maintain.
Add him to your server and mention him in any channel: the shipping report, the plan, the Friday digest, the issue filed. One Discord bot for the whole team, with the same memory he has everywhere else, and he asks before anything sends.
@Cedric a customer says checkout fails on Safari.
Logged and routed. Boris owns it, flagged as priority.
What I did
Cedric joins your Discord server like a member: an AI bot you mention, and he reads the repo, posts the digest on a schedule, keeps the plan honest, and files what the thread agreed on. Anything that sends, changes, or spends waits for a yes, in the channel.
@Cedric in any channel or thread, and the report, the plan, or the reminder comes back in place.
What shipped, what is open, in plain words. The issue the thread agreed on gets filed on your yes.
Say “every Friday at 16:00” once, and the digest posts itself.
Kevin ZhouToday at 9:04
@Cedric what shipped this week, and what's still open?
CedricAPPToday at 9:04
Eleven pull requests merged. Three notable, one still waiting on a release.
Kevin ZhouToday at 9:06
@Cedric post this every Friday at 16:00 and file the deploy as an issue.
CedricAPPToday at 9:06
Friday digest scheduled for #dev-team. Issue drafted.
Mention him where the work lives. He reads the context and answers in place, as a member of the server.
“Summarize this thread”, asked in the thread, answered in the thread.
Ask privately. DMs and personal context stay yours, never shared with the channel.
Digests, standups, and reminders on a cadence you set in words, paused or cancelled from the channel.
Created and used by people from
Automations: follow-ups and reports, sent on a schedule
Scheduling: finds the slot and books the call for you
Meetings: he joins the call, then posts the action items

Deliverables: reports and decks, drafted into the chat
Company Brain: teach him once, he knows for everyone
Team sync: updates land where everyone already reads

Shared tools: connected once, used by the whole team
Skills: your way of working, saved and reused by all

“I was impressed to see our team using it spontaneously. Linking it with our systems was very easy, and it now helps us with all of our lead management.”
Fabienne: Cedric, run the meeting.
Four quick steps, anyone can do it.
Cedric is ready
Welcome. Link a tool or two, add me where your team talks, and ask away.
Connections
@Cedric book calls with the new leads
Booked. All three on Thursday.
Thursday3 calls
Cedric is joining the call
Weekly standupThu 10:00
Call ended, 24 min
Ask in plain words, and Cedric works the tools behind the ask: he drafts the email, books the meeting, updates the CRM, and pulls the report. Connected once, from the chat.
Cedric holds the context of everything your team does: the meetings, the threads, the decisions, the tools. He tracks and coordinates all of it better than a human can, at 3am as readily as 3pm. The week he saves you from is well documented:
Atlassian, McKinsey, and UNC Charlotte research.
From your dashboard. He joins as a member and answers when mentioned in a channel or a thread.
Yes, once GitHub is connected. What shipped, what is open, and the issue the thread agreed on, filed on your yes.
Only the channels he has been given access to, like any member. DMs with him stay private.
"Every Friday at 16:00", said once. The digest posts itself. Pause or cancel from the channel.
Yes. Same memory, same connected tools. A plan made in Discord is known in the web dashboard and in Slack.
Sending outside the server, changing a record in a connected tool, or spending. Each waits under the reply as a button.
100K credits ($50) on sign up. No card needed.