Claude Version Picker banner
REPOZY REPOZY

Claude Version Picker

Development community

Description

Windows wrapper that let's you chose between 2 different Claude Code versions you want to use. Simply enter the "claude" command and chose which version to launch — pin a stable build for daily work while keeping the latest version a keystroke away

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Claude Code Version Picker

A lightweight Windows wrapper that turns the `claude` command into a version chooser — keeping a pinned stable version for daily work while giving you instant access to the latest release.

PS> claude

Choose Claude Code version:
  1) v2.1.110    Pinned daily-work version
  2) latest      Current installed version
  d) doctor      Diagnostics
  h) help        Help
  q) quit
Choose:

Why

Anthropic ships Claude Code updates frequently. New versions bring access to newer models (e.g. Opus 4.7 requires v2.1.111+), but a recurring pattern in the Claude Code community is that certain updates change agentic behaviour in ways that feel less reliable for complex, multi-step work — things like long-horizon planning, context management across large codebases, following multi-part instructions without drift, and unexpectedly high token consumption within a single session.

Version recommendations

**v2.1.110 — best all-around.** The last release before Opus 4.7 (introduced in v2.1.111), with all security and stability fixes from April 7–15 included. The effort default is `high` from v2.1.94, but `/effort medium` restores lighter behavior. Recommended for users who want a mature, well-tested binary without the Opus 4.7 transition and without sacrificing security hardening.

**Important nuance:** a majority of "worse planning / lazier / heavier" complaints in the community are actually tied to model and serving changes on Anthropic's side — changes that affect all CLI versions equally and cannot be avoided by pinning any specific binary. The CLI version controls defaults and tooling; it does not pin the model's reasoning behaviour. No pinned CLI version is a guarantee against model-level regressions.

This picker makes it easy to keep your preferred stable binary for day-to-day work while having the latest version available for when you need newer models or features — without any manual PATH swapping or re-installing.

How it wo