teamthread

Your team's daily standup, written from real activity.

A team thread is posted to your Slack channel every weekday morning — drawn from yesterday's commits, issues, and Slack messages. No teammate has to write a DM-prompt response.

Try it free for 7 days See a real team-thread sample →

$9/seat/month · 3-seat minimum · card-on-file, charged after the trial.

Sample team thread— posted to #eng-standup for Yara's eng team on Tuesday 14 May 2026

View full thread

What to watch today

PR #408 (webhook signature verification refactor) is the next item on the payments-reliability run; expect ~5 review comments to land before lunch.

First three replies in thread

Alex — No observable signal in connected systems yesterday; mentioned an AM dentist appointment in #eng. No observable signal — please confirm in thread if you'd like a paragraph here tomorrow.

Jules — Started multi-currency-prep research yesterday: 6 commits on the wip branch (no PR yet) and a new Linear issue LIN-455 scoping APAC pay-rail providers. Today: continuing APAC provider scan, flagging top candidates in LIN-455. No blockers flagged.

Kavi — Opened PR #408 ('webhook signature verification refactor') with 5 commits and reviewed PR #412 twice. Moved LIN-203 to in-review. Today: incorporating review comments on PR #408 and verifying the signature path against staging. Flagged signature errors from the test webhook in #payments-debug — under investigation in PR #408.

Continue reading the sample →

How it works

Paste your Slack incoming webhook URL (or pick email delivery).
Paste a GitHub Personal Access Token and a Linear API key.
Add your teammates: display name, GitHub login, Linear email, Slack handle.
Pick a cron time and which weekdays should post.
Every weekday morning, the team thread appears in your Slack channel, written from yesterday's commits, issues, and Slack messages.

Questions

How is this different from a question-prompt standup bot?: A question-prompt bot DMs each teammate three questions and asks them to type the answers. teamthread reads the activity each teammate has already produced — commits in connected repos, issues in connected Linear projects, messages in connected Slack channels — and writes the thread itself. Teammates never have to write a standup paragraph.
What's in the thread?: A one-line 'what to watch today' synthesis, then one alphabetical paragraph per teammate covering what they did yesterday, what they're picking up today, and any blockers visible in the source feed. Teammates with no observable activity get a 'please confirm in thread' line rather than an invented paragraph — every cited PR, issue, or channel reference is verifiable against the source feed.
Can I preview a run before it posts?: Yes — the dashboard has a one-click preview that runs the pipeline on demand and shows you the full artifact 30 minutes before the cron tick. Pulling the post in that window cancels the cron for the day.
What if the AI makes something up?: A deterministic validator runs after the LLM passes and rejects any PR number, issue ID, or channel reference that isn't verbatim in the source feed. Rejected runs aren't silently dropped — they email you the unpublished draft for manual review.
Can a teammate opt out?: Yes. Every team-thread post has an 'exclude me from future threads' link in the footer that any teammate can self-serve. The opt-out takes effect immediately and notifies the buyer so the seat can be reassigned.
How does pricing work?: $9/seat/month. 3-seat minimum, so the thread always has more than one person to summarize. 7-day free trial — your card is collected at signup and not charged until the trial completes.
How is data stored?: Raw source feeds and LLM input/output are kept for 90 days in case you need to audit a past run, then aged out. Your tokens are stored encrypted in Vercel's environment store; no third-party secrets handler.