Skip to content

bug: Plan mode is not enforced by the application — model can override at will #32520

Closed as not planned

Description

@irybakov

Description

Plan mode is a read-only exploration mode intended to prevent any file changes, commits, or script execution. However, it relies entirely on a system prompt instruction ("MUST NOT make any edits, run any non-readonly tools") with no application-level enforcement.

Actual behavior

Despite the system prompt, the model was able to execute git add, git commit, and git push when the user directly instructed it to, bypassing the Plan mode restriction.

Expected behavior

Plan mode should be enforced at the application/tool level, not the model level. Write tools (edit, write, bash for non-readonly commands, etc.) should be physically blocked or require explicit mode-switching before execution.

This is a security/correctness issue — a model prompt is not enforceable. A mode switch in the application itself is.

Activity

  1. github-actions commented on Jun 16, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    These all describe the same underlying problem: plan mode is enforced via system prompt only and not at the application/tool level.

  2. github-actions commented on Aug 16, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions