indexzero / indexzero/try.rs

[TUI]: Prepopulate Ctrl-G destination with Worktrunk worktree path

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Existing issues
  • I searched the existing issues for this interaction.
Current workflow

try worktree <name> creates a detached Git worktree under the tries directory. When that experiment becomes permanent, selecting it in try and pressing Ctrl-G opens the graduate destination prompt.

Today the default is derived from TRY_PROJECTS and the date-stripped try basename. For example:

/Users/cjr/src/tries/2026-07-16-extract-google-ai-serp
→ /Users/cjr/src/extract-google-ai-serp

That default does not match the permanent worktree layout managed by Worktrunk (wt), so it must be replaced manually on every graduation.

Proposed interaction

When the selected try is a Git worktree, Ctrl-G should prepopulate the destination using the Worktrunk worktree directory and name convention.

For this example, the proposed value is:

/Users/cjr/indexzero/0x-worktrees/try-extract-google-ai-serp

The date prefix should be removed from the try basename, and the permanent worktree name should be prefixed with try-.

The prompt must remain editable before confirmation.

Why this improves the TUI

Graduation is the transition from an experiment to a maintained worktree. Prepopulating the actual permanent-worktree location removes repetitive path editing and makes Ctrl-G align with the existing wt workflow.

Acceptance criteria
  • Ctrl-G recognizes when the selected try is a Git worktree.
  • The graduate prompt defaults to the corresponding Worktrunk worktree path.
  • 2026-07-16-extract-google-ai-serp produces a worktree name of try-extract-google-ai-serp.
  • The default path for the example is /Users/cjr/indexzero/0x-worktrees/try-extract-google-ai-serp.
  • The destination remains editable.
  • Escape cancels without moving the worktree.
  • Non-worktree tries retain an appropriate TRY_PROJECTS-based default.
  • Tests cover the inferred name, destination, editing, and cancellation behavior.
try version

try v0.1.0

Shell

zsh

Additional context

This concerns the destination proposed by the existing script_ascend/Ctrl-G workflow, not the initial detached worktree created by try worktree.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing script_ascend/Ctrl-G workflow and the handling of selected Git worktrees, then run the relevant TUI tests or interaction locally. Done means the prompt infers the date-stripped try name with a try- prefix, uses the Worktrunk destination, remains editable, supports Escape cancellation, preserves non-worktree defaults, and has tests for these behaviors.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, rust, zsh
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.