Docs that keep themselves up to date.
uptodate.sh tracks changes across your repos and Slack, drafts the doc updates, and sends them to you for review. You approve the changes instead of writing them yourself.
Heads up, we shipped the longer session change this morning.
The Authentication page is out of date. Sessions now last 30 days instead of 7, and it came up in #support 4 times this week. I’ve drafted the fix.
Sessions stay active while you use the app and expire after 30 days of inactivity. You can end a session at any time from Settings → Security.
Every change lands in one review.
Connect the places your product actually changes. uptodate.sh watches them for you.
GitHub
Merged PRs, releases, and changelog entries.
Slack
Channels where product and support changes get discussed.
Linear
Shipped issues and closed feature work.
Support
The questions users keep asking your team.
It watches what changes
Connects to your repos, Slack channels, and support tickets to notice what moved — and which docs no longer match.
It drafts the update
For each gap, it proposes a precise edit in place. No blank pages, no rewriting from scratch.
You approve
Every change arrives as a review in Slack or email. Nothing ships to your docs without a yes.
Everything stays current, on its own.
The docs you connect keep matching your product without anyone going back to edit them.
148 pages, in sync.
uptodate.sh kept them current as your product changed. No one had to go back and edit them.