765TFLOWCommunity
Request access

Context Engineering Flow · for Revit

Your AI engineer — working directly on the open Revit model

765T Flow is the bridge between an AI assistant and your Revit. We built an engineer's way of working into it, along with more than 300 compiled Revit commands that run fast — so the assistant does real work with you, and your team moves faster.

Watch FLOW workHow CEF works
Runs on your machineYour own AI subscription

01 / Story

AI is capable. It still does not know your project.

AI helped me code, learn and work faster. But on a real BIM job the limit appeared immediately: it could not see the open model, did not know the project standard, and could still sound certain without enough evidence.

Another chatbot inside Revit did not solve the root problem. I needed a system outside the interface that could connect several Revit sessions, route the right job to the right model, and bring every result back to one place.

FLOW started there: fewer errors, fewer loops, and more time for work that needs experience. AI does not replace BIM professionals; it expands what they can handle.

02 / What MCP CEF is

CEF is the working layer between AI and Revit.

An AI agent becomes useful in Revit only when it has three things: the right context, the right tools, and clear rules. CEF — Context Engineering Flow — organises those layers so the agent does not have to guess.

  1. 01

    See the model the task needs

    Flow reads the open model within the task scope: elements, parameters, views, sheets, systems, warnings and links. The agent gets evidence, not a screenshot to interpret.

  2. 02

    Use real Revit tools

    More than 300 tools are compiled against the Revit API, with schemas and permission levels. The agent combines them; Flow controls how they run.

  3. 03

    Follow project standards

    Checklists, BEPs, PDFs, notes and office rules become task context. The result follows how your BIM team works, not a generic answer.

One agent, several Revit sessions.

Each Revit session has its own ID. The agent routes the right job to the right model and can follow several sessions from one place.

  1. 01

    The right model

    The job goes to the session you selected, not the window that happened to be active.

  2. 02

    No single queue

    A long audit does not block a short task on another model.

  3. 03

    You keep the interface

    Flow works through open sessions without turning Revit into a full-screen chatbot.

03 / MCP in action

From a PDF catalogue to a Revit family — in one real session.

Give the catalogue to the agent. Flow reads the specification, builds the family in Revit, and returns the result for inspection. The recording below shows the whole session.

Screen recording
English narration and a command-line client; the everyday interface can be Claude Desktop.

Every change follows a verifiable loop.

Flow does not click through Revit blindly. Every job is read, previewed, authorised, executed and read back through the same sequence.

MCP sessionstdio · local
  1. 01revit_inspect_modelread
    Read the current state

    Collect only the elements, parameters, views and warnings the job needs.

  2. 02revit_discover_toolsread
    Choose an allowed tool

    Return tools that are valid for this model and task scope.

  3. 03revit_call_tool · previewread
    Preview the change

    Resolve what will change without writing to the model.

  4. 04revit_call_tool · request_approvalgated
    Check execution authority

    Run only in the authorised document, tool set and task scope.

  5. 05revit_call_tool · executegated
    Execute once

    Call a defined Revit API transaction, not a generated console script.

  6. 06revit_inspect_modelread
    Read the result back

    Return structured evidence and element IDs you can inspect in Revit.

The installer registers the connection with supported AI clients on your machine. No JSON to paste and no paths to hunt down.

How teams actually use it

Read notes from real BIM workflows and the product gaps we are still closing.

More than 300 Revit tools are ready for the agent to use.

Each tool is compiled against the Revit API and carries a schema, permission level and readback. The agent chooses the combination; Flow keeps execution inside defined boundaries.

What Flow can doReady to run

Capability families

  • Parameters & shared parameters
  • MEP systems, pipe & duct
  • Sheets, views & templates
  • Family authoring & family QA
  • Rebar & reinforcement
  • Audit, warnings & model health
  • Schedules & data exchange
  • Evidence & structured read-back

The count comes from the current build, not the roadmap.

04 / Value

Reduce the loops that consume the week.

Flow focuses on QA/QC, model data and repetitive work that creates errors before an issue deadline.

  1. 01

    Check before issue

    Run the checklist and return what was checked, fixed and left for a human decision.

  2. 02

    Pipe slope and flow direction

    Measure each run against project requirements and identify the exact segments to change.

  3. 03

    Missing or incorrect parameters

    Compare against schedules and an approved mapping, then update in batches.

  4. 04

    Warnings and model health

    Group warnings by severity and return element IDs for direct inspection.

  5. 05

    Views, sheets & templates

    Check templates, naming rules and sheet sets before issue.

  6. 06

    Build a family from a spec

    Turn the data in a PDF into a parametric family that can be checked in Revit.

Flow is shaped by real BIM jobs.

New capabilities are prioritised from BIM tasks with real data, project standards and a clear acceptance test.

Email us
  1. 01
    Report an unfinished job

    Show us where Flow stopped and what the correct result should look like.

  2. 02
    Request a capability

    Send the Revit task that consumes the most time in your week.

  3. 03
    Shape a workflow

    Use a real project to define the context, tools and readback criteria.

Early Access means features can change. Release notes identify what has been tested.

05 / Your machine

The Revit model stays on your machine.

Flow runs locally and connects to the AI client you choose. The RVT file is not uploaded to 765T; only the context a job needs is sent to that AI.

Where your data goesLocal by default
  1. 01
    Your AI clientreceives context and plans the task
  2. 02
    765T Flowcontrols tools and execution
  3. 03
    Revitthe model open on your machine
  1. 01
    Choose your AI client

    Keep your subscription and model choice. No new API key and no resold tokens.

  2. 02
    Not used for training

    765T does not use your model, standards or job history as training data.

  3. 03
    Preview and readback

    Flow previews the change, runs inside the allowed scope and returns the result with element IDs.

Data sent to the AI

Only the context the job needs. Not the RVT file and not your full standards library.

Install once. Work from the AI client you know.

The installer sets up the Revit add-in, local service and MCP connection. You assign work from your AI client instead of learning another interface.

See the jobs it runs
  1. 01
    Claude Desktop extension

    The installer registers the connection; open Claude Desktop and start assigning work.

  2. 02
    Command-line agents

    Use the same local MCP from Codex or another compatible command-line agent.

  3. 03
    No admin rights needed

    Installs in your Windows profile and supports silent deployment in an office environment.

06 / Get a build

Get the Early Access build.

Email us for the build that matches your Revit version. Flow is free during Early Access.

Requirements
  • Windows 10 or 11
  • Revit 2024 and later
  • Claude Desktop with an active subscription, or an MCP-capable command-line agent
Price
Free765T does not charge during Early Access; you still pay for your own AI subscription.

Frequently asked questions.

01Do I have to approve every single change?

No. Authority binds to the task scope. Flow previews, runs and reports changes with element IDs; you do not approve each element separately.

02Does the RVT file leave my machine?

No. Flow reads and edits locally. Only the context a job needs is sent to the AI client you chose.

03Is my work used to train AI?

Not through 765T. We do not use your model, standards or job history to train AI.

04How is Flow different from Revit chat?

Chat mainly answers. Flow gives the agent model context, compiled Revit tools and readback so it can act and verify the result.

05Which AI clients work with it?

Claude Desktop and command-line agents that support MCP. We name a new client only after it passes the compatibility test.

06Why is it not a panel inside Revit?

A panel is tied to one window. Running alongside Revit lets Flow route work to several open sessions from one place.