Getting started

Send your first daily in a few minutes. Before you start, your admin must have installed Standcast and listed you in a team in standcast.yml.

1. Install the CLI

The standcast CLI is a single binary. It also runs the MCP server and is what the Claude Code skill calls.

Download the binary for your system from the latest release:

System	File
macOS, Apple silicon	standcast-bun-darwin-arm64
macOS, Intel	standcast-bun-darwin-x64
Linux, x64	standcast-bun-linux-x64
Linux, ARM64	standcast-bun-linux-arm64
Windows, x64	standcast-bun-windows-x64.exe

On macOS or Linux, put it on your PATH as standcast. For example, on a Mac with Apple silicon:

mkdir -p ~/.local/bin
curl -fsSL -o ~/.local/bin/standcast \
  https://github.com/ImFelipeOliveira/standcast/releases/latest/download/standcast-bun-darwin-arm64
chmod +x ~/.local/bin/standcast
standcast --version

Each release also has a SHA256SUMS file to check the download. Or use the install script, which downloads the right binary, checks it against SHA256SUMS and installs it to ~/.local/bin/standcast:

curl -fsSL https://api.standcast.app/install.sh | sh

2. Sign in

standcast login

The CLI shows a code and opens GitHub in your browser. Enter the code and authorize Standcast. The CLI then prints "Signed in as" and your login.

Signing in also links you to your Slack user, so that the digest can mention you. If your admin connects Slack or changes standcast.yml after you sign in, run standcast login again.

Check who you are and which organizations you can write dailies for:

standcast whoami

{"login":"alice","orgs":[{"installationId":12345678,"login":"acme"}]}

3. Write your daily

Pick the way that fits your tools:

• Claude Code: install the plugin and run /daily. See Claude Code skill.
• Cursor, Codex, Claude Desktop, VS Code or another MCP client: add standcast mcp to your client and ask for your daily. See MCP server.
• Only the terminal: use standcast draft and standcast submit. See CLI.

In every case, the flow is the same:

1. Standcast builds a draft of yesterday from your GitHub activity since your last daily, plus your own Linear cards if your organization connected Linear.
2. You fix yesterday, then write today and any blockers.
3. You see the final daily and confirm it. Nothing is sent before that.

4. After you send it

• Your daily is stored for today's standup date. If you send again the same day, the new version replaces the old one.
• At the team's digest_at, your daily appears in the digest of every team you are in.
• If the digest already went out, your daily is posted as a reply in the digest thread, and the result says late: true.
• Webhooks registered by your admin receive a daily.submitted event, and a blocker.opened event for each new blocker.

Something went wrong? See Troubleshooting.