YOU ARE VIEWING ONE ITEM FROM THE AICRIER FEED

Claude Code adds worktree baseRef setting

AICrier tracks AI developer news across Product Hunt, GitHub, Hacker News, YouTube, X, arXiv, and more. This page keeps the article you opened front and center while giving you a path into the live feed.

// WHAT AICRIER DOES

7+

TRACKED FEEDS

24/7

SCRAPED FEED

Short summaries, external links, screenshots, relevance scoring, tags, and featured picks for AI builders.

Claude Code adds worktree baseRef setting
OPEN LINK ↗
// 1h agoPRODUCT UPDATE

Claude Code adds worktree baseRef setting

Claude Code 2.1.133 adds `worktree.baseRef`, letting `--worktree`, `EnterWorktree`, and agent-isolation worktrees branch from either `origin/<default>` or local `HEAD`. It fixes the common “don’t drop my unpushed commits” problem, but it still doesn’t give teams a first-class `origin/dev` base.

// ANALYSIS

This is a real quality-of-life fix for agentic coding, but it’s still opinionated toward trunk-based workflows. Teams running a long-lived integration branch get a partial answer, not the branch-aware worktree control they actually want.

  • `fresh` restores the old default of branching from `origin/<default>`, while `head` preserves local unpushed commits in new worktrees
  • That makes Claude Code safer for multi-step refactors where the current branch already contains important work
  • The gap is obvious for orgs that treat `dev` as the integration branch; there’s still no explicit `origin/dev` option
  • This looks like Anthropic tightening workflow ergonomics around worktrees rather than rethinking the underlying branch model
  • Net effect: better for solo devs and trunk-based teams, still awkward for larger branch-heavy setups
// TAGS
claude-codeclidevtoolcoding-agentagentautomation

DISCOVERED

1h ago

2026-05-08

PUBLISHED

1h ago

2026-05-08

RELEVANCE

9/ 10

AUTHOR

nsxdavid