eval backend resolves the evaluation backend for the current credentials and refreshes the local cache. Later evaluation commands use this result to choose the Coze or TEA evaluation platform. For TEA, the result includes the workspace, project, account, and session_key coordinates required by evaluation requests.
The backend result is cached by identity and evaluation gateway for 7 days. To bypass the cache, pass
--cache-refresh on the eval command group or on the top-level dataset command group.eval backend
Evaluation Gateway Configuration
The default evaluation gateway usesagentkit.cn-beijing.volcengineapi.com, signing service agentkit, and region cn-beijing. Override these variables only with connection settings supplied by the service provider. The global cloud-provider option does not replace evaluation gateway configuration.
Debug Options
Theeval command group and top-level dataset command group support these debug options. They are scoped to evaluation backend caching and TEA request troubleshooting, and are not global options.
target, draft updates, and explicit version management require TEA. Do not mix resource IDs, project settings, or field mappings across Coze and TEA
Full requests printed by --verbose can contain cases, prompts, or business data even though the session cookie is masked. Inspect diagnostic logs before sharing. Refresh the backend cache after changing accounts, gateways, or backend settings