OpenAI announced on September 11, 2026 that Custom GPTs will be retired and replaced by a Plugins system, and its own Help Center FAQ — now directly surfaced on the live web, where the case previously held only an echo-reconstructed copy — confirms retirement on December 11, 2026, with new GPT creation ending October 26 in affected Enterprise workspaces and approved Enterprise deferrals running to February 11, 2027. Migration carries GPT instructions and knowledge files into a plugin, but trade press (ADTmag, Visual Studio Magazine) corroborates that custom actions and conversation history do not transfer, and a September 23 developer-forum thread documents that sharing settings also reset: replacement plugins start private with no external link-sharing option, pushing small creators onto a public directory with no published review timeline. Dates have shifted across document revisions — the Enterprise migration target moved from Sept 17/25 to Sept 22/Oct 26 — which explains why no migration was observed on the originally reported Sept 17 date, while hands-on reporting confirms in-product migration prompts are now live. Net effect: the retirement plan itself is upgraded from 'reportedly' to first-party-confirmed and multiply corroborated; the two user-suspected workflow gaps from earlier Reddit testimony remain untested, and a new third gap (external distribution for creators who built businesses on shared GPTs) is now concretely documented.
Position already held — OpenAI is enacting exactly what ip:concept.vendor-lock-in and ip:concept.platform-debt describe, with ip:framework.sovereign-software-assurance's vendor-vanishes test as his standing frame — so this stays known, not news. But the newly first-party-confirmed facts bear on his work concretely: custom actions and sharing settings do NOT transfer, meaning the watch item he flagged on dev:project.mcp-ip-wiki has now resolved in the risky direction and warrants an audit of whether its ChatGPT search/fetch compatibility rides on Custom GPT actions before the Oct 26/Dec 11 dates (Enterprise scoping still leaves his own exposure unconfirmed), while the documented creator-distribution reset is dated case material for ip:framework.platform-escape-path's extract-the-spec argument and his LeverageAI governance advisory.
ip:concept.vendor-lock-inip:concept.platform-debtip:framework.sovereign-software-assurancedev:project.mcp-ip-wikiip:framework.platform-escape-pathip:source.retail-mcp-is-the-doorway-not-the-memory-ebook
queries asked of Scott's wikis
- vendor lock-in hosted AI platform dependency risk
- MCP connector custom actions portability migration
- agent instructions and knowledge files as portable artifacts
- platform-managed agents vs self-hosted agent harness
- skill/plugin packaging formats for reusable agent behavior
- platform retirement impact on dependent creators and workflows
now 0 pts/hpeak 6 pts/hcomments 0/hpeers p14momentum: steady3 platformsage 651h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-10-01T19:24:59Z
First tested migration report moves the custom-action portability risk from documented to observed: a daily-driver GPT lost its AWS API Gateway/Lambda calls, and the user's MCP-server replacement attempt also appeared insufficient — sharpening (not redirecting) the dev:project.mcp-ip-wiki audit watch item. With the Sept 17 miss now explained by the documented date shift and rollout confirmed live, uncertainty eases high->medium; engagement stays inert (~0.17 pts/h, 41st percentile), so this remains a corroborated-but-cold case at low heat.
2026-10-01T18:31:30Z
evidence attached: reddit.post.1wv6qqb — First-hand report that the Custom GPT→Plugin migration locks out third-party API integrations is concrete friction evidence for the migration case.
2026-09-30T02:01:29Z
grounded: known/medium — Position already held — OpenAI is enacting exactly what ip:concept.vendor-lock-in and ip:concept.platform-debt describe, with ip:framework.sovereign-software-as
2026-09-30T01:52:48Z
The first-party plugin submission docs add a second independent line: OpenAI has now both documented retirement intent (FAQ) and operationalized the replacement pipeline, lifting the plan from 'reportedly' to corroborated. But the Sept 17 migration target passed with no observed rollout, Dec 11 remains single-sourced, and engagement has gone cold (0.17 pts/h, 26th percentile, inert HN attachment) — so this is a corroborated-but-cold case and heat drops from medium to low.
2026-09-30T00:38:31Z
evidence attached: hn.story.49900443 — First-party plugin submission docs confirm the Plugins pipeline the Custom GPT migration depends on is operational.
2026-09-21T14:12:50Z
A second user account broadens the suspected replacement gap from bounded personal workflows to non-developer organizational use, but remains anticipatory testimony rather than a tested Plugin migration. It does not independently verify the retirement schedule or establish functional non-equivalence.
2026-09-21T00:22:50Z
evidence attached: reddit.post.1wlwnud — This is direct user evidence that the planned Custom GPT retirement may leave non-developer business workflows without an equivalent replacement.
2026-09-15T16:34:31Z
The new user testimony identifies a potential migration gap in preserving project-specific context isolated from personal identity, but does not demonstrate that Plugins lose this capability. It adds a workflow requirement to investigate, not independent confirmation of the retirement schedule or a verified migration failure.
2026-09-15T16:23:36Z
evidence attached: reddit.post.1wh4pcx — The user report provides concrete workflow-level evidence that Custom GPT retirement can disrupt bounded, project-specific environments beyond simple bot migration.
2026-09-14T13:26:53Z
grounded: known/low — This illustrates the dependency risk Scott already articulates in Sovereign Software Assurance and Vendor Lock-In; the supplied evidence does not establish Open
2026-09-14T13:23:57Z
origin walked (codex/luna, conf 0.98): anchor reddit.post.1wg2ms1 -> echo.other.fdc7a15dc6 by OpenAI
2026-09-14T13:23:01Z
case created — Specific near-term migration and retirement dates warrant tracking, although the purported official FAQ is not available in the supplied evidence.