Run TUI commands in the active project directory

[oaleynik]

🧢 Changes

Runs commands launched from but tui command mode in the active GitButler project directory.

This applies to both built-in but command mode and shell command mode.

☕️ Reasoning

When but tui is launched with -C <repo>, the TUI displays and operates on that repo through its active Context. However, command mode spawned child processes without setting their working directory, so they inherited the shell’s original cwd.

That could make a user run a command while looking at repo A in the TUI, but accidentally execute it in repo B.

The fix sets the child process cwd to ctx.workdir_or_fail()? before spawning.

CleanShot.2026-07-04.at.17.22.54.mp4

[Copilot]

Pull request overview

This PR fixes but tui command mode so that any child processes spawned from the TUI (both built-in but commands and arbitrary shell commands) run in the active project’s working directory instead of inheriting the user’s original shell CWD. This aligns command execution with the repository the TUI is currently operating on via its Context.

Changes:

• Thread &Context through the TUI message handler into command mode handling.
• Set spawned command processes’ working directory via cmd.current_dir(ctx.workdir_or_fail()?) before execution.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
crates/but/src/command/legacy/status/tui/app/mod.rs	Passes ctx into handle_command so command mode can use the active project context.
crates/but/src/command/legacy/status/tui/app/command_mode.rs	Uses ctx.workdir_or_fail()? to set the child process working directory before spawning commands.