teamthread

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

A team thread is posted to your Slack channel or your inbox on the working days you pick, written from commits, pull requests and Linear issues since the last thread. 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 in review with LIN-203 tracking related errors—watch for merge.

First three teammates

Alex — No observable signal in GitHub or Linear since the last thread.

Jules — Jules committed 9ad3e62 ("Add currency column to invoices") and c40f7b8 ("Format amounts by currency in receipts") to yara-saas/app, and updated LIN-455 "Multi-currency: research APAC providers" to In Progress.

Kavi — Kavi opened PR #408 in yara-saas/app ("Webhook signature verification refactor") and committed b71e04d ("Move HMAC handling into one module"). Kavi also reviewed PR #412 in yara-saas/app and updated LIN-203 "Webhook signature errors from the test endpoint" to In Review.

Continue reading the sample →

How it works

Paste your Slack incoming webhook URL (or pick email delivery).
Paste a GitHub Personal Access Token, a Linear API key, or both.
Add your teammates: display name, GitHub login, Linear email.
Pick a time, your timezone and which weekdays should post.
On those mornings, the team thread appears in your Slack channel or inbox, written from commits, pull requests and Linear issues since the last thread.

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 and pull requests in the repositories your token can read, and their Linear issues — and writes the thread itself. Teammates never have to write a standup paragraph. It reads no Slack messages: Slack is only where the thread is posted.
What's in the thread?: A one-line 'what to watch today' pointer, then one alphabetical paragraph per teammate covering what they did since the last thread. It reports activity, so it doesn't say what anyone plans to do or what's blocking them unless the source says so. Teammates with no activity in those sources get a line saying so rather than an invented paragraph, and every cited PR, issue or commit is checked against the source feed.
Can I preview a run before it posts?: Yes. The dashboard's preview writes today's thread on demand and shows it to you without posting it. The scheduled post still goes out at its time; pause the daily thread before then if you don't want it.
What if it makes something up?: Every draft is checked before it posts. A deterministic validator rejects any PR number, issue ID, commit hash or channel that isn't in the source feed, and a second check compares each statement with the feed. A rejected draft isn't posted: we try again, and if every attempt that morning is rejected, you get an email with the unpublished draft. These checks reduce mistakes but can't rule them out, so every thread links to its source feed.
Can a teammate opt out?: Yes. Every team-thread post has a 'leave me out' link in the footer. It emails the buyer, who removes that teammate from the dashboard in one click. Because the post goes to the whole team, the link sends a request rather than removing anyone by itself.
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?: Source feeds and threads are kept for 90 days in case you need to audit a past run, then aged out. Your tokens are encrypted with AES-256-GCM before they're stored, and the key is kept apart from the stored data.