Automated Cohere Model Release Watch
Every Monday, WebRun signs into Cohere, reads the changelog and documentation for new models, retired model versions, and endpoint changes, matches each one against the endpoints and model versions your build actually calls, posts what changed to Microsoft Teams, and WhatsApps the engineer on call.
How do I keep track of model changes that affect my integration?
Every Monday, WebRun signs into Cohere, reads the changelog and documentation for new or retired models and version changes, and matches them against the endpoints your build actually calls. It posts what changed to Microsoft Teams and WhatsApps the engineer, so a deprecation never lands as a production surprise.
- A retirement date is known weeks before it lands in production
- Alerts fire only for the models and endpoints you actually call
- Documentation changes stop being something someone happens to notice
Built for engineering teams · AI product builders · platform engineers · technical founders
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
dashboard.cohere.comin a real browser with your saved login - no setup, no API keys. -
1
Cohere - read the changelog and docs
cohere.com
WebRun opens Cohere to read the changelog and docs. - Sign into Cohere and open the changelog and the documentation pages you track
- Record any model added, any model version marked as retiring, and any endpoint behaviour change
- Note the dates attached to each change so a retirement has a countdown
- Compare against the list of models and endpoints your build calls, which you set once at setup
- Read only. WebRun never reads, copies, or regenerates an API key
Done when Every change since last week is recorded and matched against what you call.
-
2
Microsoft Teams - post what changed
microsoft.com
WebRun opens Microsoft Teams to post what changed. - Post the week's changes to your engineering channel in Microsoft Teams
- Split them into changes that touch your endpoints and changes that do not
- Give each item a plain sentence on what changed plus the link to the source page
- Keep a running note of upcoming retirement dates so the countdown stays visible
Done when The engineering channel has this week's changes, split by whether they affect you.
-
3
WhatsApp - flag anything you depend on
whatsapp.com
WebRun opens WhatsApp to flag anything you depend on. - Send the engineer on call a WhatsApp note only when a change touches a model or endpoint you use
- Name the model or endpoint, what changed, and the date it takes effect
- Say nothing in the weeks where nothing you depend on changed
- Leave any code, config, or model change to a person. WebRun never edits your integration
Done when The engineer hears about changes that affect the build, and nothing else.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it touch my API keys or my code?
No. WebRun never reads, copies, or regenerates an API key, and it never edits your integration. It reads published changelog and documentation pages and reports what changed.
How does it know which changes affect us?
You list the models and endpoints your build calls once at setup. Every change is matched against that list, so the WhatsApp alert only fires for something you actually depend on.
What if nothing changed this week?
Microsoft Teams gets a one-line note that the week was quiet, and WhatsApp stays silent. The alert channel is reserved for changes that touch your build.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.