Compatible (BYOK)Use OpenHands with GlideflowAI.
A software-development agent for longer, tool-using tasks. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.
What this connection is for
OpenHands is a software-development agent environment aimed at tasks that need more than a single code completion. It can combine a language model with a workspace, terminal-like tools, and iterative observation of results. That makes it interesting for a contained issue or maintenance task where the agent needs to read, act, observe, and revise rather than merely suggest a patch.
Longer-horizon agents deserve a stricter setup discipline than an editor autocomplete. The model provider, runtime sandbox, repository access, and task boundary all matter. Before configuring a non-default provider, make sure you understand the OpenHands version, the deployment mode, and the credential boundary. A compatible endpoint is only one part of a secure agent setup.
GlideflowAI is listed as Compatible (BYOK) for OpenHands because an OpenAI-compatible provider is the expected protocol, but this gallery does not claim a particular OpenHands release or deployment has been end-to-end tested. Use the project’s current provider documentation to configure the endpoint, key, and model rather than copying an unverified UI path.
Why pair it with GlideflowAI
A standard compatible gateway can reduce credential sprawl when you test OpenHands alongside other agent tools.
Open public pricing and model IDs are useful context for a tool-using agent, where a task can involve multiple turns and commands.
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.
Confirm the provider mechanism for your OpenHands deployment
Check the documentation for your current OpenHands version and deployment mode. Locate its documented OpenAI-compatible or custom LLM provider settings before changing environment or runtime configuration.
Supply compatible connection values through that mechanism
Use the standard endpoint, a privately stored API key, and an exact catalog model ID.
Base URL : https://api.glideflowai.com/v1 API key : sk-your-key Model ID : glm-5.2Constrain the first run
Use an isolated test repository and a small, observable task. Keep network, shell, and repository permissions limited until you have reviewed the agent's behavior.
Before you begin: Manual check: identify the active OpenHands version, deployment mode, and current provider configuration before attempting setup.
Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing.
Frequently asked questions
Why is OpenHands only Compatible?
The protocol is a fit, but exact provider fields and deployment controls differ across OpenHands releases and environments.
Should I put the key in a project file?
No. Use the deployment's supported secret mechanism or environment handling, never a tracked repository file.
What should I test first?
Validate a read-only or one-file task in an isolated workspace before granting broader runtime capabilities.
Ready to connect OpenHands?
Create a key, use the setup above, and verify the connection on a small task before you scale it up.
