Skip to content

Start new worktrees with a warm build directory #953

Description

@shiny-code-bot

Objective

Every new worktree starts with an empty build directory. On 2026-09-19, with kache at an 89% hit rate, the first codex-core test build in a fresh worktree still took over ten minutes, and each worktree's build directory is about 60 GB.

Finish Line

Creating a worktree with dev-worktree yields a build directory warm enough that the first focused test run starts in under two minutes, without sharing a mutable target directory between worktrees.

Current Status

State: parked outside the milestones.
Parked until fresh-start work records at least two cold first builds of a new worktree that take more than 10 minutes and delay milestone work. The fix belongs with the owner of the dev-worktree host tooling, not in this repository.
Next action: none until then.
Blocked by: no native issue blocker.
Last verified: 2026-09-26 backlog reconciliation against the merged DIRECTION.md.

Scope

  • In: an APFS-cloned template target created from a recent main build and cloned by dev-worktree (clones are free and stay independent, which respects the no-shared-mutable-target rule); or whatever the measurement shows is the real cost.
  • Out: sharing one target directory between worktrees; changes to kache itself.

Acceptance Criteria

  • Cold-start time broken down by cause.
  • Chosen approach implemented in dev-worktree.
  • First focused run under two minutes, measured three times.

Relationships

Related: #942 (dogfood pivot), milestone "Codex Lab Fast Feedback Loop" (#638, #639, #640, #814). Related: #855 (target retention), #853 (latency and disk budgets).

Validation

Time from dev-worktree to first passing focused test, before and after.

Decisions

None yet.

Open Questions

Whether a cloned target survives the absolute-path and fingerprint checks cargo applies when the workspace path differs.

Activity

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

    planDurable planning issueplan:waitingDurable plan parked pending a decision, event, or non-issue condition; not for PR QA

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions