Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #4769 +/- ##
==========================================
+ Coverage 55.40% 55.68% +0.27%
==========================================
Files 1762 1763 +1
Lines 114271 115327 +1056
Branches 25547 25899 +352
==========================================
+ Hits 63313 64220 +907
- Misses 42216 42342 +126
- Partials 8742 8765 +23
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
lulusir
changed the title
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1786069412.0 |
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1787197346.0 |
|
|
lulusir
force-pushed
the
codex/improve-acp-error-message
branch
from
August 21, 2026 07:54
40cedb8 to
f72da1d
Compare
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1787303337.0 |
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1787646115.0 |
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1788150617.0 |
Update stale side-entry and lifecycle expectations. Wait for prompt acceptance and discovery convergence.
Retain submitted prompts in thread replay history. Suppress matching Agent echoes to avoid duplicate user rows.
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1788253557.0 |
Strip the reserved WebMCP usage hint from restored user turns. Keep the Agent prompt enrichment unchanged.
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1788263965.0 |
…ws from stacking Loading a long historical ACP session froze the main thread for tens of seconds and the restored assistant rows visually stacked over each other. Freeze (profiled via DevTools trace, ~30s scripting): - react-highlight never sets a language- class, so highlight.js ran auto-detection over every full-size tool argument/result block at mount. Oversized blocks now render as plain text; sized blocks highlight with an explicit language (plaintext fallback). - every code block mount fired a leading-edge scrollIntoViewIfNeeded during the React commit (7s of forced layout). Restored blocks skip the mount scroll; streaming updates still follow output. - the attach snapshot rebuilt the whole ChatModel and remounted every row even when the transcript was identical. restoreLoadedSession now skips replacement when message ids match. Stacking (geometry verified in a headless Chromium loop): - createMessageByAI/User clobbered an object-passed className with the undefined second argument, so chat_with_more_actions never reached the DOM and the absolutely positioned action bar (bottom: -40px) painted over the next message row. Propagate the object className and reserve an in-flow strip (thinking_container padding, bar at bottom: 0). - also adds the message/thinking-result copy actions and a 20px top margin for assistant rows in the chat panel.
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1789996105.0 |
Contributor
Author
|
/next |
Contributor
|
🎉 PR Next publish successful! 3.9.1-next-1790001292.0 |
TUI programs running inside the terminal (opencode, vim, tmux etc.) set the clipboard by emitting OSC 52 sequences. xterm.js core does not register a handler for this identifier, so the sequence was silently dropped. In web/remote scenarios the native command fallback (osascript, xclip...) writes the clipboard of the machine hosting the backend instead of the user's browser clipboard, leaving copy features broken. Register an OSC 52 handler on each XTerm instance, decode the base64 payload as UTF-8 and write it through IClipboardService. Query sequences (payload '?') and malformed payloads are ignored without affecting normal terminal output.
This branch has not been deployed
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
2 participants
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.
Types
Background or solution
Agentic task startup previously had several lifecycle and usability gaps around ACP process capacity:
This PR introduces bounded ACP standby capacity managed by the Node-side process pool. It keeps at most one compatible standby process within the configured limit while always prioritizing foreground task launches. Failed or cancelled launches release temporary resources and preserve the task draft and unsent prompt for retry.
It also improves ACP error normalization by:
Agent Task project management, task statuses, dialogs, tooltips, accessibility labels, and recovery messages are now localized in English and Chinese.
Unit, BDD, mock-agent, and Playwright coverage has been added for capacity handling, cancellation, cleanup, error guidance, and recovery.
Verification performed:
node --check test/bdd/fixtures/acp-agent/mock-acp-agent.mjsyarn workspace @opensumi/playwright buildgit diff --checkFull browser E2E execution was not run.
Changelog