Skip to main content

Platform transition · September 29, 2026

The era of Custom GPTs is ending. The work continues.

Preserving the learning. Reworking the capabilities. Testing what comes next.

I'm aware of the change, and I'm working on it.

Custom GPTs were an important part of my learning: a place to explore ideas, develop working methods, and discover what useful AI assistance could become. Across OverKill Hill, AskJamie, and Glee-fully, that work includes published GPTs, prototypes, unfinished concepts, and supporting documents.

OpenAI has announced the retirement of Custom GPTs. I'm actively working to replatform the useful concepts, solutions, and systems into modular Agent Skills and, where appropriate, plugins. I'm also reviewing where separate GPTs can become parts of a coherent capability package.

This is a transition in progress. It is not a claim that every project has a tested replacement or that every concept will become a released product.

What OpenAI has announced

OpenAI’s scheduled retirement date for Custom GPTs is December 11, 2026. Existing GPTs remain usable until their applicable retirement date, subject to access and workspace permissions. Some Enterprise workspaces with an approved deferral have a different date; follow the notice for the account or workspace where the GPT was created.

OpenAI's migration workflow does not transfer existing conversations or custom actions, and replacement access and behavior need to be checked separately. Read OpenAI's retirement and migration FAQ. Source checked September 29, 2026.

How I'm carrying the work forward

  1. Preserve: recover instructions, reference material, examples, decisions, and source history.
  2. Reorganize: identify the useful capabilities, combine overlapping work, and keep the three regions' purposes and ownership distinct.
  3. Build skills: turn repeatable methods into modular procedures with clear inputs, outputs, and limits. An unfinished concept does not have to become a GPT first.
  4. Test and package: verify representative tasks and integrations before packaging related skills into plugins.
  5. Release deliberately: publish replacement links and availability on the relevant project pages when each replacement is ready.

What this means for the pages here

GPT-focused project pages carry a transition notice. Original descriptions remain as records of what was built or proposed. A GPT link is a legacy platform link, not a guarantee of continuing availability. Concept pages remain concepts until implementation and testing establish otherwise.

References to AI agents, model names, Agent Skills, or historical experiments do not by themselves mean a project depends on Custom GPTs. Independent applications and existing skill packages keep their own release and validation records.

Explore Skillz Forge for the existing skill work, or contact me about a specific project. Existing skill work is not proof that a particular GPT has been migrated.