Skip to content

[Bug] Content Security Filter false positive on Russian verb "Разгребать" permanently locks agent chat session #808

Description

@romangalaxys10-spec

Summary & Impact

A severe false-positive trigger in the platform's Content Security / Safety Guardrail filter flags standard, innocuous Russian vocabulary and locks the entire agent chat session, forcing the user to abandon their work and recreate the full project context from scratch.


False Positive Reproduction

  • Trigger Word: "Разгребать" (transliterated: razgrebat).
  • Literal & Idiomatic Meaning: Russian verb meaning "to rake", "to sort through", or "to clear up a backlog / declutter / shovel" (e.g. "разгребать дела" = clearing up tasks/chores; "разгребать завалы кода" = sorting through legacy code).
  • Observed Behavior: The safety classifier flags the input with a content security violation warning, bans/halts the active agent chat session, and offers no appeal or continuation mechanism.

User Report & Discord Context


Root Cause Analysis & Proposed Action

  1. Safety Classifier / Keyword Blocklist Optimization:
    • Update the multilingual safety filter token embeddings/regex allowlist to prevent benign Slavic / Russian verbs containing standard morphological roots (e.g. греб- / грести / разгребать) from false-positive tripping violence or harassment rules.
  2. Session Resilience / Soft Recovery:
    • A content moderation trigger on a single turn should not permanently corrupt or freeze the entire agent session/container.
    • The user should be allowed to edit or delete the flagged turn and continue the existing conversation without having to rebuild multi-step agent environments and context from scratch.

Submitted on behalf of the community by Roman M. (Volunteer / Ambassador).

Activity

  1. github-actions commented on Sep 24, 2026

    @github-actions

    👋 感谢你的反馈,我们已经收到。

    • 维护者看到后会尽快回复你。
    • 状态保持为 status: 待评估,你可以随时补充信息。
    • 信息不全时我们会打上 needs: 更多信息 标签并 @ 你。

    👋 Thanks — we've received your issue.

    • A maintainer will get back to you as soon as we can.
    • Status stays at status: 待评估 (Triage); feel free to add context.
    • If we need more details, we'll add needs: 更多信息 and ping you.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions