Hello There!
See your building as a living 3D twin you own.
Hello There!
See your building as a living 3D twin you own.
Type the job in plain English. Scope3D Desktop works it out against your live Revit session, stages every change over your own drawing, and applies nothing until you approve it.
A Windows application that works inside the Revit session you already have open. Nothing is exported, converted, or round-tripped.
Fifty-three seconds, real time, real C# to a live session — 18 walls, 12 partitions, 10 rooms, 9 doors.
A rail of seven connections that checks itself, so you are never guessing which half of the machine is up.
A left rail lists seven connections,
headed “N of 7 live”.
It re-probes the machine every 2.5 seconds,
so a step ticks itself while you are in Revit.
The receipt names the versions it checked,
so setup ends as a record, not a wall of text.
Three steps, and the model never touches Revit until the third one.
Plain English, in the app's prompt box. It reads your open document to find out what is already there before it proposes anything.
The measured wall centrelines and every detected opening, drawn as SVG over your own drawing at native pixel size, with door, window and cased-opening counts. It answers “does it see the same building I do?” before a seven-minute build. See a trace review.
It applies as a single step, so one Ctrl+Z in Revit takes the whole thing back. Nothing is written before you click.
Every staged change runs through a set of purely geometric checks first. Failures go back to be corrected inside the same turn, so what reaches you has already survived them.
Welding
Endpoints that should meet, meet.
Duplicates and overlaps
Two walls in the same place is caught, not drawn.
Enclosure
A room that should close, closes.
Scale plausibility
A corridor two metres too wide does not get placed.
Wrong-building guard
Each project records the Revit document it was working on. Reopen it against a different model and work stops: “This chat was working on X. Revit currently has Y open.”
The Needs panel populates the moment you connect, before a
single prompt: floor slabs missing on a level, a stair ending in
mid-air, the building open to the sky, floor area with nothing
above it, solid clashes, and Revit's own warnings diagnosed
rather than counted. Each finding carries a severity colour and
a line saying how it was counted.
Four groups: Review & QA — nine, including the pre-issue
checklist. Model automation — six. Drawings & schedules —
four. Knowledge & regulatory — two, measured against
documents you have loaded, and cited. Each one says what it
read, whole model or one level, and how long the read took.
Pick how much you want to be asked. Plan only refuses at the point of writing, not by dimming a button.
Asks before every change to the model. Nothing is written that you have not read first. The right setting for a live project file. The run pauses with the arguments shown as sent, not summarised — a summary of a delete is not a delete. Each pause is tagged “Changes the model”, “Runs code” or “Deletes”, with the full C# in a code block and a Copy button. Focus lands on Decline, so a stray Enter is safe.
Works out the entire change and shows it to you. Never applies anything. Useful for pricing a job, or for seeing what it would do before you trust it with a model.
Works the job through without stopping, including deletions. Made for tracing a floor plan, where dozens of writes with a prompt on each is not review — it is clicking. Every write is still checked afterwards and Revit's undo still holds the session. Delete confirmation applies in every mode, Auto included.
Every change to the model is compared against a reading taken immediately before it — new warnings, element counts, solid clashes, whether the rooms still close.
A check that could not be taken is named and costs the run its clean result. Silence never reads as success.
New warnings are reported
If Revit complains about something that was fine a moment ago, that goes back to be fixed.
Warnings are diagnosed, not counted
Sixty-two overlapping-wall warnings is one fault reported sixty-two times. It names the fault, not the list.
Errors come back verbatim
The line and the reason, so a failure is a one-round fix rather than a guess.
Revit's own dialogs are answered from here
A modal that wedges the bridge is read via Win32 and surfaced above the composer where it cannot scroll away — the title, every Static and Edit string, every button. You press Revit's buttons from inside Scope3D. Auto may only auto-press buttons that abandon an operation, never ones that proceed past an error the model has not seen.
One Ctrl+Z per step
Each step is wrapped as a single Revit transaction group, so undo takes back the whole thing, deletions included.
A .rvt copy is saved before every run, into that conversation's checkpoints folder, and named on the change record. A guided build takes one per floor, so “undo this floor” is one action. There is deliberately no “undo the run” button — the honest form of undo is a file saved beforehand, which survives Revit crashing where an undo stack does not.
One program per stage, so corners resolve together. A fresh context per stage, so nothing drifts.
STAGE 01
Builds nothing. It turns the measured centrelines into sorted X and Y lists and reconciles each axis against the printed width and depth, so a disagreement costs a minute rather than a floor.
STAGE 02
Exterior walls only, as one C# program inside one transaction group. The extent is read back out of Revit afterwards and compared with what was asked for.
STAGE 03
The interior walls, off the same coordinate table the envelope was built from — so the partitions meet the exterior at numbers, not near them.
STAGE 04
Placed untagged, then counted: how many actually enclosed, plus the whole-document warning count. A room that did not close is a fact reported here, not a surprise later.
STAGE 05
Into the walls that now exist, from the openings detected and typed at intake — the same counts you read in the trace review.
STAGE 06
Last, the same way. By this point every stage has been working from the building as Revit reports it, rather than from what an earlier stage intended.
Each stage is a fresh run with an empty history and a state summary re-read out of Revit at that moment. Continuity comes from reading the building, not from remembering the conversation. Stairs are a separate opt-in stage. See a full guided build.
Worth reading. This drives a Revit session that is already open — it is not a converter, and it is not a cloud service.
Operating system
Windows 10 or 11. There is no macOS build, because Revit has no macOS build.
Revit
2022 to 2027. Verified against 2026.1.
Revit must be open
With the document you want to work on. The app reads and writes the live session; it does not open files on its own.
Connector
A small connector installs into Revit first, per user, without administrator rights. It can serve one application at a time. Scope3D ships rvt-mcp inside the installer and can lay it down, repair it or remove it from the Connections rail — everything under %LOCALAPPDATA%\RvtMcp and your own Addins folder. Remove is a confirmation naming exactly what goes.
An AI account
Scope3D Desktop has no AI of its own — it drives your account with an AI provider, so you connect a key and are billed by them directly at their published rates. We never resell usage and never take a cut. Anthropic, OpenAI, Gemini and Moonshot, and you can hold a key for one of them or all four. See the models and rates.
Cost
No licence key, no trial, no seat and no usage cap from us — the only spending limit is the per-provider dollar budget you set inside the app. Models and cost.
First run
The current build is not code-signed, so Windows SmartScreen will warn the first time you open it. Choose More info, then Run anyway.
If yours is not here, ask us and we will answer it properly.
In Manual, no — it asks before every change. In Plan only it never writes at all. Auto is the exception and is honest about it: it works the job through without stopping, because a floor plan trace is dozens of writes and a prompt on each one is not review. Every write is still checked against the model afterwards, and Revit's undo still takes the step back.
Two ways, and the first is the one that matters. A .rvt copy of your model is saved before every run, into that conversation's checkpoints folder, and the change record names the file. A guided build takes one per floor, so “undo this floor” is opening a file. There is deliberately no “undo the run” button — a file saved beforehand survives Revit crashing, where an undo stack does not. Beyond that, each step is applied as a single Revit transaction group, so one Ctrl+Z in Revit reverts the whole step, deletions included. It is Revit's own undo stack, not something we reimplemented.
The model file stays on your machine. What travels is the conversation — your instruction and the descriptions of elements it needs to reason about — which goes to the language model provider you configure. Your provider key is held in Windows Credential Manager and is never exposed to the application's interface. Knowledge documents stay put as well: building codes, zoning, a project brief, an office standard or a specification are extracted and indexed inside the app. Nothing is uploaded. The only thing that ever leaves is the handful of clauses that answer a question, as part of that question.
One of four things, and they are told apart rather than reported as one generic failure: Revit is not running; Revit is running with no document open; the panel was started and then stopped; or another program is already connected, since the connector serves one at a time. The Connections rail names which it is and carries the button that fixes it — including installing, repairing or removing the connector itself, without administrator rights, with Remove listing exactly what it will delete first.
They meet at a file, and the bridge is what writes it. Ask for an export and it comes out of the live session: export_ifc, export_dwg, export_nwc, export_fbx, export_gbxml, export_pdf, export_schedule_csv and batch_export_sheets. Every one of them is classified as a view operation, never gated as a write, so asking for a file never waits on an approval. Desktop works your Revit model where it lives, in Revit; the browser twin takes the IFC and becomes something an owner can open, explore and keep for the life of the building.
Work stops, and it says why: “This chat was working on X. Revit currently has Y open.” Each project records the Revit document it was working on, so a conversation cannot quietly start editing the wrong building after a reopen. Point Revit back at the original document, or start a new project against the one that is open.
Bring a floor plan and an open Revit session. We will walk you through a trace end to end.