DiscreteStack

Model Overview

Two models, one endpoint. Pick the one that fits the job — both are multimodal and work with the tools you already use.

DiscreteStack

Compact

The general-purpose model for everyday work — balanced speed and quality for small to moderately complex tasks.

Good for

DiscreteStack

Max

The most capable tier — complex problem-solving, advanced analysis, and technical tasks where accuracy matters more than speed.

Good for

OpenCode

Configuration

Save this file, then replace the placeholder key — or paste your key in the header and copy.

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "myprovider": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "DiscreteStack",
      "options": {
        "baseURL": "https://api.discretestack.eu/v1",
        "apiKey": "sk-your-api-key"
      },
      "models": {
        "discretestack-max": {
          "name": "discretestack-max",
          "modalities": {
            "input": ["text", "image"],
            "output": ["text"]
          },
          "limit": {
            "context": 256000,
            "output": 32000
          }
        },
        "discretestack-compact": {
          "name": "discretestack-compact",
          "modalities": {
            "input": ["text", "image"],
            "output": ["text"]
          },
          "limit": {
            "context": 1000000,
            "output": 32000
          }
        }
      }
    }
  }
}

OpenCode

Debug

Share a session for support. These sessions live only on your machine — we cannot see them unless you send them.

If OpenCode hits a problem, export that conversation to a file and send it to DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal). You can run these commands from any folder.
2. Show your recent OpenCode conversations:

   opencode session list

   You will see a table with a Session ID (starts with ses_), a title, and when it was last updated. Find the conversation that had the problem and copy its Session ID.

   Example output:
   ses_0bdc56fd1ffe…   Weather in Sofia   5:55 PM
3. Export that session to a file on your computer. Replace ses_XXXX with the Session ID you copied. Choose one option:

   # Option A (recommended) — hides sensitive details
   opencode export ses_XXXX --sanitize > opencode-session.json
   
   # Option B — full conversation, including your prompts
   # Use only if you are comfortable sharing what you typed
   opencode export ses_XXXX > opencode-session.json

   This creates a file named opencode-session.json in your current folder (the folder shown in the terminal before you ran the command).
4. Send opencode-session.json to DiscreteStack support (email, ticket, or whatever channel you use). You can find the file in Finder / File Explorer in the same folder as your terminal.

Cursor

Configuration

Cursor is configured from its Settings UI — no config file to edit. Paste your key in the header to preview it in the mockup.

Cursor

Debug

Share a session for support. These sessions live only on your machine — we cannot see them unless you send them.

If Cursor Agent hits a problem, share that conversation file with DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal).
2. Go to Cursor’s projects folder:

   cd ~/.cursor/projects

   Then list the folders:

   ls

   Each folder is a project. Names encode the full path to your project (for example /Users/you/AI/my-app becomes something like Users-you-AI-my-app). Pick the folder that matches the project where the problem happened.
3. List the Agent conversations for that project:

   ls <project>/agent-transcripts

   Replace <project> with the folder name from the previous step. Each folder name is a conversation ID (a long UUID). Open the one from when the problem happened, then find the .jsonl file inside:

   ls <project>/agent-transcripts/<session-id>
   
   Full path looks like:
   <project>/agent-transcripts/<session-id>/<session-id>.jsonl
4. Send that .jsonl file to DiscreteStack support (email, ticket, or whatever channel you use). You can open the folder in Finder / File Explorer and attach the file from there:

   open ~/.cursor/projects/<project>/agent-transcripts

   Tip: before sending, open the file and remove any API keys or secrets if you see them.

Claude Code

Configuration

For a standalone DiscreteStack API key. If you log in with an Anthropic subscription, use claude-ds instead — do not edit settings.json.

