Tapir / Community

Ask. Report. Test.

Architects, developers and the maintainers in one place. Bugs and ideas become fixes that someone with your Archicad version tests before they ship.

Where to find us

Discord

Ask anything

Architects, developers and the maintainers, in one server. Show what you made and talk with the people who build Tapir.

Join Discord
YouTube

Learn the API

A video series from the first command to full workflows.

Watch the tutorials
AI assistants

Talk to your model

MCP servers let Claude and other assistants read and change a project through Tapir.

Tapir and AI

How the bots work.

Most fixes are written by bots and checked by people. The maintainers set the rules and can stop any change; you decide whether a fix works in your Archicad.

01Post itDescribe the bug or idea on Discord or GitHub. A GitHub account is not needed on Discord.
02An issueEvery half hour, Discord posts that read like a bug report or a feature request become GitHub issues, and the bot replies with the link.
03A draft fixThe issue bot answers, asks for what it is missing, or writes the fix and opens a pull request. It is built for every Archicad version and reviewed.
04You testA comment on the pull request links the built add-on and asks the person who reported it to try it.
05ReleasedGreen and reviewed, it is merged three days later unless a maintainer stops it, and ships in Monday's release.
Report

How to report a bug

Post it on Discord or open an issue on GitHub; both reach the same place. A report that can be fixed in one go says:

  • your Archicad version and build, and its language (for example 29.0.0 (3100) INT);
  • your Tapir version (the About Tapir dialog shows it);
  • what you did: the script or Grasshopper definition, or the command and the JSON you sent;
  • what you expected and what happened instead, with the error message;
  • whether the project is a Teamwork project, and which libraries are loaded, when it matters.

Public Issues and Discord channels are public. Leave out client names, project names and file paths you don't want to share.

Test

How to test a fix

A fix is only known to work once someone has run it in Archicad. The bots can build Tapir but cannot run Archicad, so your test is what matters most.

  1. Open the pull request linked from your issue. A comment on it lists the downloads, one per Archicad version and platform. Downloading needs a GitHub login.
  2. Unzip the download for your Archicad version. On macOS it holds another zip with the .bundle.
  3. In Archicad, open Options > Add-On Manager > Edit List of Available Add-Ons, remove or disable the installed Tapir, then Add the .apx (Windows) or .bundle (macOS) and click OK.
  4. Do what went wrong before, in a copy of your project.
  5. Say on the pull request whether it works and fixes your case. Afterwards, put your installed Tapir back the same way.

Testing often? The community test runner tests open pull requests on your own Archicad while it is closed, leaves your Tapir in place and posts the result. It runs on Windows and needs Python and a GitHub account.

Help build it

Get involved

We're building a motivated, diverse community around Archicad automation.

Say hello on Discord, and tell us what you automate in Archicad.