🤖 refactor: auto-cleanup by mux-bot[bot] · Pull Request #3695 · coder/mux

mux-bot · 2026-07-08T16:43:09Z

Summary

This is the long-lived auto-cleanup PR. Each run, the auto-cleanup agent reviews new commits merged to main, rebases onto the latest main, and applies at most one extremely low-risk, behavior-preserving cleanup. The branch accumulates a small stack of independent cleanups until it is merged.

Cleanups in this branch

Dedupe memory sweep recordUsage callbacks (MemoryConsolidationService). The consolidation sweep and the harvest sweep each inlined the same 15-line callback that routes billed usage to the headless-usage sidecar and emits analyticsIngest. Extracted into a private makeSweepUsageRecorder(...) helper.
Dedupe the "memory scope is full" cap check (MemoryService). The create and saveFile (new-file) paths each inlined a byte-identical block that called store.listFiles(), compared the count against MEMORY_MAX_FILES_PER_SCOPE, and threw a MemoryCommandError with the same message. Extracted into a private assertScopeHasRoom(store, scope) helper.
Dedupe blockquote line formatting in the bash monitor wake prompt (bashMonitorWakeStore.ts). buildBashMonitorWakePrompt rendered both the matched-output lines and the lost-monitor script with the identical .map((line) => \> ${line}`).join("\n")blockquote pattern in two places. Extracted into a module-levelblockquoteLines(lines)` helper.
Dedupe the tool_search removal in prepareToolSearch (toolCatalog.ts). Both fallback branches (PTC enabled, and empty deferred catalog) inlined the identical { [TOOL_SEARCH_TOOL_NAME]: _removed, ...rest } destructure to drop the built-in tool_search entry from the tool record. Extracted into a module-level withoutToolSearch(tools) helper.
Dedupe the Anthropic cache-create token extraction in accumulateProviderMetadata (usageHelpers.ts). The function inlined the same verbose (metadata.anthropic as { cacheCreationInputTokens?: number } | undefined)?.cacheCreationInputTokens ?? 0 cast twice (once for the accumulated metadata, once for the current step). Extracted into a module-private getAnthropicCacheCreateTokens(metadata) helper.
Dedupe capability-model thinking-policy resolution (thinking/policy.ts). After 🤖 feat: integrate GPT-5.6 Sol/Terra/Luna with native max effort and pro-mode toggle #3708 taught the thinking policy to resolve mappedToModel aliases, both getThinkingPolicyForModel and hasExplicitThinkingPolicy inlined the identical getExplicitThinkingPolicy(resolveModelForMetadata(modelString, providersConfig ?? null)) call. Extracted into a private getExplicitThinkingPolicyForModel(modelString, providersConfig) helper.
Dedupe queue entry clear-callback projection (messageQueue.ts). After 🤖 feat: queue messages behind special sends instead of erroring (FIFO message queue) #3696 rewrote MessageQueue into FIFO QueueEntry items, both getClearCallbacks and removeWorkspaceTurn inlined the identical spread that builds a QueueClearCallbacks object from an entry's optional onCanceled / onAcceptedPreStreamFailure fields. Extracted into a private entryClearCallbacks(entry) helper.
Dedupe the OpenAI-origin model check in openaiExplicitPromptCachingAvailable (cacheStrategy.ts). After 🤖 feat: GPT-5.6 explicit prompt cache breakpoints for direct OpenAI #3712 added the GPT-5.6 explicit-prompt-caching eligibility gate, the function inlined the identical split(":", 2) + origin !== "openai" || !modelName check twice — once for the request model and once for the resolved capability target — and the destructured origin/modelName locals were unused past their guard in both places. Extracted into a module-private isOpenAIOriginModel(canonical) helper.
Dedupe the tool-call-execution-start emit in StreamManager (streamManager.ts). 🤖 fix: start tool elapsed timers when execute() actually runs #3716 introduced the ToolCallExecutionStartEvent, emitted from two places: applyToolExecutionStart (part already stored) and the "tool-call" case that consumes a pendingExecutionStart recorded before the part landed. Both inlined the byte-identical this.emit("tool-call-execution-start", { type, workspaceId, messageId, toolCallId, timestamp } satisfies ToolCallExecutionStartEvent) block, differing only in the toolCallId/timestamp source. Extracted into a private emitToolCallExecutionStart(workspaceId, streamInfo, toolCallId, timestamp) helper.
Dedupe model-parameter extras merge (aiService.ts). After 🤖 feat: apply mid-turn thinking-level changes at the next model step #3718 added mid-turn thinking-level rebuilds, the initial-model path and the fallback-model path each inlined a byte-identical closure (mergeModelParameterExtras / mergeNextModelParameterExtras) that folds providers.jsonc providerExtras UNDER the Mux-built provider-options namespace (short-circuiting when there are no extras, deep-merging via mergeProviderExtrasUnderMux when the namespace is a plain object). The two differed only in the namespace key and the overrides source. Extracted into a module-level makeModelParameterExtrasMerger(namespaceKey, providerExtras) factory that returns the merger closure.
Unify the legacy tool_search part-rename helper (toolCatalog.ts). 🤖 fix: avoid OpenAI tool search name collision #3719 renamed the built-in tool-search tool to tool_catalog_search and added request-time rewriting of historical tool_search call/result parts. It introduced two byte-identical helpers — renameLegacyToolSearchCallPart(part: ToolCallPart) and renameLegacyToolSearchResultPart(part: ToolResultPart) — that differ only in the part type; the rename body is identical. Collapsed both into a single generic renameLegacyToolSearchPart<T extends { toolName: string }>(part: T) and dropped the now-unused ToolCallPart / ToolResultPart imports.
Trim duplicated context-cap rationale comment (codexOAuth.ts). 🤖 fix: cap GPT-5.6 context over Codex OAuth #3724 added the GPT-5.6 family to CODEX_OAUTH_CONTEXT_WINDOW_OVERRIDES and rewrote the map's inline comment with a sentence that restated the rationale already given in the map's doc comment directly above it. Dropped the duplicated rationale sentence, keeping only the tier-specific explanation. Comment-only; no behavior change. (Re-applied on top of [openai] 🤖 fix: use 372K GPT-5.6 OAuth context #3730, which later rewrote the same inline comment and re-introduced the duplicate.)
Dedupe flat-section pinned block resolution (pinnedReorder.ts). 🤖 feat: project-less scratch chats #3723 added a scratch branch to locatePinnedBlock that renders scratch chats as one flat "Chats" section, mirroring the existing multi-project branch. Both branches inlined the byte-identical collectFlatSectionRows(...).filter(isWorkspacePinned).map((row) => row.id) projection, the if (!pinnedIds.includes(meta.id)) return null guard, and the return { fullOrder: pinnedIds, blockIds: pinnedIds } shape — differing only in the includeRow predicate ((row) => row.kind === "scratch" vs isMultiProject). Extracted into a private locateFlatSectionPinnedBlock(meta, sortedWorkspacesByProject, includeRow) helper.
Dedupe JSON-wrapped tool-output unwrap (workflowRunMessages.ts). 🤖 fix: stop terminal workflow await loops #3725 added isTerminalWorkflowRunToolOutput, which re-inlined the byte-identical output.type === "json" && "value" in output container check already used by stripWorkflowRunRecordForModel to detect the { type: "json", value } SDK/UI wrapper before recursing on the inner value. Extracted the check into a module-private isJsonWrappedOutput(output) helper that both functions call, moving the shared rationale into the helper's doc comment. No control flow or return-shape change.
Hoist errorType local in finalizeWorkspaceTurnFromStreamError (taskService.ts). 🤖 fix: keep workspace-turn handles running through auto-retryable stream errors #3729 reworked workspace-turn stream-error settlement, and the reworked function read event.errorType three times and repeated the event.errorType != null guard once for the explicitRecovery computation and once in the recovery if. Hoisted a single const errorType = event.errorType and routed all uses through it, deduplicating the repeated member access and null guard. ErrorEvent is a Zod-inferred plain data type, so the property read has no side effects; pure behavior-preserving simplification with no control-flow change.
Extract buildSkillDescriptor helper for skill discovery (common/orpc/schemas/agentSkill.ts + agent_skill_list.ts + agentSkillsService.ts). 🤖 feat: skills refresh — invocation control, $ARGUMENTS, dynamic context, .claude compat #3728 (skills refresh) added user-invocable / argument-hint / when_to_use frontmatter and normalized them via resolveSkillAdvertise / resolveSkillUserInvocable / resolveSkillWhenToUse. Both descriptor-building sites — readSkillDescriptor (the agent_skill_list tool) and readSkillDescriptorFromDir (agentSkillsService discovery) — then inlined the byte-identical 7-field object literal mapping parsed.frontmatter + scope into an AgentSkillDescriptor before AgentSkillDescriptorSchema.safeParse. Extracted the mapping into a shared buildSkillDescriptor(frontmatter, scope) in agentSkill.ts (co-located with the resolveSkill* helpers it calls) and dropped the now-unused resolveSkill* imports at both call sites. Callers still run safeParse themselves since they handle validation failure differently. No behavior change.
Hoist duplicated Date.parse(record.createdAt) in the bash monitor delivery gate (workspaceService.ts). 🤖 fix: defer bash monitor wakes during task_await #3732 (defer bash monitor wakes during task_await) reworked the delivery gate in drainBashMonitorWakes so a match is re-checked against the shown frontier while pinned to its originating process instance via Date.parse(record.createdAt). The new non-blocking getMonitorWakeDeliveryState branch and the fallback getSettledShownThroughOffset branch each inlined the identical Date.parse(record.createdAt) call as the originNotAfterMs argument. Hoisted a single const originNotAfterMs = Date.parse(record.createdAt) before the branches (with a clarifying comment on why the origin timestamp pins the check) and routed both calls through it. Date.parse is pure, so the hoist is behavior-preserving.
Dedupe the "wait for any in-flight load" block in DevToolsService (devToolsService.ts). 🤖 fix: clean up devtools.jsonl on archive/remove and reap orphaned session dirs #3733 added removeWorkspaceData (archive/remove DevTools cleanup) directly beside the existing clear; both inlined the byte-identical const pendingLoad = this.loadingPromises.get(workspaceId); if (pendingLoad) { await pendingLoad; } guard that drains any in-flight loadFromDisk before mutating in-memory state so a late load cannot repopulate stale data after the mutation. Extracted into a private awaitPendingLoad(workspaceId) helper with the shared rationale in its doc comment; both call sites keep their situational one-line comment. No control-flow change.
Dedupe MCP OAuth redirect URI resolution (router.ts). Both the global (mcpOauth.startServerFlow) and per-project (projects.mcpOauth.startServerFlow) handlers inlined the byte-identical block that derives the OAuth callback redirectUri from request headers — preferring the Origin header (used verbatim when it parses as a URL), then falling back to x-forwarded-host/host with the forwarded proto (defaulting to http), and returning Err("Missing Host header") when no usable Host header exists. Extracted into a module-level resolveMcpOauthRedirectUri(headers) helper that returns the resolved URI or undefined; each handler now maps undefined to the same Err. startServerFlow is async (its returned promise is passed through unawaited), so moving the call out of the origin-branch try cannot change behavior — the try only ever guarded the synchronous new URL(...) construction. No header semantics or return-shape change.

This run

Considered origin/main from the previous checkpoint 0890eb050 through bb8c97542 (HEAD), covering the one new commit merged since the last run:

ci: migrate visual regression testing from Chromatic to Coder Pixel (🤖 ci: migrate visual regression testing from Chromatic to Coder Pixel #3736, bb8c97542)
Cleanup 🤖 docs(bash): timeout_secs description—start small, retry backoff; avoid large defaults for UX #19 taken (see above). 🤖 ci: migrate visual regression testing from Chromatic to Coder Pixel #3736 was a CI/Storybook migration (CI/workflow edits are out of scope for cleanups), so this run targets adjacent duplication instead: the two MCP OAuth startServerFlow handlers in router.ts each inlined the identical redirect-URI resolution; extracted into a shared resolveMcpOauthRedirectUri helper.
Checkpoint advanced to bb8c97542 so the commit is marked considered (one cleanup taken this run).

Validation

Rebased cleanly onto origin/main (bb8c97542); all prior cleanups replayed without conflict and the branch merges cleanly into main.
make static-check passes fully — ESLint, both TypeScript configs, Prettier, shell formatting (shfmt), generated-file/doc-sync checks, code-to-docs links, shellcheck, and hadolint.

Risks

Very low. Each cleanup is a behavior-preserving simplification that extracts byte-identical inlined logic into a helper (or, for #15 and #17, hoists a repeated side-effect-free property read / pure call into a local) — no control flow, arguments, thresholds, error types, emitted events, validation, or rendered text change. Cleanup #16 adds a helper in the shared skill-schema module consumed by both discovery paths; both call sites still validate via AgentSkillDescriptorSchema.safeParse, so descriptor output is unchanged. The sole comment-only cleanup (#12) touches no executable code. Cleanup #19 touches the MCP OAuth redirect-URI resolution (a security-sensitive path) but preserves the exact header-parsing logic, proto defaulting, and Missing Host header error; its only structural change — moving the async startServerFlow call out of the origin-branch try — is inert because the returned promise is passed through unawaited, so the try never guarded anything beyond the synchronous new URL(...).

Auto-cleanup checkpoint: bb8c975

Generated with mux • Model: anthropic:claude-opus-4-8 • Thinking: xhigh • Cost: $0.00

mux-bot · 2026-07-08T16:43:16Z

@codex review

chatgpt-codex-connector · 2026-07-08T16:43:21Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-08T17:04:18Z

⚠️ Auto-fixup: CI failure appears to be infrastructure/flaky, not caused by this cleanup commit — no code pushed.

Root cause: The Static Checks job failed with the runner annotation "The self-hosted runner lost communication with the server" after running the full 10m, and its log blob was never uploaded (BlobNotFound). Test / Integration was cancelled and Required failure are both downstream of that (Required only aggregates results).

Verification: Ran make static-check locally on this PR's HEAD (a2454d31b). ESLint, both TypeScript configs (tsgo --noEmit ×2), and Prettier all pass. The only local miss is fmt-shell-check because shfmt isn't installed in the fixup sandbox — and this PR changes no shell files, so it's irrelevant.

Recommendation: Re-run the failed CI jobs. No code change needed.

mux-bot · 2026-07-09T00:30:58Z

@codex review

Latest push rebases onto origin/main (through #3698) and adds one low-risk, behavior-preserving cleanup: extract the duplicated per-scope "memory scope is full" cap check in MemoryService.create / saveFile into a private assertScopeHasRoom(store, scope) helper. No control flow, thresholds, error types, or events change. make static-check (ESLint + both tsconfigs + Prettier) and bun test memoryService.test.ts (75/0) pass locally.

chatgpt-codex-connector · 2026-07-09T00:31:07Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-09T09:11:10Z

@codex review

New in this run: cleanup #3 — deduped the identical blockquote line-prefixing (> per line, joined by newlines) in buildBashMonitorWakePrompt into a module-level blockquoteLines(lines) helper. Behavior-preserving; validated by the existing buildBashMonitorWakePrompt output-format tests (21/21 pass).

chatgpt-codex-connector · 2026-07-09T09:11:18Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-09T20:39:20Z

@codex review

chatgpt-codex-connector · 2026-07-09T20:39:25Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-10T00:31:11Z

@codex review

Added auto-cleanup #5: getCodexOauthContextLimit now reuses the already-resolved, non-null compatibilityModelId with the isCodexOauthAllowedModelId / isCodexOauthRequiredModelId variants instead of re-invoking isCodexOauthAllowedModel / isCodexOauthRequiredModel (which re-derive the same id and re-scan providersConfig). Behavior-preserving; targeted tests + make static-check (minus sandbox-only shfmt) pass.

chatgpt-codex-connector · 2026-07-10T00:31:17Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-10T09:08:42Z

@codex review

Added cleanup #6: extracted a module-private getAnthropicCacheCreateTokens(metadata) helper in usageHelpers.ts to dedupe two byte-identical Anthropic cache-create token reads inside accumulateProviderMetadata. Behavior-preserving; rebased onto latest main (checkpoint ec47caf).

chatgpt-codex-connector · 2026-07-10T09:08:50Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-10T16:48:10Z

@codex review

chatgpt-codex-connector · 2026-07-10T16:48:16Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-11T00:26:32Z

@codex review

Added cleanup #7: deduped the byte-identical QueueClearCallbacks projection in MessageQueue.getClearCallbacks and removeWorkspaceTurn into a private entryClearCallbacks(entry) helper (behavior-preserving). Rebased onto latest main and advanced the checkpoint to 956ac533e.

chatgpt-codex-connector · 2026-07-11T00:26:40Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-12T00:27:26Z

@codex review

This run adds one behavior-preserving cleanup (#8 in the branch list): dedupes the two identical openai-origin model checks in openaiExplicitPromptCachingAvailable (cacheStrategy.ts, introduced by #3712) into a module-private isOpenAIOriginModel(canonical) helper. The destructured origin/modelName locals were unused past their guard. Rebased onto origin/main (48722b9); make static-check passes (except fmt-shell-check, which needs shfmt unavailable in this env) and the cacheStrategy/providerOptions test suites pass (173).

chatgpt-codex-connector · 2026-07-12T00:27:35Z

To use Codex here, create a Codex account and connect to github.

chatgpt-codex-connector · 2026-07-15T20:30:27Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-15T20:41:49Z

🤖 Auto-fixup diagnosis: flaky test, no code fix pushed.

CI run 29448420645 failed only in Test / Integration with a single failing test:

● Runtime integration tests › SSHRuntime sync does not import stale remote tracking refs
  › initWorkspace repairs a reusable snapshot whose base repo is missing objects

thrown: "Exceeded timeout of 120000 ms for a test."
  at tests/runtime/runtime.test.ts:1835

Why this is flaky and not caused by the cleanup commit:

It's a per-test timeout (120s exceeded), not an assertion failure. The full runtime.test.ts suite ran ~245s, so a slow SSH/git integration test simply overran its budget on this runner.
This PR touches no test files and none of the cleanup-touched files sit on the SSH initWorkspace / git-snapshot-repair code path. Touched files are unrelated refactors (helper extraction, local-variable hoisting, dedup) in AI/skills/tokens/schema/service modules.
The only taskService reference in runtimeFactory.ts (the module this test imports) is a comment, and the taskService change is a no-op errorType hoist in the stream-error finalization path — unrelated to runtime init.
All other jobs (Static Checks, Unit, E2E, Storybook, Windows, Builds) passed; sendMessage.errors self-recovered on retry.

No code changes are safe or warranted here. Recommend re-running the failed job; this should pass on retry.

Generated with mux • Model: anthropic:claude-opus-4-8 • Thinking: xhigh

mux-bot · 2026-07-16T08:54:13Z

@codex review

chatgpt-codex-connector · 2026-07-16T08:54:20Z

To use Codex here, create a Codex account and connect to github.

mux-bot · 2026-07-16T16:35:45Z

@codex review

Added cleanup #18: extracted a private awaitPendingLoad(workspaceId) helper in DevToolsService to dedupe the byte-identical in-flight-load drain that clear and the new removeWorkspaceData (from #3733) both inlined. Behavior-preserving; checkpoint advanced to 0890eb050.

chatgpt-codex-connector · 2026-07-16T16:35:52Z

To use Codex here, create a Codex account and connect to github.

Extract the byte-identical consolidation/harvest sweep `recordUsage` callbacks in MemoryConsolidationService into a shared `makeSweepUsageRecorder` helper. Behavior-preserving: same sidecar recording and analyticsIngest emit; only the workspaceId source and analyticsSource literal differ per call site. Auto-cleanup checkpoint: f7f0f02

Both fallback branches in prepareToolSearch inlined the identical { [TOOL_SEARCH_TOOL_NAME]: _removed, ...rest } destructure to drop the built-in tool_search entry from the record. Extract a module-level withoutToolSearch(tools) helper; output is byte-identical.

accumulateProviderMetadata inlined the same verbose (metadata.anthropic as { cacheCreationInputTokens?: number }).cacheCreationInputTokens ?? 0 cast twice. Extracted a module-private getAnthropicCacheCreateTokens(metadata) helper. Behavior-preserving; the displayUsage.ts site is intentionally left alone because its chain has an extra usage.inputTokenDetails.cacheWriteTokens fallback.

Both getThinkingPolicyForModel and hasExplicitThinkingPolicy inlined the identical getExplicitThinkingPolicy(resolveModelForMetadata(model, providersConfig ?? null)) call after #3708 added alias resolution to each. Extract a private getExplicitThinkingPolicyForModel helper; behavior-preserving.

Both eligibility gates in openaiExplicitPromptCachingAvailable inlined the identical split(":", 2) + `origin !== "openai" || !modelName` check (once for the request model, once for the resolved capability target). The destructured origin/name locals were unused past their guard. Extracted into a module-private isOpenAIOriginModel(canonical) helper. Behavior-preserving.

renameLegacyToolSearchCallPart and renameLegacyToolSearchResultPart were byte-identical except for their part type. Collapse them into a single generic renameLegacyToolSearchPart<T extends { toolName: string }> and drop the now-unused ToolCallPart/ToolResultPart imports. Behavior-preserving.

The CODEX_OAUTH_CONTEXT_WINDOW_OVERRIDES doc comment already explains that these caps are kept separate from model metadata so API-key requests retain the public window. #3724 rewrote the inline comment to restate the same point, so trim the duplicated sentence and keep only the tier-specific rationale. Comment-only; behavior-preserving.

Dedupe the repeated event.errorType member access and the duplicated event.errorType != null guard introduced by #3729 into a single local const. Pure behavior-preserving simplification; ErrorEvent.errorType is a plain Zod-inferred data property with no side effects.

…very gate

mux-bot · 2026-07-18T00:33:00Z

@codex review

This run adds cleanup #19: deduped the byte-identical MCP OAuth redirectUri resolution shared by the global and per-project startServerFlow handlers in router.ts into a resolveMcpOauthRedirectUri helper. Behavior-preserving — the async startServerFlow call moved out of the origin-branch try is inert since its returned promise is passed through unawaited (the try only guarded the synchronous new URL(...)).

chatgpt-codex-connector · 2026-07-18T00:33:06Z

To use Codex here, create a Codex account and connect to github.

mux-bot Bot force-pushed the auto-cleanup branch from a2454d3 to 450337d Compare July 8, 2026 17:01

mux-bot Bot force-pushed the auto-cleanup branch from 450337d to e32952d Compare July 9, 2026 00:30

mux-bot Bot force-pushed the auto-cleanup branch from e32952d to d8d0ba5 Compare July 9, 2026 09:10

mux-bot Bot force-pushed the auto-cleanup branch from d8d0ba5 to 78cd7b2 Compare July 9, 2026 20:38

mux-bot Bot force-pushed the auto-cleanup branch from 78cd7b2 to a676f79 Compare July 10, 2026 00:30

mux-bot Bot force-pushed the auto-cleanup branch from a676f79 to 32928e3 Compare July 10, 2026 09:08

mux-bot Bot force-pushed the auto-cleanup branch from 32928e3 to 8afce4c Compare July 10, 2026 16:47

mux-bot Bot force-pushed the auto-cleanup branch from 8afce4c to 990576b Compare July 11, 2026 00:26

mux-bot Bot force-pushed the auto-cleanup branch 2 times, most recently from cd778d7 to 08734b9 Compare July 12, 2026 00:27

mux-bot Bot force-pushed the auto-cleanup branch from 08734b9 to b42facd Compare July 13, 2026 12:53

mux-bot Bot force-pushed the auto-cleanup branch from cbefdbe to 0fbce7b Compare July 16, 2026 08:53

mux-bot Bot force-pushed the auto-cleanup branch from 0fbce7b to 3242eef Compare July 16, 2026 16:35

mux-bot Bot added 19 commits July 18, 2026 00:18

🤖 refactor: dedupe memory scope-full cap check into helper

ce2c020

refactor: dedupe blockquote line formatting in bash monitor wake prompt

df37ec7

refactor: dedupe queue entry clear-callback projection in MessageQueue

2ce73e0

refactor: dedupe tool-call-execution-start emit in StreamManager

156f997

refactor: dedupe model-parameter extras merge in aiService

6438630

refactor: dedupe flat-section pinned block resolution in pinnedReorder

65cfd88

refactor: dedupe JSON-wrapped tool-output unwrap in workflowRunMessages

5f5b80f

refactor: extract buildSkillDescriptor helper for skill discovery

aadba15

refactor: hoist duplicated Date.parse(createdAt) in bash monitor deli…

526ad02

…very gate

refactor: extract awaitPendingLoad helper in DevToolsService

990df93

refactor: dedupe MCP OAuth redirect URI resolution in router

8df1538

mux-bot Bot force-pushed the auto-cleanup branch from 3242eef to 8df1538 Compare July 18, 2026 00:32

Uh oh!

Conversation

mux-bot Bot commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Cleanups in this branch

This run

Validation

Risks

Uh oh!

mux-bot Bot commented Jul 8, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 8, 2026

Uh oh!

mux-bot Bot commented Jul 8, 2026

Uh oh!

mux-bot Bot commented Jul 9, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 9, 2026

Uh oh!

mux-bot Bot commented Jul 9, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 9, 2026

Uh oh!

mux-bot Bot commented Jul 9, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 9, 2026

Uh oh!

mux-bot Bot commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

mux-bot Bot commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

mux-bot Bot commented Jul 10, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 10, 2026

Uh oh!

mux-bot Bot commented Jul 11, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 11, 2026

Uh oh!

mux-bot Bot commented Jul 12, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 12, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 15, 2026

Uh oh!

mux-bot Bot commented Jul 15, 2026

Uh oh!

mux-bot Bot commented Jul 16, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 16, 2026

Uh oh!

mux-bot Bot commented Jul 16, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 16, 2026

Uh oh!

mux-bot Bot commented Jul 18, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jul 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

mux-bot Bot commented Jul 8, 2026 •

edited

Loading