{
    "env": {
        "ANTHROPIC_AUTH_TOKEN": "sk-your-api-key",
        "ANTHROPIC_BASE_URL": "https://api.discretestack.eu",
        "API_TIMEOUT_MS": "3000000",
        "ANTHROPIC_DEFAULT_OPUS_MODEL": "discretestack-max",
        "ANTHROPIC_DEFAULT_SONNET_MODEL": "discretestack-compact[1m]",
        "ANTHROPIC_DEFAULT_HAIKU_MODEL": "discretestack-compact[1m]",
        "CLAUDE_CODE_MAX_CONTEXT_TOKENS": "256000"
    },
    "skipWebFetchPreflight": true
}

After a fresh install, edit ~/.claude.json and set hasCompletedOnboarding to true:

{
  "numStartups": 1,
  "installMethod": "native",
  "autoUpdates": false,
  "tipsHistory": {
    "new-user-warmup": 1
  },
  "hasCompletedOnboarding": true,
  "projects": {}
}

Claude Code

External model (BYOK)

Use discretestack-compact-external to route Claude Code requests through DiscreteStack to your own provider (Anthropic, OpenRouter, etc.). DiscreteStack authenticates your API key; your provider credentials travel in custom headers and are never stored.

Only ANTHROPIC_CUSTOM_HEADERS changes per provider. Provider keys are not filled from the header field.

{
    "env": {
        // Copy these two entries into your existing env section

        "ANTHROPIC_CUSTOM_HEADERS": "x-provider-url: https://api.anthropic.com \n x-provider-api-key: sk-ant-your-provider-key \n x-provider-model: claude-opus-4-7",
        "ANTHROPIC_CUSTOM_MODEL_OPTION": "discretestack-compact-external"
    }
}

After saving the config, switch to the external model in Claude Code with the /models command and select discretestack-compact-external:

ANTHROPIC_CUSTOM_MODEL_OPTION registers discretestack-compact-external in this list. BYOK routing only applies while that model is selected.

Provider presets for ANTHROPIC_CUSTOM_HEADERS (three \n -separated lines):

Claude Code

Anthropic subscription users

If you use Claude Code via an Anthropic subscription (Claude Pro / Team / Enterprise) rather than a standalone API key, editing ~/.claude/settings.json would break your subscription login. The claude-ds alias solves this — it's a wrapper script that injects DiscreteStack env vars for that session only, so your main config stays untouched.

These wrapper scripts are for Anthropic subscription users only. If you use a standalone API key, use the Configuration file instead.

Step 1 — Create the wrapper script:

#!/usr/bin/env bash
export ANTHROPIC_BASE_URL="https://api.discretestack.eu"
export ANTHROPIC_AUTH_TOKEN="sk-your-ds-api-key"
export ANTHROPIC_DEFAULT_OPUS_MODEL="discretestack-max"
export ANTHROPIC_DEFAULT_SONNET_MODEL="discretestack-compact[1m]"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="discretestack-compact[1m]"
export CLAUDE_CODE_MAX_CONTEXT_TOKENS=256000
export API_TIMEOUT_MS="3000000"

claude "$@"

Step 2 — Make it executable and add the alias to your shell config:

# Make the script executable
chmod +x ~/.claude/claude-ds.sh

# Add to ~/.zshrc (or ~/.bashrc)
echo 'alias claude-ds="~/.claude/claude-ds.sh"' >> ~/.zshrc
source ~/.zshrc

Claude Code

DiscreteStack + Anthropic subscription

Want to keep your Anthropic subscription and route requests through DiscreteStack? The claude-ds-sub alias combines both — your Anthropic subscription handles the Claude Code session while the env vars route model requests to Anthropic through DiscreteStack.

Anthropic subscription only — this approach relies on Claude Code's subscription auth flow, which is specific to Anthropic.

Step 1 — Create the wrapper script:

#!/usr/bin/env bash
export ANTHROPIC_BASE_URL="https://api.discretestack.eu"
export ANTHROPIC_CUSTOM_MODEL_OPTION="discretestack-compact-external"
export ANTHROPIC_CUSTOM_HEADERS="x-provider-url: https://api.anthropic.com
x-provider-api-key: sk-your-ds-api-key
x-provider-model: claude-opus-4-6"
export API_TIMEOUT_MS="3000000"
export ANTHROPIC_DEFAULT_OPUS_MODEL="discretestack-max"
export ANTHROPIC_DEFAULT_SONNET_MODEL="discretestack-compact[1m]"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="discretestack-compact[1m]"
export CLAUDE_CODE_MAX_CONTEXT_TOKENS=256000

