Skip to content

Warm existing harness-created worktrees #344

Description

@janicduplessis

Problem

Agent harnesses such as Codex and Claude Code can create a git worktree before the agent starts. Stim already treats that checkout as its own workspace for Metro, devices, builds, status, and logs, but --carry-ignored is available only when Stim creates the worktree. A harness-created worktree can therefore begin without dependencies, Pods, or reusable native output even when the main checkout is warm.

Product direction

Add an explicit way to warm the current existing worktree from its repository's main checkout. Reuse the safe ignored-path and .worktreeexclude behavior from stim worktree create --carry-ignored, but do not copy tracked source or create/switch branches because the harness already owns those decisions.

Do not make stim start, stim doctor, or ordinary builds mutate the checkout automatically. The operation should be opt-in and should refuse outside a linked worktree or when the source checkout cannot be identified safely.

Open decision

Choose the smallest command shape for warming the current worktree without expanding Stim into general project setup. Update the agent guide only if this becomes part of the normal harness-created-worktree workflow.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions