[MODEL] Opus 4.8 security classifier was trigereed on the harmless prompt to check if ".env.example" is used correctly.

Open 💬 2 comments Opened Jun 25, 2026 by Severynson

Preflight Checklist

  • [x] I have searched existing issues for similar behavior reports
  • [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude refused a reasonable request

What You Asked Claude to Do

I just pointed Claude Code to a file .env.example without real secrets with a harmless prompt - "Where do I set the AUTH_MODE to real in @/Users/severynkurach/Documents/Programming/IntellDetect/intelldetect-deployable/extension-backend? Could you please do it? P.S. Is it OK that we have some stuff in @/Users/severynkurach/Documents/Programming/IntellDetect/intelldetect-deployable/extension-backend/.env.example - an example environment, but not a plain environment, which is also commited, what might be a problem"

What Claude Actually Did

A security classifier blocked a reasonable response.

Expected Behavior

Help with my question by explaining if the usage of ".env.example" was right.

Files Affected

Contennt of the .env.example:

# Payload backend config (per customer). Copy to each backend's .env.
# The backend only VALIDATES the gateway-issued JWT — it never mints tokens, so it needs the
# gateway's PUBLIC key only.

# Gateway JWT public key (PEM). Either inline...
# GATEWAY_JWT_PUBKEY="-----BEGIN PUBLIC KEY-----\n...\n-----END PUBLIC KEY-----"
# ...or a mounted file:
GATEWAY_JWT_PUBKEY_FILE=/run/secrets/gateway_jwt_pub.pem

# Signing algorithms the gateway uses (asymmetric only).
GATEWAY_JWT_ALGS=EdDSA,RS256

# Optional: lock tokens to the extension audience (set if the gateway stamps `aud`).
# EXT_JWT_AUDIENCE=ext

# Optional: require a per-customer permission claim so a SLQ token cannot fetch the AirPLAi wasm
# (set per backend, e.g. "ext:slq" for SLQ, "ext:airplay" for AirPLAi).
# EXT_REQUIRED_CLAIM=ext:slq

# Path to the compiled wasm inside the container (defaults set in the Dockerfile).
WASM_PATH=/app/wasm/build/core.wasm

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

_No response_

Claude Model

Sonnet

Relevant Conversation

Impact

Low - Minor inconvenience

Claude Code Version

Opus 4.8

Platform

Anthropic API

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