KOSHI0.6.0
Using koshi
v0.2usingfield manual

Lock mode

Pass every key to the focused program, then safely return to koshi shortcuts.

Lock mode stops koshi from interpreting normal shortcuts. Every unreserved key goes straight to the focused program.

Toggle from the keyboard

Press <C-l> to lock. Press it again to unlock.

The lock chord is explicit and does not follow the configurable leader. koshi keeps a valid unlock path when loading keybinding.kdl; an invalid locked-mode map is rejected instead of trapping input.

The default locked mode still binds:

KeysAction
<C-l>Unlock
<C-q>Quit — leave the session, which keeps running
<C-g>Toggle mouse-selection mode

Control one client from a shell

koshi lock --client <CLIENT_ID>
koshi unlock --client <CLIENT_ID>
koshi toggle-lock --client <CLIENT_ID>

Lock mode is per client. Locking one attached terminal does not lock another, and each terminal reads its own keybinding.kdl to decide what unlocks it.

Add another unlock chord

unlock-alternative adds a second escape without replacing <C-l>:

keybinding.kdl
version 1
unlock-alternative "<A-u>"

mode "locked" {
    bind "<A-u>" "core:unlock"
}

The locked block must bind the chord to core:unlock, or the whole file is rejected.

Run koshi keys conflicts after changing locked-mode bindings.

On this page