Home
Features

Features

Everything between a clash report and a resolved model.

ClashFree is one pane beside your Revit model. It reads the report, sorts it for your trade, lets AI weigh and build every fix, checks each in Revit and leaves the decision to you.

Import and grouping Work list AI fixes Verification Revise AI queue What a fix changes Coordination profile Claude Install and data

Import and grouping

Navisworks XML and BCF

Import one or several clash reports; they merge into one list. Report details shows which file is which model, what is new and what is gone on a re-import.

Matched to your elements

Each clash finds its two elements in the host model and its loaded links. A fitting or accessory resolves to its run's nearest straight, so the fix moves the run.

Duplicates merged

The same pair in two tests, or in a BCF and an XML, becomes one clash.

Ignored, with a reason

Approved or resolved in the report, within tolerance, or a copy of your own run in another trade's model (with a twin in the host). Never silently dropped.

Grouped by root cause

Clashes group by the run that causes them; the run whose change costs least per clash it clears moves first. Groups are ranked by priority with stable G-ids.

AI grouping review

Optionally, the AI reviews the rule-based groups and proposes edits (merge, split, move a clash, set aside, re-rank), checked by a validator and marked with their source in the list. Manual pins are respected.

Pick a clash in Revit

No report? Pick the two clashing elements in the model, link elements included, and work on that pair.

Recheck all

Re-test every matched clash in Revit by solids, host and links read-only, to see what is still real.

Export NWC

Export the model to an NWC under the report's name, so a Navisworks Refresh picks it up for the next clash run.

Trade-first work list

One list, sorted for your trade.

Choose your trade once. Everything is filtered to what your trade may move, and the rest is sorted where it belongs.

To fix: your trade's runs that ClashFree can move.
Coordination: nothing ClashFree may move; another trade or a person decides, with the reason.
Ignored: duplicates, approved, within tolerance, or set aside by you.
Cleared: no longer clashes, after your fix, someone else's, or because Revit finds the elements apart. A background re-test after each import and each Keep keeps it current, skipping elements that have not changed.
Move back puts any clash in another tab; it stays there until its elements change.
Search, Level and Filters (priority, strategy, AI status, change, related) with removable chips, and a flat list of clashes instead of groups.
One selection model: Shift-click ranges, Space toggles, Esc clears. A row click shows it in Revit; › opens it.

ClashFreeTrial · 12 days leftClaude

HVAC ▾Search groups, elements, levels

To fix64Coord.38Ignored211Cleared52

Struct vs MEP.xml + Arch vs MEP.xml+12 new · 7 gone

G-003Duct 600×300 SA vs Beam 500×300 · 4 clashesOffset up/down

G-009Duct Ø315 EA vs Wall (rated)Offset up/down

G-017Duct 400×250 RA vs Pipe DN150 CHWOffset sideways

G-024Duct 300×200 SA vs Tray 600✓ verified

G-031Duct Ø200 EA vs Column C4flagged

AI fixes

Every verb a modeller uses, scored before it is chosen.

For each clash ClashFree lists every feasible option with its score and the terms behind it, and the options a hard limit removed with the reason. The AI picks one by id or proposes its own with an override_reason that is logged and shown to you. The pane's AI and Claude over MCP have the same verbs, the same options and the same checks.

offset_vertical

Up or down at 45° or 90°, the smallest clearing or the preferred distance.

offset_horizontal

Left or right inside the trade's zone, often the best when a ceiling line is close.

move_whole_run

Move a short run between its fittings, priced by the length carried along.

shift_stretch

Where the run ends in a dead end: shift it out and stretch the rest.

drag

Move a straight with its end fittings, as a modeller drags it; neighbours stretch or take a transition, a redundant jog is removed.

slide_tee

Slide a tee along its main and carry its branch; the main lengthens on one side, shortens on the other.

tilt_tee

Turn the tee about its main so the branch leaves at an angle: one elbow where a shift needs two.

reroute

The router's best path per side over the run as a polyline, around obstacles and access zones.

area

Several moves of your trade's runs, verified and kept or rolled back together.

risers

Vertical runs move east, west, north or south and stay inside the slab span.

flag_for_human

When nothing verifies: the reasons and a limit code (dead_end, crossed_wall, slab, duplicate_b…).

How options are scored and chosen

Verification and safety

Checked in Revit before you see it. Undone if you say no.

Every fix runs inside one Revit transaction group: applied, verified, rolled back and drawn as a ghost route with a snapshot. Keep re-applies it as a single undo step; Reject leaves the model exactly as it was.

Clash cleared at the clash test's own clearance (hard or clearance test).
Joints connected through every new fitting.
No new clash against the host model and linked models.
Both runs judged: other clashes on them come back cleared or unchanged, with a note.
Linked and other trades' elements are never edited.
Preview fix draws the route with the clash points it clears and any new ones; Show zooms to the clash with a section box.

ClashFreeTrial · 12 days left

← G-003 › clash 1 of 4Next →

✓ Verified against host + link 'Structure.rvt'

Duct 600×300 offset 320 mm down at 45°

joints connected
clash cleared · also cleared 3
no new clash (host + links)
clearance 25 mm kept

Target cleared · also cleared 3 · new 0 · still there 0

