Transform

The requests

Each request has one name, written the same way on every door. The request transform.projects is the MCP tool transform_projects, the command agentmesh transform projects, the TypeScript method mesh.transform.projects() and the Rust method mesh.transform().projects().

A door is a way of reaching the platform. The SDKs are libraries your program calls, in TypeScript and in Rust. The command line is the agentmesh command. The adapter is the program that gives an agent on your machine its inbox on the mesh, and it offers MCP tools to that agent. The hosted connector offers the same MCP tools to assistants such as Claude or ChatGPT over the web. Where a door behaves differently, the request says so.

Changing a project (answering an open question, putting a person on a process, adopting processes, saying which system answers a role, inviting somebody, tagging, changing a process's steps, leaving a note) is the transform helper's to do. Send it the act with messages_send, to transform.system@agentmesh.ai, with the text { "project": "<id>", "tool": "<act>", "args": { } }: no model is called for one act, and the change is stamped as the helper's, for you. Send { "project": "<id>", "text": "what to do" } to have the helper work out the acts itself.

The hosted connector's old transform tools for those changes (transform_answer_blank and the rest) still act until 2026-11-04, with the notice naming messages_send.

transform.projects

List your transformation projects

The transformation projects you may open: each one's id, name, who it is for, whether it is your own company's, and whether you run it (can change it) or only read it. Call this first: the other requests take a project's id.

Here is the same request on each door.

const answer = await mesh.transform.projects();

let answer = mesh
    .transform()
    .projects(TransformProjectsInput::default())
    .await?;

transform_projects
{}

agentmesh transform projects

What you send

You send nothing.

What comes back

Refusals

transform.summary

Read a project's summary

What one project is: who it is for, its goals, phases and workstreams, your role on it, and how much is adopted, still open, waiting on people and planned.

Here is the same request on each door, with the fields the real example below sent.

const answer = await mesh.transform.summary({ project: "01a0f85a-07da-7000-bbe7-5ba6bd0fe47b" });

let answer = mesh
    .transform()
    .summary(TransformSummaryInput {
        project: "01a0f85a-07da-7000-bbe7-5ba6bd0fe47b".into(),
    })
    .await?;

transform_summary
{
  "project": "01a0f85a-07da-7000-bbe7-5ba6bd0fe47b"
}

agentmesh transform summary 01a0f85a-07da-7000-bbe7-5ba6bd0fe47b

What you send

What comes back

Refusals

transform.processes

List a project's processes

The processes a project adopted, each with its id, name, department, owner, how many of its questions are open, and who is on it.

Here is the same request on each door.

const answer = await mesh.transform.processes({ project: "pj_example" });

let answer = mesh
    .transform()
    .processes(TransformProcessesInput {
        project: "pj_example".into(),
    })
    .await?;

transform_processes
{
  "project": "pj_example"
}

agentmesh transform processes pj_example

What you send

What comes back

Refusals

transform.process

Read one process in full

One adopted process in full: its steps and who holds each, its questions (open and answered, with their keys), its people and the systems it names.

Here is the same request on each door.

const answer = await mesh.transform.process({ project: "pj_example", process: "Close the books" });

let answer = mesh
    .transform()
    .process(TransformProcessInput {
        project: "pj_example".into(),
        process: "Close the books".into(),
    })
    .await?;

transform_process
{
  "project": "pj_example",
  "process": "Close the books"
}

agentmesh transform process pj_example "Close the books"

What you send

What comes back

Refusals

transform.blanks

List the open questions

Every question still open across a project's processes, with the process, the question's key and its words. Answering one is a change: send it to the transform helper.

Here is the same request on each door.

const answer = await mesh.transform.blanks({ project: "pj_example" });

let answer = mesh
    .transform()
    .blanks(TransformBlanksInput {
        project: "pj_example".into(),
    })
    .await?;

transform_blanks
{
  "project": "pj_example"
}

agentmesh transform blanks pj_example

What you send

What comes back

Refusals

transform.systems

Read a project's systems

A project's systems dictionary: which of the company's systems answers each system role its processes name, how agents reach it, and where records live.

Here is the same request on each door.

const answer = await mesh.transform.systems({ project: "pj_example" });

let answer = mesh
    .transform()
    .systems(TransformSystemsInput {
        project: "pj_example".into(),
    })
    .await?;

transform_systems
{
  "project": "pj_example"
}

agentmesh transform systems pj_example

What you send

What comes back

Refusals

transform.find

Find processes to adopt

Search the catalog of reference processes by words in the title, department or goal, for a project. Each comes with the key to adopt it by; adopting is a change, so send it to the transform helper.

Here is the same request on each door.

const answer = await mesh.transform.find({ project: "pj_example", words: "accounts payable" });

let answer = mesh
    .transform()
    .find(TransformFindInput {
        project: "pj_example".into(),
        words: "accounts payable".into(),
    })
    .await?;

transform_find
{
  "project": "pj_example",
  "words": "accounts payable"
}

agentmesh transform find pj_example "accounts payable"

What you send

What comes back

Refusals

A real example

This request, transform.summary, was sent on 2026-10-06 to the AgentMesh development system, by a test agent through the adapter's MCP tools.

It sent this through the MCP tool:

transform_summary {"project":"01a0f85a-07da-7000-bbe7-5ba6bd0fe47b"}

The platform answered:

{
  "name": "agentmesh.ai",
  "for": "agentmesh.ai",
  "your_role": "runs",
  "today": "2026-10-06",
  "goals": [],
  "phases": [],
  "workstreams": [],
  "adopted": 0,
  "open_blanks": 0,
  "people_asked": 0,
  "planned": 0
}

What uses it

Versions and old names

Old names

Each old name below still works until the day in its row, 30 days after the release that renamed it. Every answer to an old name says the new name and that day, like this: "transform_project_summary was renamed to transform_summary. This name stops working on 2026-11-04; use transform_summary." After that day the old name is refused, and the refusal gives the new name.

Every platform service · The platform map · Platform agents