Lookup Foundation, RevitLookup 2026 and DA4R 2026

In immediately reaction to the release of Revit 2026, DA4R and RevitLookup follow suite:

The Lookup Foundation

Roman @Nice3point Karpovich, aka Роман Карпович, has been heroically maintaining and enhancing RevitLookup for several years now.

He would like to expand and generalise it to implement a whole suite of tools for exploring the .NET objects.

For that purpose, we transferred ownership of the RevitLookup repository from my personal account to the new Lookup Foundation:

Lookup Foundation

GitHub redirects from the old URL to the new one, so existing links on the web will continue working:

All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL

RevitLookup has been actively developed for many years, shaped by the contributions of a dedicated open-source community. Today, we mark an important milestone: the project transitions from its original home under Jeremy Tammik’s leadership to a new organization — the Lookup Foundation — where its development will be guided by the community that relies on it.

This transition ensures RevitLookup's continued growth as a community-driven project . RevitLookup is no longer just one person’s project; it belongs to the community that builds, tests, and improves it every day.

The Lookup Foundation will ensure the project remains open, sustainable, and driven by its users. Whether you're a developer, a Revit expert, or simply someone who benefits from the tool, you have a role to play in its evolution.

Please also refer to Roman's LinkedIn announcement.

Once again, many thanks to Roman for all his hard work setting this up, and for the numerous enhancements and migration to Revit 2026 discussed below.

RevitLookup 2026

The Lookup Foundation released RevitLookup 2026.

A new major RevitLookup update with official Revit 2026 support and a lot of enhancements 🎉

This release focuses on performance, a renewed UI, expanded functionality, redesigned application architecture, clearer separation of core components and user flow improvements. Let's move to the details.

General
Dashboard Page

The Dashboard has been significantly redesigned to make it easier to understand for users unfamiliar with the Revit API.

RevitLookup 2026

Summary Page

Updated and improved Summary page components.

RevitLookup 2026

Settings Page

RevitLookup 2026

Unit Dialogue
Modules Dialogue

RevitLookup 2026

Application
LookupEngine

RevitLookup now runs on its own engine. The engine can run outside Revit, and can be reused across the entire family of Autodesk products. This is a pledge for the future for products like AutocadLookup, InventorLookup and others.

Isolating the engine also brings many new improvements:

Improvements

RevitLookup 2026

Development:

Design Automation API for Revit 2026

The APS Design Automation API for Revit 2026 has been released, DA4R 2026.

Vibe Programming Revit Macros

Michael Kilkelly shared an 8-and-a-half minute video on LinkedIn using the Revit API launchpad with vibe coding to generate from scratch and execute Revit API macros.

Michael has been working with the Revit API and macros for a long time, cf. his 2015 tutorial on getting started with Revit macros.

Direwolf Fast Revit Data Extraction

Direwolf implements a data analysis framework for Autodesk Revit. It extracts, serialises, and stores parameters from BIM models in fractions of a second.

From Floppies to a Memory Stick

I bought a 1 TB memory stick, and it got me thinking. In the beginning of my programming career, we used floppy disks. They originally held 360 KB.

  kb = 1024 byte
  floppy = 360 * kb = 368640 byte
  mb = 1024 * kb = 1048576 byte
  tb = 1024 * mb = 1073741824 byte
  tb / floppy = 2912.711111

Assuming a floppy is 3 millimetres thick, my stick would be able to store that data from a stack of floppies about 2900 · 0.003 = 8.7 metres high.