Take over write lock
dsh_takeoverPreempt a conversation's write lock. DSH's write lock is a cross-process kernel semaphore that never expires while its holder lives, and no API can take it away: the only means is killing the holder, so this tool first works out who…
Instructions
Preempt a conversation's write lock. DSH's write lock is a cross-process kernel semaphore that never expires while its holder lives, and no API can take it away: the only means is killing the holder, so this tool first works out who that is. (1) If the lock is actually free, a normal resume follows and nothing is killed. (2) If the holder is an orphan this server left behind, its OS start time must match the registration before takeover. (3) Another live dsh-any-agent instance also requires force=true. (4) If the holder is unknown, or its start time is missing or differs from the registration, release the conversation in its original host and retry. Killing a holder that is running a turn interrupts that turn (logged as interrupted); the conversation itself is unharmed.
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": {
"conversation_id": "<conversation_id>"
},
"name": "dsh_takeover"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Allow takeover from another live instance or a shared child process. The lock holder’s process identity still has to be verified. | |
| conversation_id | Yes | Conversation id, from dsh_start or dsh_list. |