Legacy agent types
What changes for agents built on the retired OpenAI Assistant and OpenAI GPTs paths.
On this page
Runbear used to let you import an OpenAI Assistant or a GPT and drive it through Runbear's channels. Both paths are retired for new setups. This page covers what that means if you have one.
What is retired#
OpenAI Assistant agents. You cannot create one. Existing agents continue to run and stay readable through the dashboard and the public API, but they are read-only through the Agent API surface, and the tooling around them is no longer extended.
OpenAI GPTs import. Removed. The import endpoint returns an explanatory error.
OpenAPI Actions and __api__ function calling. These add-on styles were how
Assistant agents called external APIs. They accept no new configurations. The
replacement is MCP, which covers the same ground with
per-user authorization and a managed catalog.
Moving to a current agent#
There is no automatic conversion, because the pieces do not map one to one. In practice a rebuild is short:
- Create a new agent from the Agents page.
- Copy the Assistant's system prompt into Instructions, splitting it into named blocks as you go.
- Re-upload or reconnect its files as a knowledge source. Files that came from Notion, Confluence, Google Drive, Slack, or SharePoint should be connected at the source instead, so they stay current on their own.
- Replace each OpenAPI action with the equivalent tool, or a custom MCP server if the API is your own.
- Move the channel connections over and remove the old agent once the new one answers correctly.
The rebuilt agent gains what the Assistant path never had: incremental knowledge sync, per-user tool authorization, triggers, and traces.