Error · 422

command_blocked

This command is not allowed on the shell

What happened

The command is not one the shell channel will run. The refusal happens before anything reaches the server.

What to do

Read recovery.hint in the response body: it names what was refused. Use the tool built for that operation instead.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

validation_failed — The request failed validation
password_too_weak — The password does not meet the policy
job_not_allowed — That background job is not on the allow-list

Back to the full error reference

422 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/command_blocked",

:"This command is not allowed on the shell",

:422,

:"The command is not one the shell channel will run. The refusal happens before anything reaches the server.",

:"command_blocked",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Read recovery.hint in the response body: it names what was refused. Use the tool built for that operation instead."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'command_blocked') {
  // Read recovery.hint in the response body: it names what was refused. Use the tool built for that operation instead.
}

What happened

What to do

Other 422 responses