Compatible (BYOK)Use OpenCode with GlideflowAI.
An open coding agent for terminal-centered development loops. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.
What this connection is for
OpenCode is a terminal-oriented coding agent for developers who want to stay close to files, commands, and project conventions while delegating parts of a task. It is a natural fit for a work style built around inspecting a repository, forming a plan, applying a focused change, and then verifying the result with the normal project tooling. The terminal surface keeps the agent's work in the same place as git and tests.
The broad OpenAI-compatible model-provider pattern is the relevant connection point here. Exact configuration filenames and schemas can vary as OpenCode evolves, so an integration page should not turn a passing example into a guaranteed menu path. The safe path is to find the current custom OpenAI-compatible provider surface in OpenCode and enter only documented provider values there.
This listing is Compatible (BYOK). GlideflowAI's existing docs confirm the endpoint values, but the exact current OpenCode file example is deliberately left to the project documentation and local version. Keep credentials external, choose an exact model ID, and validate with a small task before asking an agent to make broad changes.
Why pair it with GlideflowAI
When your OpenCode version exposes a compatible provider, the same GlideflowAI key can serve terminal and editor workflows.
The gateway's visible model list and public USD rates give a stable reference even when tool configuration formats change.
Setup
Use a new API key for the tool, select a model from the catalog, and begin with a small task. Do not put a key in a repository, screenshot, or shared configuration file.
Find OpenCode's current custom provider setting
Consult the OpenCode documentation for the installed version and locate its OpenAI-compatible or custom provider configuration. This page intentionally does not invent a filename or schema.
Use the standard endpoint values
In that supported provider configuration, enter the GlideflowAI base URL, API key, and an exact catalog model ID.
Provider : OpenAI Compatible Base URL : https://api.glideflowai.com/v1 API Key : sk-your-key Model ID : glm-5.2Prove the connection on a safe task
Ask for an explanation or a one-file plan, then inspect requests and output before enabling wider file or command access.
Before you begin: Manual check: verify the current OpenCode provider schema before publishing a version-specific configuration snippet.
Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing. For tool-specific troubleshooting, see the existing guide.
Frequently asked questions
Why is OpenCode not marked Verified?
The endpoint is compatible, but its configuration schema can vary and this gallery does not claim a current full-path test for every version.
Does the URL need /v1?
Yes, OpenAI-compatible clients should use https://api.glideflowai.com/v1.
What is the safe first troubleshooting step?
Test the key and selected model against the documented endpoint before changing agent permissions.
Ready to connect OpenCode?
Create a key, use the setup above, and verify the connection on a small task before you scale it up.
