Skip to main content
TRAE is an AI-native IDE by ByteDance. Its built-in Custom Config panel accepts any OpenAI-compatible or Anthropic-compatible endpoint, routing the full AI Gateway catalog through Orq.ai for unified tracing, cost tracking, and access controls without any plugin or extension.

​
Prerequisites

​
Setup

1

Open the Models settings

In TRAE, click the icon in the top-right of the chat panel to open Settings, then navigate to Models.
2

Add a provider entry

Two provider formats are needed. For each, click + Add Model, expand the Custom Config section, and fill the fields for the relevant format below.
Always use the provider/model_id format for Model ID (e.g. openai/gpt-5.6-sol, anthropic/claude-sonnet-5). Model IDs without the provider prefix return a 400 invalid model format error.
For OpenAI, Google, DeepSeek, and all other non-Anthropic models:Replace <ORQ_API_KEY> with the key from Workspace Settings → API Keys.
3

Configure Advanced Settings (optional)

Expand Advanced Settings to tune per-model behavior:
4

Submit

Click Submit. The model appears in the TRAE model selector.
5

Select the model in a chat

Use the model selector in the bottom-right of the TRAE chat panel to pick the AI Gateway-routed provider for the current session.

​
Skills

Orq Skills add pre-built agentic workflows to Trae for the full Build, Evaluate, Optimize lifecycle.

​
Installation

Set an API key and connect the Orq MCP server first. Skills are then triggered by describing what is needed.

Orq Skills

The full catalogue of skills and slash commands.
Slash commands (/orq:quickstart, /orq:traces, and others) are only available in Claude Code.

​
Troubleshooting

The Model ID is missing the provider prefix. Change gpt-5.6-sol to openai/gpt-5.6-sol, claude-sonnet-5 to anthropic/claude-sonnet-5, and so on. All AI Gateway model IDs require the provider/ prefix.
A Claude model is configured under the OpenAI Chat Completions format. Create a separate provider entry using API Format: Anthropic Messages pointing at https://my.orq.ai/v3/anthropic instead.
If OPENAI_API_KEY or OPENAI_BASE_URL are set in the environment and a legacy OpenAI provider is also configured in TRAE, requests may resolve to the wrong endpoint. Unset those variables if not in use:
Confirm the API Key field contains a valid Orq.ai API key (not an OpenAI or Anthropic key) and that Custom Request URL points to the correct Orq endpoint for the chosen format.

​
Verification

Select the AI Gateway-routed model in the TRAE chat panel and send a message. The response appears in the chat and the request appears in Orq.ai Traces with the selected model identifier.