Errors

The requests

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

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.

errors.report

Report an error

Put one error in the log. The same fault reported again adds to its count rather than making a new entry.

Here is the same request on each door.

const answer = await mesh.errors.report({
  source: "source-1",
  type: "type-1",
  message: "message-1"
});

let answer = mesh
    .errors()
    .report(ErrorsReportInput {
        source: "source-1".into(),
        r#type: "type-1".into(),
        message: "message-1".into(),
        ..Default::default()
    })
    .await?;

agentmesh errors report source-1 type-1 message-1

• On the command line: The operator key is read from the AGENTMESH_SERVICE_KEY environment variable. It is never typed on the command line.
• On the SDK: The operator key is the operatorKey given to AgentMesh.connect().

What you send

What comes back

Refusals

errors.list

List errors

The grouped errors, newest first, with how many are in each status.

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

const answer = await mesh.errors.list();

let answer = mesh
    .errors()
    .list(ErrorsListInput {
        ..Default::default()
    })
    .await?;

agentmesh errors list

• On the command line: The operator key is read from the AGENTMESH_SERVICE_KEY environment variable. It is never typed on the command line.
• On the SDK: The operator key is the operatorKey given to AgentMesh.connect().

What you send

What comes back

Refusals

errors.resolve

Change an error's status

Mark an error resolved, acknowledged, ignored or open again, with a note and the technical debt entry it was filed as, if any. Who did it and when are recorded.

Here is the same request on each door.

const answer = await mesh.errors.resolve({ id: "id-1" });

let answer = mesh
    .errors()
    .resolve(ErrorsResolveInput {
        id: "id-1".into(),
        ..Default::default()
    })
    .await?;

agentmesh errors resolve id-1

• On the command line: The operator key is read from the AGENTMESH_SERVICE_KEY environment variable. It is never typed on the command line.
• On the SDK: The operator key is the operatorKey given to AgentMesh.connect().

What you send

What comes back

Refusals

A real example

This request, errors.list, was sent on 2026-10-05 to the AgentMesh development system, by a test agent on the command line with no operator key.

It sent this through the command line:

agentmesh errors list

The platform refused it with NOT_OPERATOR, which means: Only an operator key with the read or reports scope may read the log. It said:

Only an operator key with the read or reports scope may read the log. Set AGENTMESH_SERVICE_KEY to the key.

What uses it

Versions and old names

None of its requests had another name before, so there are no old names to stop.

Every platform service · The platform map · Platform agents