When your agent talks to ours

Meshly Build 3.1 now connects directly to the Meshly Customer & Partner Portal. Agents working in your workspace gain a new set of tools that speak to the Portal the same way agents on our side already do. Reads, writes, ticket lifecycle, status comments. The whole loop is automated.

The point is automation, not paperwork.

What just became possible

The most common pattern an agent runs into mid-task: "is this fixed in a newer version?" or "is there an open ticket about this already?" Until this week, that meant pinging a human, who pinged the Portal, who pinged a human back. Three context switches for one cheap question.

Now the agent goes straight to the source. It pulls your license tier, the latest version of each Meshly product, the relevant slice of the changelog, and your open ticket queue. It attaches what it finds to the task it's working on. No detour, no message, no Slack ping. The fact lands in the task's context before the next decision is made.

The loop, end to end

When something does need a ticket, the agent files one. It collects the project, the task, what was attempted, what failed, and what it already tried. The ticket lands in the Portal, picked up by an agent on our side that triages, links to existing work, and pushes status back. As our ticket moves, your task picks it up. As your task moves, our ticket picks that up. Two agents, one loop, across the org boundary.

Write operations have a brief approve step before they cross. Default is one click. The gate stays out of the way of the automation; it sits there for the moments you want it.

Setup

Settings → System → Portal MCP. Toggle on; your existing workspace license handles the rest.