Skip to content

[RFE] Tunable "go slow and do not overlook anything" vs "go fast and get things done" prioritization #3006

Description

@ANogin

See #2969 for some examples of Claude Code rushing into things despite explicit rules about needing to ensure correctness first. In general Claude Code seems to be constantly prioritizing action over deliberation, attempting to fix bugs based on the first inkling of what might be causing it instead of at least trying to confirm its hunch, or investigate more properly, etc. I found it extremely counterproductive - it messes up code in ways that often takes extra effort to undo (I try to checkpoint periodically as it is doing its task, but sometimes I am doing my own thing, not watching over it to prevent it going off the rails), does things that it was told in 10 different ways not to do, etc. I wonder whether part of the issue is the system prompt that makes it way to eager to get to the next step. I understand there are cases when this is reasonable, but definitely not for me. I would have preferred a toggle between the current "get to the next steps ASAP" version and "go slowly and make sure not to overlook things" mode that would be way better for me.

Activity

  1. ANogin commented on Jul 10, 2025

    @ANogin
    Author

    Note that this kind of applies both to how Claude acts itself and how it's writing the code to behave: currently it heavily prioritizing writing fallback code, providing default values for all arguments, etc, and it's really hard to convince it to prioritize correctness and create code that aborts when something is missing.

  2. github-actions commented on Dec 5, 2025

    @github-actions

    This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

  3. ANogin commented on Dec 7, 2025

    @ANogin
    Author

    I think this is still relevant. The choice of model and ability to tell it to ultrathink helps somewhat, but would still be helpful to be able to ask it to take more care and not rush.

  4. github-actions commented on Jan 6, 2026

    @github-actions

    This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

  5. github-actions commented on Jan 16, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  6. locked as resolved and limited conversation to collaborators on Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions