Pigment vs Razorpay

Pigment's recent releases split into two streams. The agent stream peaked in late July when Agents moved to the homepage and began working across multiple Applications in a single conversation. Everything since has been platform craft: chart formatting and readability, View Templates, live deployment progress, metric difference detection, and Metric data kept in sync across environments. Three newer undated entries continue that pattern with per-series chart control, wider View Template options, and a centralized usage overview spanning Workspaces.

Agent capability has slowed while the surrounding model surface is being made consistent. Templates are becoming the unit of that consistency, with a Simple View Template now settable as the default for all new Views in an Application and duplicable across Applications. Environment management is maturing in parallel through deployment progress and connected Metric data that travels with a deployment and cannot be edited downstream. The new Workspace usage overview points somewhere different again, at administrators of multi-workspace estates who need cells, AI credits and storage in one view.

Expect the usage overview to grow from warnings into capacity administration, since the limits it reports against already exist. The agent stream is the one to watch for a resumption, and the open question the cross-Application work raised is governance over what an agent may reach.