What's new.

The pane's AI now has every fix Claude over MCP has; Send to AI needs no key

• Every fix verb in the pane. AI fix and the AI queue's Run can now propose drags, tee slides and tilts, shift and stretch, the router's reroutes and area fixes, as well as offsets and whole-run moves, from the same scored options, hard limits and verification in Revit as Claude over MCP.
• Its own strategy needs a reason. When the pane's AI proposes something other than a listed option, it must give an override_reason, which is shown to you.
• Send to AI needs no key. It only adds clashes to the AI queue. Running the queue from the pane needs your API key (Run reads Set API key without one); Claude Desktop or Claude Code can take queued items over MCP with get_queue.

The public beta build

The first build for public beta testers: a new pane, a Cleared tab, and every fix held to the clash's own test.

New

• Cleared tab. After every import, when the pane opens and after each Keep or Reject, ClashFree re-tests your To fix clashes in Revit in the background, geometry only and no AI. Clashes that no longer clash move to Cleared, with Move back on every row.
• Preview fix sits right before Keep: it draws the fix's route in Revit as a ghost, with the clash points it clears and any new ones. Show now only zooms to the clash with a section box.
• Each clash keeps its own test. A clearance test from Navisworks (for example 25 mm) sizes every option, the AI's proposal and the verification; a hard test needs only no contact.
• A new pane. One list with To fix, Coordination, Ignored and Cleared, your trade first, one selection model, a clash page with the proposal, its verification and what it changes, a trial pill and a clear lock page.
• AI queue page: what is running, what waits, the results, and Claude's live budget.
• Open the selection over MCP: select two elements in Revit and ask Claude to open that clash.

Improved

• A fitting or accessory named in a report now resolves to its run's nearest straight, so more imported clashes find their element.
• Grouping, help and pane wording across the board.

Who gives way, Revit 2023–2027 and the beta

New

• System classes. Every run resolves to a class (supply duct, smoke extract, kitchen exhaust, sprinkler, gravity drainage, hydronic, domestic water, condensate, steam, cable tray, conduit…) with change costs scaled by size. The cheaper change gives way; gravity drainage is hands off; a line with a fall is never moved up or down.
• What a fix changes. Every option and proposal lists fittings added and removed, length, parts moved, and what an engineer must re-check: airflow, hydraulics, head loss, vents and drains, falls, firestops, bend radius.
• Revit 2023, 2024, 2025, 2026 and 2027 from one per-user installer that finds your Revit versions and Claude Desktop or Claude Code.
• Beta access: sign-up on this site, e-mail activation, a 15-day trial per e-mail, update banner, Settings with diagnostics and Delete my data.
• Claude setup from the command line: ClashFree.Mcp.exe register, unregister and doctor.

Improved

• A drag now removes a jog it makes redundant, with one corner elbow or a straight run, instead of leaving a needless dip.
• A drag that adds a low or high point away from the obstacle is scored as unfinished.
• Precedents also come from the same room on other levels.

Fix judgement

• Scored options. ClashFree lists every feasible fix, scores it and shows what hard limits removed; the AI picks by id and must give a reason to override.
• Coordination profile in three layers (base, project, you): ceiling lines, height zones, clearances, wall classes. Suggestions when you keep the second-ranked option for the same reason.
• Walls: structural walls are hard, other walls cost a new crossing with opening, damper or firestop notes. A run lying inside a wall is reported first.
• Precedents and access zones: how neighbouring runs already pass the obstacle, and the access zones of valves, dampers, terminals and equipment.
• New fixes with Claude over MCP: drag a run with its end fittings, slide a tee along its main, tilt a tee and area fixes for neighbouring clashes; risers kept inside their slab opening.
• Duplicate check: an element of your trade in another trade's model is a duplicate only when its twin exists in your model.

Grouping, the AI queue and Claude

• Clashes grouped by the run that causes them, report sets that survive a reload, trades, priority and a fix ledger.
• The AI queue prepares proposals in the background while you review; an AI review of the grouping.
• The MCP server: drive ClashFree from Claude, with a budget per clash.
• Reroutes that stretch around obstacles (with Claude over MCP).

Clash reports in

• BCF import with an element resolver for the host model and its links.
• Navisworks XML clash report import.

The core loop

• The executor: split, offset, fit and reconnect a run, inside one transaction group that Reject rolls back exactly.
• Verification against the host and linked models.
• AI proposals from a fixed list of strategies, never coordinates.
• The chat pane beside the model, with revisions in plain words.