LevelCode editor: activity timeline, approval redesign, error handling + reliability - #2
Merged
ndemianc merged 7 commits intoJul 10, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Long/looping agent runs 401'd (Signature has expired) — only the chat path refreshed the access token on 401; the agent loop was called raw. Add isAgentAuthError + wrap the turn call: on a 401 before any content has streamed, refresh once (via a ctx.refreshAuth hook wired in extension.js), update ctx.apiKey, and retry the turn once. Mid-stream/second failures propagate; BYOK / refresh-failed rethrow. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…rade card ask_user and update_plan panels get a collapse/expand header (plan collapse state persists across re-renders). Plan redesign: professional .ci status icons (check / spinning sync / circle), a progress bar + count pill, refined rows. Free-tier cap (402 cap_reached) now renders a compelling upgrade card (plan-aware: paid users get a Manage-plan button) instead of raw error JSON. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…le in dev apply-branding.mjs prunes orphaned LevelCode extensions from vscode/extensions (renamed-away atom-* copies double-registered commands). run-dev.sh compiles the client only (compile-client), skipping the proprietary Copilot build (stripped/disabled anyway, and broken under Node 24 by a glob CJS/ESM error). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ots, approval redesign Rework the agent's command/tool activity into a connected timeline (rail + nodes). Executed commands render as collapsible GitHub/Copilot-style cards: a Running→Ran header with command chips + live state, the command with lightweight shell syntax highlighting, streamed output visible by default, an exit/duration status foot, and the agent's intent in italics. A Copilot-style falling-dots indicator replaces the spinner while running. run_command approval is redesigned as a quiet Cursor/Claude-style ask card (no macOS-terminal chrome) with Enter/Esc keyboard shortcuts that collapses to a one-line verdict. agent.js posts the command explanation so the card can show the why. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… upgrade card) Pairs with thin.ly's upstream-error sanitizer (PR #341): the gateway now returns a safe, classified error, so the editor picks a calmer presentation. Providers forward the structured error 'code'; agent.js and extension.js pass it along on agentError/assistantError; chat.html adds isServiceIssue + addServiceCard — a neutral notice (amber warning icon, no accent, no CTA) — and routes service_unavailable / service_busy / gateway_error to it, keeping the accent upgrade card reserved for a genuine user-wallet cap. Even if the code fails to propagate, the gateway message is already sanitized, so no raw provider text can reach any branch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
licenseUrl / reportIssueUrl / releaseNotesUrl in product.overlay.json pointed at github.com/levelcode/levelcode; the canonical repo is github.com/levelcodeai/levelcode. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ndemianc
added a commit
that referenced
this pull request
Jul 24, 2026
All five points were real. Two of them made the tool quietly report LESS than the truth, which is the failure mode that matters most for something whose whole job is producing accurate facts. 1. prevTag was interpolated into a shell string. A tag name is repo-controlled but still runtime-discovered input, so this is now defended twice: all git calls go through spawnSync with an argv array (a shell cannot be quoted out of one), and the base tag must match ^vX.Y.Z$ before use. Shape matters independently of injection — a stray v0.9.2-rc1 sorts into the 'v*' glob and would silently produce the wrong range, wrong commit list and wrong compare link. Verified: v0.9.2-rc1, v-wip and "v0.9.2; rm -rf /" are all rejected. 2. PRs were only detected from merge commits, so on a squash-merging repo the list would read "(none detected)" while every subject carried "(#123)". Both shapes are now collected. 3. Suites were keyed by basename, so two extensions with the same test filename would produce an ambiguous "biggest suites" list. Keyed by relative path now. 4. The coverage line printed "N cases in total" while suites whose summary could not be parsed silently contributed 0 — authoritative-sounding and UNDER- reporting. This one bit immediately: 5 of 24 suites do not print a count, so "273 cases in total" was wrong. It now says how many suites were counted and names the ones that were not. 5. The fix/perf heading also carried reverts; renamed to say so. Also fixes a bug I introduced while making #2: prNumbers became a Set, but the renderer still read .length, which is undefined on a Set — so the PR list emptied itself silently. Caught by re-running against the real range (expected #33-36, got "(none detected)"). Materialised to a sorted array. Verified end to end against v0.9.1..HEAD: PRs #33-36 detected, coverage line now honest about the 5 unparsed suites, and all guardrails still fire. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
The full LevelCode editor pass from this cycle. Builds on the atom-* → levelcode-* rename.
Agent activity (chat webview)
Error handling (pairs with thin.ly #341)
Reliability / build
All webview changes were verified in a static harness in both light and dark themes (rail continuity, highlighting, dots animation, collapse/expand, approval Enter/Esc, service card), no console errors.
🤖 Generated with Claude Code