Platform Agent

The Platform Agent is the AI assistant you chat with in the Major web app. Describe what you want and it plans the work, asks for approval where needed, and builds it: apps, agents, skills, and workflows. It can also query your connectors directly to answer questions about your data.

​

Example requests

• “How many deals did we close last quarter, by region?”
• “Build an app that tracks open support tickets from our Postgres database.”
• “Create an agent that posts a summary of new Salesforce leads to #sales every morning.”
• “Write a skill that explains how our billing tables fit together.”
• “Make a workflow that runs the lead-scoring agent whenever a new Attio record is created.”
• “Add a date filter to the revenue dashboard and deploy it.”

​

What it can do

​

How it works

​

Plans

For complex, ambiguous, or long-running requests, the Platform Agent tells you its approach before it starts, or asks a question when there are meaningfully different ways to do the work. The mode selector in the chat composer has two modes:

• Auto - the Platform Agent works through the request and pauses only for approvals.
• Plan - the Platform Agent researches and writes a plan first. It appears as a Plan review card; click Accept plan to let it proceed, or Decline plan to redirect it.

​

Sandboxes

Apps, agents, skills, and workflows are each edited on a sandbox attached to the chat. Several can be attached at once, so one conversation can build an app and the agent it calls. A sandbox is held by one person at a time; if someone else is editing the same item, the Platform Agent tells you it is locked. Chats you start from an item’s editor are pinned to that item, and its sandbox starts automatically.

​

Tool cards

Each action the Platform Agent takes appears in the conversation as a tool card, so you can see what it read, queried, edited, or ran. Plans, approvals, and setup requests appear as cards you act on directly.

​

Approvals

When the Platform Agent wants to use a tool that needs your sign-off, it shows a Permission request card with the tool name, the reason, and the arguments it will send. Choose: By default, read-only connector tools and app GET requests run without asking, and tools that write ask first. Actions such as running an agent or a database migration always ask. Manage your saved rules, or set always allow, ask, or always deny for any tool ahead of time, on the Tool Permissions page. When you chat with a specific agent, that agent’s tool permissions apply instead of yours.

​

Models

Pick a tier - Smartest, Balanced, or Fastest - from the model picker when you start a chat. Each tier maps to the model your organization configured for it. The model is fixed once the chat starts, and a chat with an agent uses that agent’s model. Admins choose the model behind each tier in Settings > Models.

​

Conversation files

Files the Platform Agent writes in its working directory, such as notes, scripts, and intermediate results, persist for the conversation, so you can pick up where you left off.

​

Platform Agent and MCP

The Platform Agent uses the same tools and skills as the Major MCP server. If you prefer to work in Claude Code, Codex, ChatGPT, Cursor, or another MCP client, connect it to Major and you get the same capabilities there. The main differences:

​

Next steps