Uh oh!
There was an error while loading. Please reload this page.
feat(tool): add interactive terminal tool with vscode auto-attach - #41258
feat(tool): add interactive terminal tool with vscode auto-attach#41258Albertban wants to merge 3 commits into
Conversation
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
The following comment was made by an LLM, it may be inaccurate: Potential duplicate found:
This appears to be a closely related PR addressing similar functionality for interactive terminal tooling with PTY sessions. You may want to review whether #23794 is already merged, closed, or if it overlaps with the current PR #41258. |
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
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