Skip to main content

Crush

Use Crush with Divyam for file edits and shell commands.

Before you start

You need a Divyam account and an API key. If you don't have them yet, follow Getting Started first.

Replace the shortened divyam-sw-v1-... shown in examples with your complete API key.

The examples use divyam-as/gpt-6-sol. For another model, select its current ID in your harness or copy it from Models and pricing, and check its context limit and supported features.

1. Install Crush and set your key​

Install Crush using the official instructions, then set your key in the terminal where you will start Crush:

export DIVYAM_API_KEY="divyam-sw-v1-..."

2. Configure Divyam​

divyam-as/

Model ID: divyam-as/gpt-6-sol. Context window: 1,050,000 tokens. Models and pricing

Add this to ~/.config/crush/crushrc, creating the directory and file if needed. These are Crush configuration commands, executed by Crush when it loads the file.

provider add divyam \
  --type openai-compat \
  --base-url "https://api.preview.divyam.ai/v1" \
  --api-key "$DIVYAM_API_KEY"

model add divyam/divyam-as/gpt-6-sol \
  --context-window 200000 \
  --default-max-tokens 8192

For image files with an image-capable model, add --supports-images true to the model add command above.

3. Start an interactive session​

From your project folder, run:

crush

Press Ctrl+L and select divyam/divyam-as/gpt-6-sol.

In Crush's composer
Hello, what are your capabilities?
Paste this message, then send it.

To condense earlier messages, press Ctrl+P and select Summarize Session.

Feature limits

Divyam can omit the terminal finish_reason for capped replies, leaving Crush waiting or retrying. The 8192-token setting lowers the chance of this failure. Subagents are outside this guide.

Check your requests​

Open the Divyam console and select Logs. Your requests appear there within a few seconds, newest first, with their status, token counts and latency. Usage and Credits & Billing catch up within a few minutes.

Local cost estimates

Some clients display zero when model prices are missing. Check Credits & Billing for Divyam charges. Local dollar limits depend on the client's price and usage data.

For filters, cached-token counts and the requested-versus-routed view, see Logs and usage.