feat(tool): add interactive terminal tool with vscode auto-attach - #41449
Open
Albertban wants to merge 5 commits into
Open
feat(tool): add interactive terminal tool with vscode auto-attach#41449Albertban wants to merge 5 commits into
Albertban wants to merge 5 commits into
Conversation
Contributor
|
The following comment was made by an LLM, it may be inaccurate: Related PR Found:
Why it's related:
This appears to be an enhancement/alternative approach to the existing terminal tool work in #23794, not a true duplicate, but they are closely related features addressing the same problem space. |
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.
Issue for this PR
Closes #
Type of change
What does this PR do?
Adds a
terminaltool to opencode so the agent can open and drive a real interactive PTY (open/read/input/close), and adds VS Code extension support that auto-attaches those sessions into real VS Code terminals via a Pseudoterminal bridge.Differs from the existing open PR #23794 on the same area by:
bashtool.powershell/cmd/bash, defaulting to PowerShell on Windows).\n->\r) — before this, model-sent\ngot stuck in PowerShell's continuation prompt and keystrokes appeared lost.How did you verify your code works?
bun typecheckpasses inpackages/opencode;tsc --noEmitpasses insdks/vscode.Screenshots / recordings
N/A (no UI change beyond the auto-attached terminal).
Checklist