| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| caprock_0.39.2_darwin_amd64.tar.gz | 2026-08-31 | 8.7 MB | |
| caprock_0.39.2_darwin_arm64.tar.gz | 2026-08-31 | 8.2 MB | |
| checksums.txt | 2026-08-31 | 600 Bytes | |
| caprock_0.39.2_linux_amd64.tar.gz | 2026-08-31 | 8.6 MB | |
| caprock_0.39.2_linux_arm64.tar.gz | 2026-08-31 | 8.0 MB | |
| caprock_0.39.2_windows_amd64.zip | 2026-08-31 | 8.8 MB | |
| caprock_0.39.2_windows_arm64.zip | 2026-08-31 | 8.0 MB | |
| README.md | 2026-08-31 | 723 Bytes | |
| v0.39.2 source code.tar.gz | 2026-08-31 | 5.6 MB | |
| v0.39.2 source code.zip | 2026-08-31 | 5.9 MB | |
| Totals: 10 Items | 61.7 MB | 0 | |
Fixed
- Shift+Enter really does insert a newline now. 0.39.1 sent the right
bytes and still submitted, because the bytes were only half of it: returning
falsefrom the key handler stops xterm interpreting the key, but the browser still delivers it to xterm's hidden textarea, which emits its own carriage return. The socket carriedESC CRand then a bareCRimmediately after —[27,13]followed by[13]— and Claude Code submitted on the second one.
The keys now call preventDefault, so the textarea never sees them. Four
attempts at this bug and the first three were all arguments about which
sequence to send; nothing was watching what else went down the wire
afterwards.