By Brian Barnett, founder of Hibana Solutions · Checked against Pigment’s documentation in October 2026
Can Pigment’s Modeler Agent audit your workspace?
Yes, and it’s worth doing, more so now that it can see across applications. But its remaining limits are exactly the places where models tend to go wrong, so treat its audit as a first pass, not a verdict.
What the agent audit covers
Pigment’s community has published a step-by-step guide to auditing a workspace with the Modeler Agent. It organizes the review into four areas: modeling and architecture, performance and calculation health, security and access rights, and governance and best practices. For each, you prompt the agent to look for known problems, such as unused Blocks, heavy formulas or inconsistent naming, and to explain what it finds.
That is genuinely useful. The agent reads your Blocks and formulas faster than any person can, and it is good at spotting things that are simply inconsistent.
What has changed since the guide
When the guide was written in May 2026, the agent could audit only one application per session. That is no longer true. Pigment’s agents now work at the Workspace level, and the Modeler Agent can see, and make architectural changes, across applications. That closes the biggest gap, because many problems sit between applications, in the data that flows from one to another.
It can also now read context from outside Pigment through Agent Connectors, starting with Notion, with Google Drive and Slack announced as coming next.
Where its limits are
Pigment’s own documentation and the guide are candid about what remains. Five limits matter most:
- Performance is estimated, not experienced. The agent can rank Blocks by calculation time and flag formulas that look expensive. It can’t sit through a Board that takes twenty seconds to load at month-end with the whole team in it.
- No view of your source systems. Connectors bring in documents, not your ERP. The agent can’t check whether the NetSuite or warehouse data arriving each night is the data the model expects.
- It sees only what you can see. The agent works with your permissions. If your access is limited to some regions or applications, so is its audit.
- Its changes are real. Edits are permanent and logged in Application History, and Pigment recommends a backup before significant changes. Applications deployed through Test & Deploy accept questions only, so fixes happen in your development copy.
- No judgment on the business logic. It can tell you a formula is consistent. It can’t tell you the allocation method is wrong for your business, or that the source data is right.
What a human review adds
A senior reviewer starts where the agent stops: watching the model run under real load, tracing the data back to the systems it comes from, asking finance what the numbers are supposed to mean, and deciding what to fix first. The most valuable output of any audit is not the list of issues but their order.
Our suggestion: run the agent audit yourself, then bring its findings to a person who can tell you which ones matter. That is what our free architecture review is for.