ENSEMBLE support

Email support@ensemble.markets. Include the time, client, returned model or run ID, and request ID if available. Describe the expected result and what happened.

Do not send passwords, API keys, OAuth tokens, or a full private conversation. Send strategy source only if it is needed to explain your issue and you intend to share it with support.

Check the ChatGPT and Codex connection page for the current directory release status. For an installed plugin, enable it in the host and connect your ENSEMBLE account using the sign-in prompt.

If authentication has expired, reconnect through your host’s connection settings and verify the intended account. Unexpectedly empty research can mean a different account is connected. Ask the assistant to check the connected profile before creating replacement models.

If a tool is unknown, refresh the connection’s tool list. Some capabilities are unavailable while their feature is disabled. A temporary service outage is different from an expired sign-in; retain the error and respect its retry guidance.

An insufficient-allowance response stops that operation before work starts. The usage-help page explains balances, outstanding holds, estimates, and account limitations. A billing-provider outage means the service could not verify allowance; it does not prove that the account has no funds.

For pending work, keep the model or run ID and inspect its status later. After a timeout on a write, check whether the resource already exists before trying again. Report suspected duplicate jobs or charges with their identifiers.

Contact support about account access, correction, deletion, or a copy of your data. Identify the account using its email address. We may need to verify that the request comes from the account owner; never send a password as proof.

The privacy policy describes collection, processors, retention, and deletion. Disconnecting the plugin ends that connection; it does not itself delete research stored in ENSEMBLE.