fix(terminal): prevent project action commands from getting stuck by amitray007 · Pull Request #6338 · pingdotgg/t3code

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

amitray007 · 2026-08-12T15:22:42Z

What Changed

Prevent project-action commands from getting stuck above the prompt when the terminal has not been opened yet.
On supported POSIX shells, run the initial action command after interactive shell initialization, then return to the normal interactive shell when it exits.
Keep the terminal open through Ctrl+C so stopping a long-running action returns to a usable prompt instead of closing the terminal.
Preserve the existing terminal-write path for running terminals, older remote servers, Windows PowerShell/cmd, and unsupported custom shells.

Fixes#6337.

Why

Project actions previously opened the terminal and immediately sent the command through a separate terminal write. When the terminal had never been opened, interactive shell initialization could race that write, leaving commands such as npm run dev stuck above the new prompt without executing.

The fix includes the command in fresh terminal startup where supported and has the server acknowledge whether it handled the command. This removes the race while preserving the existing fallback behavior for Windows, unsupported shells, running terminals, and older servers.

UI Changes

Before	After

Before: With the terminal unopened, the project-action command could get stuck above the initialized prompt without executing.

After: The command executes exactly once after shell initialization. Stopping a long-running command with Ctrl+C returns to a usable prompt without closing the terminal.

Verification

vp test run packages/contracts/src/terminal.test.ts apps/server/src/terminal/Manager.test.ts — 80 tests passed
Regression coverage confirms a running terminal restarted by a launch-context change handles the action during the new shell startup
Focused formatting and lint checks for all five changed files
@t3tools/contracts, t3, and @t3tools/web typechecks
Web UI pass with the t3-testing project: a long-running custom action executed exactly once when launched with the terminal previously unopened
User-confirmed retest: the action streamed output, Ctrl+C returned to the prompt, and the terminal remained usable
Exact zsh PTY lifecycle pass: stop a long-running startup command with Ctrl+C, receive the prompt, and run a second command in the same terminal
Windows fresh-shell arguments are covered by a regression test; Windows runtime behavior was not manually tested

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Prepared with GPT-5.6 Codex in T3 Code.

Note

Prevent project action commands from getting stuck by running them during terminal startup

Adds an initialCommand field to TerminalOpenInput and an initialCommandHandled flag to TerminalSessionSnapshot in the contract schemas.
On supported POSIX shells (zsh, bash, sh), the terminal manager spawns the shell with -i -c to run the command, traps INT to avoid early exit, then execs back into the interactive shell.
The client in ChatView.tsx passes initialCommand when opening a terminal for a project script and only falls back to writing the command if the server did not set initialCommandHandled: true.
Windows and unsupported shells skip the startup injection path entirely.
Behavioral Change: project script commands now run inside the shell startup sequence rather than being written to stdin after the shell opens, changing how INT signals are handled during execution.

^{Macroscope summarized 59b7e5a.}

Note

Medium Risk
Changes terminal spawn arguments and project-action execution paths; POSIX startup uses embedded shell -c with user-supplied commands, though existing write fallback and version skew handling limit blast radius.

Overview
Fixes project actions that could appear above the prompt without running when the terminal had never been opened, by racing shell init against a separate write.

Contracts add optional initialCommand on TerminalOpenInput and initialCommandHandled on TerminalSessionSnapshot so the client knows whether the server ran the command at spawn.

Server (Manager.ts): on fresh POSIX spawns (zsh/bash/sh), rewrites shell args to run the command via interactive -c, traps INT so Ctrl+C stops the action but keeps an interactive shell (exec back into the normal shell). Returns initialCommandHandled: true only when that path runs; Windows and an already-running session do not use it.

Web (ChatView.tsx): project scripts pass initialCommand on openTerminal and only fall back to the legacy writeTerminal path when initialCommandHandled !== true (older servers, Windows, reused terminals).

^{Reviewed by Cursor Bugbot for commit 59b7e5a. Bugbot is set up for automated code reviews on this repo. Configure here.}

coderabbitai · 2026-08-12T15:22:55Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d10704-5f66-4965-a525-45c16181bdbb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

macroscopeapp · 2026-08-12T16:14:34Z

Approvability

Verdict: Needs human review

This PR changes how terminal commands are executed by embedding them in shell spawn arguments rather than writing to the terminal after startup. The shell command construction logic and platform-specific behavior changes warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 0919e076d012a610a5d3d628b2765ee6cf2239bc. Configure here.}

amitray007 · 2026-08-21T15:49:39Z

Won't be able to maintain this PR anymore. Feel free to use the code if needed, using a personal fork going forward.

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

github-actionsBot added vouch:unvouched PR author is not yet trusted in the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Aug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0da3209 to e00060aCompare August 12, 2026 15:50

amitray007 marked this pull request as ready for review August 12, 2026 16:05

amitray007 changed the title ~~fix(web): run project actions in fresh terminals~~fix(terminal): prevent project action commands from getting stuckAug 12, 2026

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from e00060a to 0919e07Compare August 14, 2026 18:33

cursorBot reviewed Aug 14, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

fix(terminal): prevent project action commands from getting stuck
59b7e5a

amitray007 force-pushed the agent/fix-project-action-fresh-terminal branch from 0919e07 to 59b7e5aCompare August 14, 2026 18:52

amitray007 mentioned this pull request Aug 16, 2026
fix(terminal): prevent project action commands from getting stuck TheBlankClub/t3code-alpha#8
Merged
4 tasks

simon-curtis mentioned this pull request Aug 17, 2026
feat(terminal): let users choose their default shell #6125
Closed
4 tasks

amitray007 closed this Aug 21, 2026

Uh oh!

Conversation

amitray007 commented Aug 12, 2026• edited by macroscopeapp BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Changed

Why

UI Changes

Verification

Checklist

Prevent project action commands from getting stuck by running them during terminal startup

Uh oh!

coderabbitaiBot commented Aug 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

macroscopeappBot commented Aug 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Approvability

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

amitray007 commented Aug 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

amitray007 commented Aug 12, 2026• edited by macroscopeapp BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Changed

Why

UI Changes

Verification

Checklist

Prevent project action commands from getting stuck by running them during terminal startup

Uh oh!

coderabbitaiBot commented Aug 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

macroscopeappBot commented Aug 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Approvability

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

amitray007 commented Aug 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

amitray007 commented Aug 12, 2026• edited by macroscopeapp BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Changed

Why

UI Changes

Verification

Checklist

Prevent project action commands from getting stuck by running them during terminal startup

Uh oh!

coderabbitaiBot commented Aug 12, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

amitray007 commented Aug 12, 2026•
edited by macroscopeapp Bot
Loading

coderabbitaiBot commented Aug 12, 2026•
edited
Loading

macroscopeappBot commented Aug 12, 2026•
edited
Loading

amitray007 commented Aug 12, 2026•
edited by macroscopeapp Bot
Loading

coderabbitaiBot commented Aug 12, 2026•
edited
Loading

macroscopeappBot commented Aug 12, 2026•
edited
Loading

amitray007 commented Aug 12, 2026•
edited by macroscopeapp Bot
Loading

coderabbitaiBot commented Aug 12, 2026•
edited
Loading

macroscopeappBot commented Aug 12, 2026•
edited
Loading

amitray007 commented Aug 12, 2026•
edited by macroscopeapp Bot
Loading

coderabbitaiBot commented Aug 12, 2026•
edited
Loading

macroscopeappBot commented Aug 12, 2026•
edited
Loading