run_doctor

Check the machine the service runs on for what its agents need: tmux and its shell, the config, the harness binaries, the hooks and worktree directories, the database and its schema.

Doctorread-onlyidempotentMCP tool

Each check answers ok, warn, fail or skip with what was found and what to do about it. This is what komrad doctor asks an engine for, and it is how to find out whether an engine is fit to run agents without a shell on it.

Calling it#

curl -X POST http://127.0.0.1:8787/doctor.v1.DoctorService/RunDoctor \
  -H 'Content-Type: application/json' \
  -d '{}'

komrad rpc run-doctor

{
  "name": "run_doctor",
  "arguments": {}
}

Offered by the komrad MCP server to orchestrator agents.

Request#

Empty#

No fields.

Response#

RunDoctorResponse#

Field	Type	Description
`findings`	list of Finding	Every check the service made, in the order it made them.
`summary`	Summary	The findings counted up.

Types#

Finding#

Field	Type	Description
`name`	string	Which check this is, such as database or tmux shell.
`description`	string	What the check is for, in a sentence.
`status`	string	How it came out: ok, warn, fail or skip.
`detail`	string	What was found, such as the version read or the path checked, when there is something to say.
`code`	string	A stable code for what went wrong, such as db_unreachable, empty when nothing did.
`error`	string	What went wrong, as the check worded it, empty when nothing did.
`fix`	string	What to do about it, empty when there is nothing to do.

Summary#

Field	Type	Description
`ok`	int32	How many checks passed.
`warn`	int32	How many passed with something worth a look.
`fail`	int32	How many failed.
`skip`	int32	How many were not made because one they need did not pass.
`total`	int32	How many checks there were.
`healthy`	bool	Whether nothing failed.