Agents

Automate

An agent is a role you create once and hand work to. It carries a job title, a trigger, a business function, a job description, a set of tools, an autonomy level, a schedule, a model and an effort level.

Nothing is installed for you

The Available tab is empty on a new project. MaShop ships no ready made role. Every agent on your project is one you wrote, and the Skills screen starts empty for the same reason.

Create an agent

Open My agents, then Create an agent. Six fields decide what it is.

• Job title. 120 characters at most.
• When should it be called in? The situation, not the description. 2 000 characters at most.
• Function. Its business function, picked from a list.
• What it can do. The tools it is allowed to use.
• Autonomy. How far it goes without you.
• Its job description. Required. This is the instruction it follows. 20 000 characters at most.

The button reads Create and activate. The agent is active as soon as it exists.

Two choices freeze at creation

The function and the tools never change again. The sheet warns you before you save, under the function and under the capabilities.

Read the consequence twice. An agent with no tool ticked has nothing of its own to run. It hands back a written report, and that choice cannot be reopened. To give it a tool, create another agent.

What stays open

Everything else is editable from the sheet: the title, the trigger, the job description, the business types, the skills served to it, the schedule, the autonomy, the effort, the model and the pause switch.

Tools from a connected service sit outside the sheet

The tools list on the sheet covers what MaShop runs itself. A connected MCP server works differently.

Its tools belong to the project, not to one agent. Every agent on the project can find them and run them, whatever was ticked at creation. Each call still passes the permission guard, and the actions this agent refuses are still refused.

So a service you connect for one job is reachable by every role you wrote. Set its limits on the connector sheet, not on the agent sheet. Connecting one is covered in Connect an MCP server.

Autonomy, and why the third option is often off

• It prepares, you sign. Nothing goes out without your approval.
• It acts after one grouped green light. You approve in batch, once per batch of work.
• It acts on its own. Reserved for jobs with no money, no sending and no publishing.

The third option switches off as soon as one of the agent's tools touches money, a sending or a publication. The screen replaces it with the reason. That refusal lives in the database, not in the interface, so no setting reopens it. Untick the tool at creation, or accept signing the work.

Its schedule

An agent carries one schedule, set on its sheet. Two shapes are accepted and no others: 0 H * * * for every day, 0 H * * D for one day a week. The minute is always 0. A rejected entry tells you which schedule was kept instead.

Recurring work that needs instructions of its own does not belong in this field. It belongs to an automation, and one agent can carry several.

What it rereads before every job

The Memory block on the sheet lists the rules served to this agent. It rereads your company rules plus the rules that name it, never another agent's. Choose here which ones are served. Write and delete them on the Memory screen.

An agent records anything back into memory only if you allow it on the sheet. That permission is off by default.

Editing an agent while work is queued

A queued run carries the agent version that left. If you save a change before that run starts, the run stops and does nothing at all. The failure line names both version numbers. Pausing the agent has the same effect: the queued run stops without acting.

So make your edits, then queue the work. Not the other way around.

Who can do what

Role	On agents
Viewer	Sees everything, changes nothing.
Editor	Creates an agent, edits it, pauses it, queues work, signs work that is not money.
Owner	Everything above, plus deleting an agent and signing anything touching money.

Creations and edits are limited to a handful per minute. A burst returns a message asking you to wait a minute, not an error.