Alpenglow@alpenglowapp
The export builder is live. Build the report once, send it anywhere: PDF, sheet, or straight to a client. Built because we were tired of doing it by hand too.
Drafted by Cedric · held for your approval
Use case · Development
Devs in flow. Everyone in the loop.
Half of what interrupts a developer is not development, and half of what frustrates everyone else is not knowing what the developers are doing. Cedric absorbs both halves, in Slack, with an approval gate on everything.
$50 in free credits when you sign up. No card needed.
- The chores around the code (announcements, follow-ups, the bug someone mentioned in a thread) get handed to Cedric in one sentence.
- Standing watchdogs turn "someone should keep an eye on that" into something that actually keeps an eye on that.
- The rest of the company gets a daily, readable view of dev activity without interrupting a single developer.
- "What has Sophie been doing?" gets answered from commits and reviews, not from vibes.
- Anything that posts, emails, or merges waits for a person's yes. The jokes below work because the gate is real.
The wall between the devs and everyone else
Every company with developers has the same wall. On one side, people deep in the work who would rather not stop to write announcements, chase reviews, or explain what they did all week. On the other, people who genuinely need to know: what shipped, what broke, what the team should tell customers.
The usual fix is meetings and status documents, which tax the developers to inform the others. Cedric takes the wall down from both sides instead: the devs delegate the chores in a sentence, and everyone else asks Cedric instead of asking a developer.
For the devs
Ship it, then say one sentence.
#devCedric is in this channel
John Keller9:14 AM
@Cedric we just shipped the export builder. Post it on our LinkedIn.
CedricAPP9:15 AM
Drafted: a three-line post on what it does and who it's for, with a visual. I made X versions too, since the launch thread reads well there. All held for your approval.
Post to LinkedIn and X?
The announcement is a chore, not a craft
Cedric writes it from the actual changelog and the thread where you built it, so the post says what shipped, not marketing fog.
Every channel at once
LinkedIn, X, the newsletter, the customer changelog: one sentence from you fans out to all of them, each in its own register.
Nothing posts itself
Every draft waits for a yes. The company account stays incapable of surprising you.
The X versions, ready to go
Cedric drafts the visuals too: an image card per post, in your brand, no designer interrupted.
Alpenglow@alpenglowapp
Saved views shipped. Your filters, your columns, your sort, remembered. The report you rebuild every Monday is now a bookmark.
Drafted by Cedric · held for your approval
For the devs
The watchdog you always meant to set up.
#devCedric is in this channel
Priya Sharma10:02 AM
@Cedric next time you see Bob messing with the production database again, email HR.
CedricAPP10:03 AM
Watch set: direct writes to production outside a migration. If it happens again I'll draft the email with the evidence attached and hold it for your yes. I've also sent Bob the runbook link, which may solve this cheaper.
Want a weekly digest of what the watch sees?
Standing eyes on anything
Deploys outside hours, direct production writes, a dependency nobody pinned: if a tool can see it, Cedric can watch it.
Evidence, not vibes
When a watch fires, the message carries the log lines and the timestamps. Nobody argues with a timestamp.
The gate keeps the joke a joke
The HR email is drafted, never sent, until a human decides Bob has truly earned it. Usually the runbook link wins.
For the devs
The bug from yesterday's thread, fixed.
#devCedric is in this channel
Sophie Marchand11:26 AM
@Cedric fix the bug John had yesterday.
CedricAPP11:27 AM
Found it in yesterday's #dev thread: the CSV import drops the header row when the file starts with a blank line. Reproduced it, patch written, tests pass. PR is open with John tagged for review.
Ping you when John reviews?
It read the thread
"The bug John had" is enough, because Cedric was in the channel when John had it. Context is the product.
Repro before patch
The fix comes with the failing case that now passes, so the review is about the approach, not about whether it works.
A PR, not a paste
The change arrives as a reviewable pull request with the story attached, and merging stays a human's click.
And the other side of the wall
Everything above serves the developers. Everything below serves everyone who ever wondered what the developers are doing, and did not want to interrupt them to find out.
For everyone else
The daily dev summary nobody had to write.
#generalCedric is in this channel
Marco Ruiz2:05 PM
@Cedric send me a daily summary of the dev activity.
CedricAPP2:06 PM
Scheduled, every day at 17:00: what merged, what's in review, what's stuck, with the week's shape as a chart. Today: 11 merges, 2 hotfixes, and the payments refactor is most of the way through review.
Daily at 17:00 work for you?
From the repo, not from memory
The summary is compiled from the day's actual activity on the connected tools, so it never depends on anyone's end-of-day energy.
Readable by non-developers
It says "the export bug is fixed", not the commit hash. The audience is the company, not the compiler.
A picture included
The chart below rides along, so the shape of the week is visible before a single line is read.
Yesterday, by the numbers
The summary's chart: one line per kind of activity, the day's headline in accent.
Merged11
Reviews given14
Open threads5
Hotfixes2
Illustrative day, compiled from the connected repo.
For everyone else
Honest answers about the week.
#leadershipCedric is in this channel
Lena Brunner3:41 PM
@Cedric what has Sophie been doing last week?
CedricAPP3:42 PM
Mostly cleaning up after the new intern's first migration: restored the two dropped indexes, rewrote the rollback, and reviewed every intern PR since. Also shipped the search fix. It was a quietly heroic week; details in the thread.
Lena Brunner3:43 PM
@Cedric so, who deserves a raise?
CedricAPP3:44 PM
That call is yours, happily. What the data says: Sophie unblocked nine teammates this month and has carried the review load for two. Breakdown attached, judgment not included.
Want the same breakdown monthly?
From commits, not vibes
The answer is compiled from what actually happened in the repo and the threads, which is fairer to the person than anyone's impression.
Invisible work becomes visible
Cleanup, reviews, and unblocking are the work that never demos well. It shows up here, which is precisely the point.
Data in, judgment out
Cedric hands over the breakdown and stops. Raises, reviews, and reckonings stay entirely human.
For everyone else
From the repo to the newsletter.
#marketingCedric is in this channel
Marco Ruiz4:24 PM
@Cedric anything new from the devs?
CedricAPP4:25 PM
Two things shipped this week: the export builder and saved views, both live. Want me to add them to the August newsletter? I'll draft the section in its voice and hold it for you.
Add both to the August newsletter?
Features find their audience
What ships in the repo surfaces where customers actually look: the newsletter, the changelog, the socials.
It offers, you decide
Cedric proposes the handoff the moment there's something worth telling. The yes is always yours.
One voice per channel
The newsletter section reads like the newsletter, not like a commit message with perfume.
What stays human, and why the jokes are safe
Activity is not performance. A quiet week can be the best engineering of the quarter, and Cedric's breakdowns say what happened, never what it was worth. Raises, reviews, and anything about a person's standing are decisions for people who look colleagues in the eye.
The Bob watch works because nothing fires on its own: the email is drafted, the evidence is attached, and it goes nowhere until a human decides. The same is true of every post, every newsletter section, every merged fix on this page.
And the intern? Everyone's first migration drops an index somewhere. The point of the Sophie answer is that the cleanup finally got seen, not that the mistake got filed.
FAQ
No. Cedric reads the repo, the tracker, and the channels it's invited to. The devs keep working; the visibility is a byproduct, not a ritual.
Yes: it writes the change, includes the repro, and opens a PR for human review. Merging stays a person's click, always. Coding agents can also hand work to Cedric and pull team context from it.
It reports the state of the work, the same information a standup or a sprint review surfaces, compiled instead of performed. It does not track hours, screens, or keystrokes, and the judgment questions stay with humans.
Nothing. Social posts, newsletter sections, HR emails real or joking: every outbound action is drafted and held for approval, every time.
Ready when you are
Take down the wall.
Add Cedric to your Slack, connect the repo, and let both sides breathe. $50 in free credits, no card needed.
$50 in free credits, no card needed.