[P2] Keep bare \new in the thread's bound project #36

Activity

1. MatthewS65537

   added

   bugSomething isn't workingSomething isn't working

   on Oct 11, 2026
2. MatthewS65537 commented on Oct 11, 2026

   

   MatthewS65537

   on Oct 11, 2026

   OwnerAuthor

   More actions

   Proposed fix

   Approach: Bare \new should start the fresh session in the project the thread is already bound to. This matches the rule start.ts:113-117 states ("existing threads keep their own bound dir") and the ctx.thread?.projectDir ?? defaultDir fallback every other command uses (\model, \sessions, \usage, \cmd, \restart). A channel pin still wins, because the \pin contract is "new sessions here start in it". An unbound thread keeps today's behavior.

   Changes:

   src/commands/handlers.ts, \new (line 640):

   -    const dir = ctx.state.defaultDir(ctx.channelId, ctx.cwd);
   +    // Same project as the thread (a pin still wins); unbound threads use the channel default.
   +    const dir = ctx.state.channelProject(ctx.channelId) ?? ctx.thread?.projectDir ?? ctx.state.defaultDir(ctx.channelId, ctx.cwd);
        await rebindThread(ctx, dir, "✨", { teardown: false });

   Help detail (line 631), so the bare form is explicit:

   -  detail: "`\\new /abs/path` also switches the current project. Accepts `~` paths. The previous session is kept (\\resume recovers it).",
   +  detail: "Bare `\\new` stays in this thread's project; `\\new /abs/path` also switches the current project. Accepts `~` paths. The previous session is kept (\\resume recovers it).",

   Tests: in test/commands.test.ts, next to "\new unbinds only…":

   • A thread is bound to /projB and state.setCurrentProject("/launch") simulates a boot. Bare \new must produce getThread("C1:T1").projectDir === "/projB", and currentProjectDir must stay /launch. My probe cc_mnt/review-20261011/commands/new-and-project.test.ts currently shows /launch.
   • With state.setChannelProject("C1", "/pinned") and a thread bound to /projB, bare \new uses /pinned.
   • An unbound thread uses defaultDir (unchanged).

   Risks / interactions:

   • rebindThread canonicalizes the dir and keeps its rebind-race guard ([P1] Prevent an older asynchronous rebind from overwriting newer owner intent #12). The pool lease goes to the thread's dir, which is already the dir its server runs in.
   • Behavior change: someone who relied on bare \new to "follow" a recent \cd from another thread now stays put. \new <path>/\cd remain the explicit way to move.

   Alternatives considered:

   • Stop resetting currentProjectDir on boot: fixes only the restart case, not the "another thread \cd'd elsewhere" case, and reverses a deliberate design.

   Effort: S. Confidence: high

   ---

   Proposal only, not implemented. Sketches are against 22ce7ee.
3. MatthewS65537

   added a commit that references this issue on Oct 13, 2026

   Harden catch-up recovery and fix small command bugs (#33, #35, #36, #37…

   ...

   5fe4ac8