openai · anthropic · google
Is the model you call still alive?
Paste a model id, an endpoint or a param. aidep follows every announced replacement until it reaches one with no retirement on file, and tells you the day each stops working.
the whole repo, no account, no token
the calendar
What dies next
dates as published by each provider
| identifier | provider | dies | replacement |
|---|---|---|---|
| ft-babbage-002+15 that day | OpenAI | Oct 23, 2026 | gpt-5.6-terra |
| v1-prompts+2 that day | OpenAI | Nov 30, 2026 | none announced |
| chatgpt-image-latest+2 that day | OpenAI | Dec 1, 2026 | gpt-image-2.5-sunburst or gpt-image-2.5-flare |
| gpt-5-2025-08-07+5 that day | OpenAI | Dec 11, 2026 | gpt-5.6-sol |
| fine-tuning | OpenAI | Jan 6, 202792 days | none announced |
| gpt-4o-audio+8 that day | OpenAI | Jan 20, 2027106 days | gpt-audio-1.5 |
| gpt-4o-mini-transcribe+3 that day | OpenAI | Feb 26, 2027143 days | gpt-live-transcribe or gpt-transcribe |
| gemini-3.1-flash-lite | May 7, 2027213 daysearliest possible | gemini-3.5-flash-lite |
already dead
| identifier | provider | retired | replacement |
|---|---|---|---|
| claude-3-5-sonnet-20241022 | Anthropic | Oct 28, 2025calls fail | claude-sonnet-4-6 |
| gemini-2.0-flash | Jun 1, 2026calls fail | gemini-3.6-flash | |
| chatgpt-4o-latest | OpenAI | Feb 17, 2026calls fail | gpt-5.1-chat-latest |
| claude-opus-4-1-20250805 | Anthropic | Aug 5, 2026calls fail | claude-opus-4-8 |
the full register, with a github search you can run per row →
after install
One PR per retirement date
- 01
Install
Three GitHub permissions, listed in full on the security page. aidep opens one onboarding PR: the complete audit of your repo, every deprecated identifier with file and line. Nothing else happens until you merge it.
example · pull request · onboardingopen12 findings in 7 files 4 dead · 8 dying nearest Oct 23, 2026 (17 days) .github/aidep.json added
- 02
Opt in to migration PRs
One PR per retirement date, grouping every file it touches. The safe rewrites are applied; anything that cannot be rewritten safely becomes a manual checklist in the PR body, not a guess. aidep never touches .github/workflows.
example · pull request · agent briefopt-insites src/chat.ts:41, :88 replace gpt-5.6-sol verified 2026-08-16 trap /v1/prompts dies 2026-11-30
- 03
Merge on evidence
Turn on evals and a model-swap PR ships a pack that replays your prompts against the old model and the new one, in your CI with your keys, and posts the result. That comment is the merge decision.
example · github-actionsheld 18/20gpt-4-turbo -> gpt-5.6-sol held on 18/20 prompts held summarize_invoice held classify_ticket drifted extract_line_items
why deterministic matters: openai’s own migration guide points at prompt objects that are themselves deprecated (dead Nov 30, 2026). aidep inlines configs instead.
the obvious question
Why not just ask my agent?
29 / 171
vendor-named replacements that are themselves already deprecated
Do. It is good at the rewrite. Two things it structurally cannot do: it cannot tell you about a date you never asked about, and it cannot know what shipped after its training cutoff.
Of the 171 registry rows that name a replacement, 29 name a replacement that is itself already deprecated. One in 6. An agent working from last year’s docs lands on a dead target that often, then says “done.”
aidep tells it when, and tells it what is true today. check what yours picked → handbook →
what it can touch
Three permissions, and findings only
Metadata read, contents read and write, pull requests read and write. That is the whole list, so aidep can never write .github/workflows; the eval workflow ships as a file you move yourself.
Your tarball is fetched, scanned in memory and discarded. What persists is a path, a line, the identifier matched there, and the registry row it matched. Never source.
No customer model key, ever. Eval runs happen in your CI with your keys. The one egress is our own Anthropic key, used to draft eval cases, and only when your repo opts in.
Install once. Hear from us when a date gets close.
The app watches your repos and opens the PR. Or leave an email, confirm it once, and we will write when the next shutdown date gets close, and nothing else.
free on every repo, migration prs included · $39 an org a month adds the eval run · pricing