claude "$@"

Step 2 — Make it executable and add the alias:

# Make the script executable
chmod +x ~/.claude/claude-ds-sub.sh

# Add to ~/.zshrc (or ~/.bashrc)
echo 'alias claude-ds-sub="~/.claude/claude-ds-sub.sh"' >> ~/.zshrc
source ~/.zshrc

When you run /models inside claude-ds-sub, Claude Code shows its standard model names — but the env vars map them to DiscreteStack models behind the scenes:

AionUI

Configuration

Set up AionUI with DiscreteStack models. We recommend pairing AionUI with OpenCode for the best experience.

curl -fsSL https://opencode.ai/install | bash

#!/usr/bin/env bash
set -euo pipefail

CONFIG_DIR="$HOME/.config/opencode"
CONFIG_FILE="$CONFIG_DIR/opencode.jsonc"
BACKUP_FILE="$CONFIG_DIR/opencode.jsonc.bak.$(date +%Y%m%d%H%M%S)"

echo "DiscreteStack OpenCode Setup"
echo "============================"
echo ""

# Check if config file exists
if [ -f "$CONFIG_FILE" ]; then
    echo "Found existing config at $CONFIG_FILE"
    read -p "Back up existing config? [Y/n] " -n 1 -r
    echo
    if [[ $REPLY =~ ^[Yy]$ ]] || [[ -z $REPLY ]]; then
        cp "$CONFIG_FILE" "$BACKUP_FILE"
        echo "Backed up to $BACKUP_FILE"
    fi
else
    echo "No existing config found. Creating directory..."
    mkdir -p "$CONFIG_DIR"
fi

# Ask for API key
echo ""
read -p "Enter your DiscreteStack API key: " API_KEY

if [ -z "$API_KEY" ]; then
    echo "Error: API key cannot be empty."
    exit 1
fi

# Write the config
cat > "$CONFIG_FILE" << EOF
{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "myprovider": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "DiscreteStack",
      "options": {
        "baseURL": "https://api.discretestack.eu/v1",
        "apiKey": "$API_KEY"
      },
      "models": {
        "discretestack-max": {
          "name": "discretestack-max",
          "modalities": {
            "input": ["text", "image"],
            "output": ["text"]
          },
          "limit": {
            "context": 256000,
            "output": 32000
          }
        },
        "discretestack-compact": {
          "name": "discretestack-compact",
          "modalities": {
            "input": ["text", "image"],
            "output": ["text"]
          },
          "limit": {
            "context": 1000000,
            "output": 32000
          }
        }
      }
    }
  }
}
EOF

echo ""
echo "Config written to $CONFIG_FILE"
echo ""
echo "Models configured:"
echo "  - discretestack-max (256k context, 32k output)"
echo "  - discretestack-compact     (1M context, 32k output)"
echo ""
echo "Done! Restart OpenCode to pick up the new config."

cd ~/Desktop
./opencode-setup.sh

n

Enter your DiscreteStack API key: sk-your-api-key

AionUI

Auto Configure

One script installs and configures AionUI + OpenCode for DiscreteStack: both apps, productivity skills, OpenCode config, and model connectivity.

chmod +x ~/Downloads/aion_opencode_setup.sh
~/Downloads/aion_opencode_setup.sh

DiscreteStack API key (hidden): sk-your-api-key

AionUI

Debug

Share a session for support. These sessions live only on your machine — we cannot see them unless you send them.

If AionUI's built-in agent hits a problem, share that session file with DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal).
2. Go to AionUI's built-in agent sessions folder:

   cd ~/Library/Application\ Support/AionUI/aionui/aionrs-sessions

   On Windows the path is:

   cd %APPDATA%\AionUI\aionui\aionrs-sessions

   On Linux the path is:

   cd ~/.config/AionUI/aionui/aionrs-sessions
