Codeanywhere, the browser-based cloud IDE, has shut down after fifteen years — and the late-August cluster starts firing today with the OpenAI Assistants API removal

A quiet feed tonight — one new entry, and it is one for the record rather than the countdown, because the shutdown it describes has already happened. The live fire drill is the existing board: the late-August cluster starts firing today.

New: Codeanywhere, the browser-based cloud IDE, has shut down

Codeanywhere — the browser-based cloud IDE that started in 2009 as PHPanywhere and grew into containerized DevBoxes with SSH, VM connections, and 75+ languages — has been wound down after fifteen years. In an official announcement, the team closed new signups, kept the service fully online through 30 June 2026 as an export window, and took the platform offline on 1 July 2026. Workspaces, containers, and any data left on the platform are no longer accessible; billing stopped as part of the wind-down.

We log it retrospectively because it is exactly the kind of thing this archive is for: a service a lot of people relied on to code from a Chromebook, a phone, or a borrowed laptop, with real search intent behind “is Codeanywhere shutting down” and “Codeanywhere alternative.” The team’s reasoning is candid — browser-based coding won, but the form that won moved toward “vibe coding” rather than the classic IDE, so rather than let the product degrade they chose a clean ending. The export window is now closed; the vendor’s advice was to push every project to its Git remote and download anything living only inside a DevBox before 1 July. Going forward the replacement is another cloud dev environment — GitHub Codespaces, Gitpod, self-hostable Coder — or a local editor with a dev container.

The late-August cluster is firing now

The stretch flagged over the last week has reached the front of the countdown:

• 26 August (today) — the OpenAI Assistants API is removed. Its removal date has arrived; /v1/assistants, /v1/threads, and /v1/runs should already be on the Responses API.
• 27 August (tomorrow) — Convictional shuts down; export catalog and order data before access ends.
• 28 August — OCI DevOps retires its Oracle Linux 7 build runners; pinned pipelines break rather than warn.
• 31 August — a four-way pile-up: GitHub Spark, Flowise cloud, the New Relic drop-filter-rules API, and the Power Automate mobile app.

Further out sit OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), and the Relay and Microsoft Sentinel SAP connector agent retirements (both 14 September). Last week’s Minimus reg.mini.dev entry keeps ticking toward 22 October.

All twelve entries within 30 days were re-checked against their primary sources tonight and hold — including the Sentinel SAP date, which our monitor cannot read off Microsoft’s JavaScript-rendered updates page and which was re-confirmed against Microsoft’s release-communications API. The full board with live countdowns is on the calendar.

Still watching, not on the board: InstantDB

No change: the circulating InstantDB / Instant Cloud wind-down report still traces only to a forwarded email quoted on Hacker News, with nothing on instantdb.com, its docs, status page, or repo. No official source, no entry — it stays on the watch list until Instant says something publicly.

Want these dates checked against your own repo instead of read off a list? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, from the same public dataset this site is built on.