Models page, marketplace subscription history, and paginated members

A smaller release focused on clarity. The page where you manage AI models has a clearer name and layout, cloud marketplace subscriptions now keep a full history of changes, and several permission issues are fixed.

Highlights

"LLM Configs" is now "Models"

MagOneAI uses two kinds of AI model: chat models, which power your agents' reasoning and replies, and transcription models, which turn speech in audio and video files into text. Until now both lived together on a page called LLM Configs.

The page is now called Models, with separate Chat and Transcription tabs. Each model card shows a badge saying what kind of model it is.

Why it matters: You can see at a glance which models you have for each job, and you're less likely to pick the wrong one.

Learn more: Model configuration

Marketplace subscription history

Customers can buy MagOneAI through a public cloud marketplace such as AWS Marketplace. These subscriptions now keep a complete, time-stamped history of every status change: the original purchase, renewals after a lapse, events sent by the marketplace, and the regular checks that keep our records in step with the marketplace.

Why it matters: When a subscription changes, you can see exactly when and why, with a complete record to point to if questions come up.

Learn more: Cloud Marketplace

Improvements

• More reliable tool connections under heavy load. Tools let agents act in other systems, such as email or a CRM. Tool calls now share one pool of network connections, with checks that keep it from running out, so connections stay reliable when many agents run at once.
• Member lists are paginated. Organization and project member lists now show 20 members per page, which makes large teams easier to browse.

Bug fixes

• Condition node default branch. A Condition node chooses which path a workflow takes next. Its default (fallback) path now works correctly, and branch pickers no longer list the same option twice.
• Settings and permissions. The Settings tab now loads for members without flickering, and members who aren't allowed to change project settings can no longer open them.
• Schedules respect permissions. People only see the schedules they're allowed to see on the home dashboard and the organization page. If schedules fail to load, you now see an error instead of a misleading "No schedules configured".