Compatible (BYOK)

Use Crush with GlideflowAI.

A terminal coding agent with explicit custom OpenAI-compatible providers. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.

Get a key

What this connection is for

Crush is a terminal coding agent for developers who want an interactive shell that combines repository context, local tools, and a selected language-model provider. It is especially appealing when model choice should be part of a project-level workflow rather than an editor extension setting. Sessions remain close to the commands, files, and version-control operations that a developer already uses.

Choose Crush when you are comfortable owning a trusted crush.json and want to switch providers without leaving the terminal. It is not the right fit for a team that cannot review local configuration files, because Crush permits shell-style value expansion in its configuration. Keep provider configuration at user scope when it contains sensitive or environment-specific choices.

Crush documents an openai-compat provider type with base_url and api_key fields. Point that provider at GlideflowAI, reference the key through an environment variable, and add only model metadata you can verify from the catalog. Keep the provider name stable so a project can clearly identify which configured route a session uses. Crush is an independent project; this is a user-managed connection, not an endorsement or partnership.

Why pair it with GlideflowAI

Crush's named provider blocks make it practical to keep a GlideflowAI route beside other terminal-provider choices.

Using $GLIDEFLOW_API_KEY in crush.json keeps a repository-specific coding session from containing the credential itself.

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.

1
Export a private key
Keep the key in the environment so the Crush configuration can reference it without storing a secret in JSON.
```
export GLIDEFLOW_API_KEY="sk-your-key"
```
2
Add an OpenAI-compatible provider
Add this provider shape to ~/.config/crush/crush.json or another documented Crush configuration scope. Add model metadata only from values you can confirm for the selected model.
```
{
  "providers": {
    "glideflowai": {
      "type": "openai-compat",
      "base_url": "https://api.glideflowai.com/v1",
      "api_key": "$GLIDEFLOW_API_KEY"
    }
  }
}
```

Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing.

Frequently asked questions

Which Crush provider type is correct?

Use openai-compat for GlideflowAI; Crush reserves its openai type for traffic routed through OpenAI itself.

Where does Crush read its configuration?

Crush can read project-local .crush.json, crush.json, or user-level ~/.config/crush/crush.json; use the least sharable scope that fits the key reference.

Why should I review a crush.json before running it?

Crush supports shell-style expansion in configuration values, so an unreviewed config can execute substitutions with your shell privileges.

Is this an official integration?

No. The connection is configured by you using a compatible API and does not imply sponsorship, endorsement, or a partnership.

Ready to connect Crush?

Create a key, use the setup above, and verify the connection on a small task before you scale it up.