Pimp My IDE / garage dispatchBack to the garage
October 11, 2026 / inline repair / action authority

A Fix button needs a torque setting.

The same diagnostic action can ask for an explanation or let an agent change the project. Put the mode, limits, and proof beside the trigger.

One label should not hide two levels of authority.
DIAGNOSTIC INPUTREPAIR OUTPUT
ASKproposal onlyAGENTproject changes

The word Fix is carrying too much.

GitHub's October 10 Copilot update for JetBrains adds a Fix action to diagnostic intention menus. The action opens inline chat. It uses agent mode when that mode is available and ask mode otherwise.[1]

That shortcut removes clicks. It also gives one visible label two possible operating modes. Ask mode can propose a repair. Agent mode can act on the project. The release note names the fallback, but a developer still needs the current mode at the moment of use.

Fast access to a repair is useful. Hidden repair authority is not.

Refusal is a real state.

Claude Code 2.1.296 changed how auto mode reports a call that its check could not approve. The interface now shows a dim "Not run" row instead of presenting the event as a red error.[2] The same release fixes managed hooks that denied a tool call but failed to stop it, plus headless sessions that started an MCP server disabled for the folder.

These are separate changes in a different product. They support one interface lesson. A repair route needs states for proposed, allowed, refused, changed, and verified. Red error styling cannot carry all of that meaning.

The prompt does not set the tradeoffs.

Piotr Sarnacki tested two Campfire Once rewrites under a constant arrival rate. At 100 POST requests per second, the Rust version delivered about 14 percent of events with no HTTP errors. The Elixir version delivered about 60 percent while about 23 percent of POST requests timed out. He also reports worst event-delivery latency near 180 seconds for that run.[3]

A larger Rust stream capacity raised delivery to about 90 percent, but maximum delivery latency rose from 11 seconds to more than 130 seconds. Sarnacki argues that disconnecting a lagging client can be better than delivering an update minutes late. His result does not declare one language the winner. It shows that a request to "fix delivery" is incomplete without a policy for loss, latency, memory, and reconnection.

Make the action contract visible.

An inline repair should name its mode before execution. The review card should list the files or symbols in scope, the failure limit, the verification command, and the rollback route. A proposed patch is not a verified repair. A skipped action is not a failed repair.

The selector below drafts that contract. It does not inspect an IDE, run an agent, edit a file, or execute a test. Copy the card into the issue or review, fill the required fields, and keep the actual output with the change.

Interactive makeover / one Fix action replaced with an action contract

Set the torque.

This combines a mode selector, guard checklist, route diagram, and copyable review card. The physical selector makes authority visible. Native controls keep the keyboard and screen-reader path intact.

DiagnosticModeGuardVerify

Repair controls

Choose what the Fix action may do. Then select the guard fields that the review will require.

Action mode
Required guard fields
Action route / template only

Fix contract

DIAGNOSTICOBSERVED
ASKSELECTED MODE
VERIFYRUN REQUIRED
Ask mode / 0 guards selectedThe action may draft a repair. The guard structure is incomplete.
Sources read / October 11, 2026

Source log

Open the evidence boundary
  1. GitHub Changelog, "New controls and chat improvements in Copilot for JetBrains", published October 10 and read October 11, 2026. GitHub says the new diagnostic Fix action opens inline chat and uses agent mode when available, with ask mode as the fallback. The same post says JetBrains IDE 2025.1 is no longer supported.
  2. Claude Code 2.1.296 release notes, published October 9 and read October 11, 2026. The notes describe the "Not run" row, managed-hook denial fixes, and a fix for disabled folder MCP servers starting in headless sessions.
  3. Piotr Sarnacki, "I'm sorry, but you still have to think", published and read October 11, 2026. The post reports delivery rate, HTTP timeout, latency, capacity, and memory observations from constant-rate tests of two Campfire Once rewrites.

Source boundary: the GitHub and Anthropic sources describe separate product changes. Sarnacki's post reports a specific comparison with its own workload and design judgments. This article draws an interface pattern across them. It did not install the JetBrains plugin, run Claude Code 2.1.296, or reproduce the Campfire tests. The selector creates a review template, not a repair result.