Repository navigation
feat(web): run shell code blocks in terminal - #97
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
incognitojam
force-pushed
the
t3code/add-run-command-button
branch
from
August 12, 2026 11:58
3b23281 to
bacb611
Compare
incognitojam
force-pushed
the
t3code/add-run-command-button
branch
from
August 12, 2026 12:00
bacb611 to
7663781
Compare
incognitojam
enabled auto-merge (squash)
August 12, 2026 12:01
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 12, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 12, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 14, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. ## Screenshots Before:  After:  ## Verification - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
incognitojam
added a commit
that referenced
this pull request
Aug 15, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 18, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 18, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 18, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
incognitojam
added a commit
that referenced
this pull request
Aug 19, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 20, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
yngatech-nightly Bot
pushed a commit
that referenced
this pull request
Aug 21, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
incognitojam
added a commit
that referenced
this pull request
Aug 27, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
incognitojam
added a commit
that referenced
this pull request
Aug 28, 2026
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually. This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only. The change includes focused rendering coverage and user-facing documentation. Before:  After:  - 18 focused web tests - Web typecheck - Targeted lint and formatting checks - Integrated web-client fixture confirming the action is visible and enabled on a completed sh fence --- Written by an agent (T3 Code, gpt-5.6-sol).
incognitojam
pushed a commit
that referenced
this pull request
Oct 6, 2026
…otgg#13060) Co-authored-by: Julius Marminge <[email protected]> Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]> (cherry picked from commit 66129c6) Fork adaptation: Replaces the fork's own Run in terminal action (fork #97) with this one rather than keeping both. The fork's version also offered bat, cmd, nu, ps1 and shellscript fences and showed the action on an unclosed fence; neither had a recorded reason. Its run-shell-code-blocks ledger entry, MessagesTimeline test and terminal icon go with it, and the terminal guide's screenshot shows the new play icon. Upstream-PR: 13060
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent replies can contain ready-to-run shell commands, but fenced code blocks only exposed line-wrap and copy actions. Running one meant copying it, opening a terminal, and pasting it manually.
This adds a Run in terminal action for recognized shell fences in completed assistant replies. It uses the existing project-script terminal launcher, so commands run in the correct workspace, reuse an idle terminal, and get a new terminal when the current one has a running process. Source-code and streaming fences stay copy-only.
The change includes focused rendering coverage and user-facing documentation.
Screenshots
Before:
After:
Verification
Written by an agent (T3 Code, gpt-5.6-sol).