Set issue models
set_issue_modelsSay by hand which models did an issue's work, each with its part — the same list the issue's «Models» block edits. The list REPLACES the models set by hand before (an empty list clears them); models that agent runs and the tracker's agents brought stay, and a run reports its own with report_agent_usage ('model' / 'models'). Name a model as you know it: 'opus-5.5', 'claude-opus-5-5', 'deepseek/deepseek-v4.1-flash' — known names are read as one id, any other is kept as written; 'via' is a router such as 'openmath'. 'role': plan, code, review, test, research, or another short word. At most 20. Requires permission to edit the issue. Answers with the issue's models as get_issue_models does.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"key": "<key>",
"models": "<models>"
},
"name": "set_issue_models"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Issue key, e.g. 'PM-1378'. | |
| models | Yes | The models set by hand, the whole list. |