I built a standup orchestrator that runs inside your AI agent (and doesn't spy on anyone)

Felipe Oliveira — Sun, 15 Nov 2026 18:25:44 +0000

When my team started writing standups with AI, three problems showed up:

Loose updates. Everyone wrote in a different format, in a different place.
No view of the team. Whoever read them had to stitch messages together.
Nobody orchestrates. Nobody nudges who hasn't posted, and blockers sit until someone notices.

Standcast fixes this by keeping the writing where people already work, in their agent, and handling the rest.

The flow

You run /daily in Claude Code (or use the MCP server in Cursor, Codex, Claude Desktop or VS Code, or the CLI).
The daily opens with what you planned in the previous one and whether each item moved. Standcast drafts "yesterday" from real activity: pull requests opened, merged and reviewed, commits, Linear cards that moved and your Claude Code sessions, grouped by project in up to 5 lines.
You edit it, write "today", blockers and support requests (what you need from someone without being stuck: a review, a decision, a pairing session) and confirm. The MCP submit tool requires confirmed: true, so the agent can't send it on its own.
At the team's digest_at, a worker posts one digest per team to Slack or Google Chat: 🚧 blockers first, then 🤝 support requests.
In the web app, Today shows the team's day: open blockers with their age, recurrence and a "probably resolved" hint when the PR already merged, support requests, today's dailies and what shipped yesterday. History keeps past digests, searches confirmed dailies and exports shipped work as Markdown or CSV.

The parts that took real work

AI sessions without leaking anything. The CLI reads the Claude Code session files on your machine, redacts secrets and hands only a summary to the agent. No session data reaches the API: only the daily text you confirm.
Configuration as code. A standcast.yml in the organization's .github repository, which you can also edit through a form in the web app. Every push that changes the file gets a check run with the error on the right line, and an invalid push never breaks anything: the last valid version keeps working.
Routing blockers. A blocker that mentions a pull request goes by DM to its reviewers, then CODEOWNERS, then the team's managers. On Linear, to the owner of the blocking card. If it is still open after N days, the team gets one alert.
Sending exactly once. Every message goes through a database claim with a fencing token before it reaches the chat. A job retry never sends twice.
Time zones and workdays. remind_at and digest_at are local times of the team; Monday covers the weekend.

The rule I won't bend

No per-person metrics, no rankings, no history of who didn't post. "Who hasn't posted yet" exists only for today, in the web app. Standcast also suggests blockers (a PR waiting for review, CI red for a day, a card stuck in progress), but those suggestions belong only to the person: they never show up in the digest, the API, webhooks or for the manager. A CI test makes sure of it.

Stack

Bun, strict TypeScript, Hono, Postgres with Drizzle, pg-boss for queues, a GitHub App, Slack, Google Chat and Linear. The CLI is a single binary with the MCP
server built in. The web app is React 19 with TanStack Router and ker. MIT.

Open beta

It's in free beta and I'm looking for teams of 3 to 15 people on GChat. If you want to try it, leave a comment or open an issue and
I'll help you set it up.

Site: https://standcast.app
Repository: https://github.com/ImFelipeOliveira/standcast
Docs: https://docs.standcast.app