Preview fix✓ Keep

Revise in plain words

Disagree? Say so, the way you would to a colleague.

Type what you want changed below the proposal. The AI revises, ClashFree re-builds and re-verifies, and you get a new preview. If the request breaks a hard limit, it tells you which one.

Verified. Pipe DN65 offset 300 mm down at 45°, 0 new clashes.o1 · score 923

Go over the beam instead.

There is no room above: the beam meets the slab (40 mm free, 165 mm needed). Keeping the route below.

Then use 90° fittings, the plant room is tight.

Verified. Same drop with 90° fittings: +352 mm of pipe, 0 new clashes. Ready to Keep.o2 · score 1 275

AI queue

The queue works ahead while you review.

Tick groups and Send to AI. You see how many items, which model and about how much it costs before anything runs. Proposals are prepared one at a time in the background, each verified and rolled back, so the next decision is ready when you are.

Cost first, then Run (with your API key; without one it reads Set API key); Stop any time from the bar under the header.
No key needed to queue: Claude Desktop or Claude Code can take queued items over MCP with get_queue.
Outcomes on the rows: verified, failed, flagged or stale (the model changed since).
Preview fix re-checks a queued fix with its snapshot at no AI cost before Keep.
Queue page: running, waiting, results, and Claude's live budget when Claude is working.

ClashFreeAI queue

Send 6 groups to AI? Claude Sonnet · about $0.08. Proposals are verified in Revit and rolled back; nothing is kept without you.

G-003 offset down 320 mm, 45° · also clears 3verified

G-009 offset up 250 mm, 45°verified

G-017 scoring 7 options…running

G-024waiting

G-031 column: no route clearsflagged

G-036waiting

Propose all worked 2 of 6 items; $0.027 so far.

What a fix changes

Every fix comes with its bill, and who must re-check it.

A proposal lists what it adds, removes and moves against the previous route, and one line per thing an engineer must re-check on that system. ClashFree simulates nothing: an impact says what to re-check, never that it is fine.

Duct: airflow and static pressure (pressure_loss), or "the pressure drop falls" when a fix saves fittings.
Sprinkler: the hydraulic calculation; a low point needs an auxiliary drain (NFPA 13).
Water: pump head or supply pressure on the index circuit; a new high point needs a vent, a low point a drain.
Drainage, condensate: the gradient end to end. Rated systems: the fire engineer's approval.
Conduit: ≤ 360° of bends between pull points. Tray: the cable bend radius. Terminals carried: the ceiling layout.

Duct 600×300 SA · drag 320 mm downo2 · verified

Fittings added+1 transition

Fittings removed−2 elbows (jog)

Net length−140 mm

Parts moved3 straights, 2 elbows

Terminals carried1 diffuser

New wall crossings0

Re-checkpressure_loss: the pressure drop falls (fewer fittings)ceiling layout: 1 diffuser moved with the run

Coordination profile

Your project's rules, in one file the team shares.

Height zones per trade and level, ceiling lines, clearances, wall classes, system classes and soft weights. Every entry is either a hard limit the validator enforces or a soft weight the scorer uses, and the AI names the entry that decided a fix.

Import and export the profile from the pane; one JSON per model, so the team works to one set of rules.
Suggestions from your own decisions: keep the second-ranked option for the same reason three times and ClashFree suggests a preference, with the evidence. Never applied silently.

Base

Built in, general practice. Stay in the trade's zone, fewest fittings, gravity never moves, structure is hard, system classes and costs.

Project

Per model, shared. Zones and ceiling heights per level or room, clearances, which walls may be crossed, classes the project promotes to hands off.

You

Your preferences. Soft weights only: a preference never loosens a ceiling line or touches a hands-off class.

Claude over MCP

Let Claude work through a group, on your Claude plan.

ClashFree's MCP server gives Claude Desktop or Claude Code the same view and the same checks as the pane. Claude opens a clash, looks around, reads the scored options and proposes fixes; every clash has a budget of tool calls and minutes so it cannot run away. Keep is always your click in the pane.

Set up Claude

get_statuslist_groupsget_groupopen_clashopen_selectionget_clashget_clash_contextget_runget_sectionget_free_spaceget_elements_nearget_optionsplan_routepropose_fixreject_previewget_queueget_grouping_inputpropose_grouping

In the pane: a toast when Claude opens a clash, a banner with its budget and Stop, and "let Claude work on this clash again, with fresh limits".

Install, trial and data

One installer, Revit 2023–2027

It finds the Revit versions on your PC and lists each with a checkbox. Per user, no admin rights needed.

Claude Desktop and Code

The installer can register the MCP server with Claude Desktop or Claude Code, and remove it again.

Your own AI

Your Anthropic API key, stored encrypted for your Windows user, or your own Claude plan through MCP.

Trial in the header

A pill shows the days left of your 15-day trial; a preview still open can always be rejected after it ends.

Settings you control

Clash content sharing on or off, beta activation, usage on this machine and the update check, in one place.

Light and dark

The pane follows Revit's light or dark theme (Revit 2024 and later).

What stays on your PC and what is sent

Public beta

See it on your model.

Free 15-day trial. Your invite code and the installer arrive by e-mail as soon as you confirm.

Join the free beta How it works