archi-magic (zsenarchitect) errors

5 recurring problems engineers report in archi-magic (zsenarchitect), ranked by impact.

#87 by errors trackedVerificationMCAD

Recurring archi-magic (zsenarchitect) errors, by impact

  1. 1A field report from an agent working in a workshared Revit model: the agent cannot run Sync to Central, so it hands the user exact click steps and then verifies with WorksharingUtils, which found a note still borrowed after the sync. The user got about 10 Keep/Discard prompts for small note edits before turning confirmations off, and a stale plugin meant a skill was missing and the agent did not connect the dots.Verification · Agent failure · 1 report74
  2. 2An AEC agent kit keeps one shared house-rules block synced across all 24 skills by script. A rule meant for Revit skills, call get_context first and stop on revit_busy, now reaches the feedback skill and four Rhino skills. In a session with no Revit open, the agent had to decide to ignore a house rule. The author notes a stricter agent would call a pyRevit tool for no reason or report a false "Revit is not running." Proposed fix is to scope the rule per tool. Small, but it's exactly what multi-tool agent setups run into once rules are shared.MCAD · Agent failure · 1 report74
  3. 3A field report from an agent session in Revit 2026 through the pyRevit MCP, making section details on a sheet: dry run then commit worked well, but new viewports came out with the label offset at about -1.16 ft and the viewport about 1.4 ft from the requested point. The author lists these as things a skill should encode.MCAD · Agent failure · 1 report66
  4. 4Feedback from one long live Revit session lists 10 gaps: the agent could not run repo checks because auto mode blocked them, the exported viewer page carried model data, and long approval waits gave no sign they were waiting.MCAD · Agent failure · 1 report66
  5. 5Notes from a real session: show a Revit 3D view in Claude Code, move elements with a gumball, send the moves back to Revit. It worked in the end, but the viewer page was blank when opened from the temp folder, and the user said 'apply my changes' without pasting the JSON, so the pending changes had to be scraped from the page text.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.