What makes up an agent
Building with chat
Everything in the agents platform is built the same way: you describe what you want in chat and Major configures it for you. This applies to agents, their skills, and their schedules — there are no forms to fill out. Major drafts the configuration, wires up the right connectors and permissions, and you refine it by just asking (“use the production database”, “only run on weekdays”). The same conversation can research your connectors and apps to write a better system prompt. For an agent specifically:- Create a new agent — it starts as a private draft.
- Describe its purpose; Major drafts the system prompt and attaches connectors, apps, and skills as needed.
- Review the auto-applied tool permissions and adjust if needed.
- Publish the agent to make it available to run.
Drafts stay private to you until you publish. Published agents can be shared with others in your organization.
Running an agent
Start a new chat and pick your agent, and it runs with the prompt, connectors, skills, and permissions you configured. Agents can also run without a person in the loop:Schedules
Run an agent automatically on a cron schedule.
App triggers
Let your deployed apps start and manage agent runs.
External channels
Deploy the agent as its own Slack bot to receive and reply in channels.
Sharing and access
Agent access is role-based — User (run), Editor (edit and publish), and Admin (share) — and an agent can be shared with individuals or groups. When an agent is shared and run by someone other than its author, Major uses per-user credentials where a connector requires them, so each runner acts as themselves.Access & Permissions
Full RBAC details for agents, skills, and schedules.