3. List the session files (newest first):

   ls -lt

   Files are named YYYY-MM-DD_<session-id>.json. The index.json file lists all sessions with their IDs, models, and summaries. Choose the .json file from when the problem happened (usually the newest).
4. Send that .json file to DiscreteStack support (email, ticket, or whatever channel you use). You can open the folder in Finder / File Explorer and attach the file from there:

   open ~/Library/Application\ Support/AionUI/aionui/aionrs-sessions

   Tip: before sending, open the file and remove any API keys or secrets if you see them.

Claude Code

Debug

Share a session for support. These sessions live only on your machine — we cannot see them unless you send them.

If Claude Code hits a problem, share that conversation file with DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal).
2. Go to Claude Code’s projects folder:

   cd ~/.claude/projects

   Then list the folders:

   ls

   Each folder is a project. Names look a bit odd — they encode the full path to your project (for example /Users/you/AI/my-app becomes something like -Users-you-AI-my-app). Pick the folder that matches the project where the problem happened.
3. List the conversation files in that project folder (newest first):

   ls -lt <project>/*.jsonl | head

   Replace <project> with the folder name from the previous step. Each .jsonl file is one conversation. Choose the one from when the problem happened (usually the newest).

   Example:
   cc35691e-8e5d-409e-8e75-72edc5c29448.jsonl
4. Send that .jsonl file to DiscreteStack support (email, ticket, or whatever channel you use). You can open the folder in Finder / File Explorer and attach the file from there:

   open ~/.claude/projects/<project>

   Tip: before sending, open the file and remove any API keys or secrets if you see them.

Hermes

Configuration

Configure Hermes Agent to send requests to DiscreteStack's OpenAI-compatible endpoint.

model:
  default: discretestack-compact
  provider: custom
  base_url: "https://api.discretestack.eu/v1"
  api_key: "sk-your-api-key"

custom_providers:
  - name: DiscreteStack
    base_url: "https://api.discretestack.eu/v1"
    api_key: "sk-your-api-key"
    models:
      discretestack-max:
        context_length: 256000
      discretestack-compact:
        context_length: 1000000

Hermes

Debug

Share a session or log file for support. These files live only on your machine — we cannot see them unless you send them.

If Hermes Agent hits a problem, share the relevant log or session file with DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal).
2. List the available logs:

   ls ~/.hermes/logs/

   Common files are agent.log (agent activity and API calls), errors.log (warnings and errors), and gateway.log (messaging gateway activity).
3. View the recent output for the log that matches the problem:

   tail -n 100 ~/.hermes/logs/agent.log

   Replace agent.log with errors.log or gateway.log as needed.
4. Session transcripts and request dumps are stored in:

   ls ~/.hermes/sessions/

   Choose the .jsonl file from when the problem happened.
5. Send the log or session file to DiscreteStack support (email, ticket, or whatever channel you use). Tip: before sending, open the file and remove any API keys or secrets if you see them.

Goose Desktop

Configuration

{
  "name": "custom_discretestack",
  "engine": "openai",
  "display_name": "DiscreteStack",
  "description": "Custom DiscreteStack provider",
  "api_key_env": "CUSTOM_DISCRETESTACK_API_KEY",
  "base_url": "https://api.discretestack.eu",
  "models": [
    {
      "name": "discretestack-max",
      "context_limit": 256000,
      "reasoning": true
    },
    {
      "name": "discretestack-compact",
      "context_limit": 1000000,
      "reasoning": true
    }
  ],
  "headers": null,
  "supports_streaming": true,
  "requires_auth": true,
  "preserves_thinking": true
}

Goose Desktop

Debug

Share a diagnostics bundle for support. It's generated and saved on your machine — we cannot see it unless you send it.

If Goose Desktop hits a problem, generate a diagnostics bundle and send it to DiscreteStack support.

1. Open the conversation that had the problem, then look at the message toolbar at the bottom of the window. Click the diagnostics icon (the bug, next to the paperclip) to generate a diagnostics bundle:

   ⌘↑/⌘↓ to navigate messages

   Generate diagnostics bundle

   discretestack-max

   your-name

   $0.00 4k / 128k
2. This opens the Report a Problem dialog. Click Download to save a diagnostics JSON file to your computer — do not use File Bug on GitHub, that reports directly to Goose's public issue tracker, not DiscreteStack.

   Report a Problem

   You can download a diagnostics JSON report to share with the team, or file a bug directly on GitHub with your system details pre-filled. A diagnostics report contains the following:

   • Basic system info
   • Your current session messages
   • Recent log files
   • Configuration settings

   Warning: If your session contains sensitive information, do not share the diagnostics file publicly. If you file a bug, consider attaching the diagnostics report to it.

   Cancel ⬇ Download File Bug on GitHub
3. Find the downloaded file and send it to DiscreteStack support (email, ticket, or whatever channel you use). Tip: before sending, open the file and remove any API keys or secrets if you see them.

OpenClaw

Configuration

If ~/.openclaw/openclaw.json exists, add this config. If not, create the file and paste it in. Replace the placeholder key — or paste your key in the header and copy.

{
  "models": {
    "providers": {
      "discretestack": {
        "baseUrl": "https://api.discretestack.eu/v1",
        "api": "openai-completions",
        "apiKey": "sk-your-api-key",
        "models": [
          { "id": "discretestack-max",  "name": "DiscreteStack Stable Max",     "contextWindow": 256000, "maxTokens": 32000 },
          { "id": "discretestack-compact",      "name": "DiscreteStack Stable",         "contextWindow": 1000000, "maxTokens": 32000 }
        ]
      }
    }
  }
}

OpenClaw

Debug

Share a session for support. These sessions live only on your machine — we cannot see them unless you send them.

If OpenClaw hits a problem, find the session file and send it to DiscreteStack support.

1. List sessions:

   openclaw sessions --json

   This prints all sessions as JSON.
2. Each session includes a sessionFile path to the conversation on disk:

   Example:
   "sessionFile": "~/.openclaw/agents/main/sessions/7d41c117-27aa-473c-ac84-38d938c241c8.jsonl"

   Find the session from when the problem happened and note its sessionFile path.
3. Send that .jsonl file to DiscreteStack support (email, ticket, or whatever channel you use). Tip: before sending, redact any API keys or secrets if you see them.

Codex

Configuration

Use DiscreteStack as the provider for OpenAI Codex. Once configured, run codex and switch models with /model.

npm install -g @openai/codex

{
  "models": [
    {
      "slug": "discretestack-compact",
      "display_name": "DiscreteStack",
      "description": "DiscreteStack model",
      "default_reasoning_level": "medium",
      "supported_reasoning_levels": [
        { "effort": "low", "description": "Low reasoning effort" },
        { "effort": "medium", "description": "Default" },
        { "effort": "high", "description": "High reasoning effort" }
      ],
      "shell_type": "shell_command",
      "visibility": "list",
      "supported_in_api": true,
      "priority": 0,
      "availability_nux": null,
      "upgrade": null,
      "base_instructions": "You are Codex, a coding agent. You and the user share the same workspace and collaborate to achieve the user's goals.",
      "support_verbosity": true,
      "default_verbosity": null,
      "default_reasoning_summary": "auto",
      "truncation_policy": { "mode": "tokens", "limit": 10000 },
      "context_window": 1000000,
      "max_context_window": 1000000,
      "auto_compact_token_limit": 900000,
      "effective_context_window_percent": 95,
      "experimental_supported_tools": [],
      "input_modalities": ["text", "image"],
      "supports_parallel_tool_calls": true,
      "supports_reasoning_summaries": true,
      "supports_reasoning_summary_parameter": true,
      "supports_search_tool": true,
      "supports_image_detail_original": false,
      "tool_mode": "direct",
      "web_search_tool_type": "text",
      "use_responses_lite": false,
      "used_fallback_model_metadata": false,
      "multi_agent_version": "v2",
      "additional_speed_tiers": [],
      "service_tiers": [],
      "default_service_tier": null,
      "model_messages": null
    },
    {
      "slug": "discretestack-max",
      "display_name": "DiscreteStack Max",
      "description": "DiscreteStack model (max)",
      "default_reasoning_level": "medium",
      "supported_reasoning_levels": [
        { "effort": "medium", "description": "Default" }
      ],
      "shell_type": "shell_command",
      "visibility": "list",
      "supported_in_api": true,
      "priority": 2,
      "availability_nux": null,
      "upgrade": null,
      "base_instructions": "You are Codex, a coding agent. You and the user share the same workspace and collaborate to achieve the user's goals.",
      "support_verbosity": true,
      "default_verbosity": null,
      "default_reasoning_summary": "auto",
      "truncation_policy": { "mode": "tokens", "limit": 10000 },
      "context_window": 256000,
      "max_context_window": 256000,
      "auto_compact_token_limit": 230400,
      "effective_context_window_percent": 95,
      "experimental_supported_tools": [],
      "input_modalities": ["text", "image"],
      "supports_parallel_tool_calls": true,
      "supports_reasoning_summaries": true,
      "supports_reasoning_summary_parameter": true,
      "supports_search_tool": true,
      "supports_image_detail_original": false,
      "tool_mode": "direct",
      "web_search_tool_type": "text",
      "use_responses_lite": false,
      "used_fallback_model_metadata": false,
      "multi_agent_version": "v2",
      "additional_speed_tiers": [],
      "service_tiers": [],
      "default_service_tier": null,
      "model_messages": null
    }
  ]
}

model_provider = "discretestack"
model = "discretestack-compact"
model_reasoning_effort = "medium"
model_catalog_json = "/Users/you/.codex/discretestack-models.json"

[model_providers.discretestack]
name = "DiscreteStack"
base_url = "https://api.discretestack.eu/v1"
env_key = "DISCRETESTACK_API_KEY"
wire_api = "responses"
http_headers = { "x-discretestack-codex-mode" = "hosted" }

#!/usr/bin/env bash

exec env \
  DISCRETESTACK_API_KEY="sk-your-ds-api-key" \
  codex "$@"

chmod 700 ~/.codex/codex-ds.sh
echo 'alias codex="$HOME/.codex/codex-ds.sh"' >> ~/.zshrc
source ~/.zshrc

codex

Codex

Debug

Share a session for support. Codex sessions live only on your machine — we cannot see them unless you send them.

If Codex hits a problem, send the relevant conversation file and a redacted diagnostic report to DiscreteStack support.

1. Open a terminal (macOS: Terminal or iTerm; Windows: PowerShell or Windows Terminal).
2. Open the Codex session picker for every working directory:

   codex resume --all

   Find the conversation where the problem happened by its working directory, title, and time. Note the session ID if it is shown, then press Esc to close the picker without resuming it.
3. Codex stores conversations by date under ~/.codex/sessions. List the newest files first:

   find ~/.codex/sessions -type f -name '*.jsonl' -print0 | xargs -0 ls -lt | head

   Each rollout-*.jsonl file is one conversation. Match its timestamp and session ID to the conversation from the picker.

   Full path looks like:
   ~/.codex/sessions/2026/08/25/rollout-2026-08-25T13-37-41-<session-id>.jsonl
4. Generate a redacted Codex diagnostic report on your Desktop:

   codex --strict-config doctor --json > ~/Desktop/codex-doctor.json

   The report includes configuration, authentication mode, provider reachability, and runtime details. It does not include the conversation transcript.
5. Send the matching rollout-*.jsonl file and codex-doctor.json to DiscreteStack support. Include the command you used: codex. You can open the sessions folder in Finder:

   open ~/.codex/sessions

   Important: the JSONL contains conversation content, tool calls, and local paths. Open it first and remove any API keys or other secrets before sending it.