visual feedback for multi-pane claude code sessions. when claude stops and waits for input, the pane background subtly shifts — lighter in dark mode, darker in light mode. resets when you send your next prompt.
uses OSC 11 escape sequences via claude code hooks, so it works in any terminal that supports OSC 11 (ghostty, iterm2, kitty, etc).
pane-tint.sh somewhere and make it executable:
| {#- Compact tool template for Qwen3.5 on llama-server. | |
| Drop-in replacement for the stock template baked into Qwen3.5 GGUFs. | |
| Usage: llama-server --jinja --chat-template-file qwen3.5-compact-tools.jinja ... | |
| Problem: the stock template dumps each tool's full JSON schema | |
| verbatim into the prompt — "type": "function", "parameters": | |
| {"type": "object", "properties": {...}} — repeated per tool. | |
| With 8 tools that's ~1275 prompt tokens of structural noise. |
| // | |
| // THIS IS MALWARE DOWNLOADED FROM A FAKE ALCHEMY ENDPOINT | |
| // REVERSE ENGINEERED BY COOKIE | |
| // | |
| const os = require("os"); | |
| const axios = require("axios"); | |
| const { execSync, spawn } = require("child_process"); | |
| // Prevent crashes from uncaught exceptions |
| -- Port of archery colorscheme to lua (transparent). | |
| -- Slightly femmed up archery colorscheme. Dash of purple. | |
| -- Set the background to dark (this doesn't affect transparency) | |
| vim.o.background = "dark" | |
| -- Clear existing highlights | |
| vim.cmd("highlight clear") | |
| -- Set the colorscheme name |
| -----BEGIN PGP PUBLIC KEY BLOCK----- | |
| mQINBFoBjT8BEAC9p+y096kmKThHgwqFa6rnAXmtIScnsblyKD80GtJInWovuaBe | |
| tlu95EfadE6H+shPuNdA+i5rUL3s1S7GopHr2nclr51YjmNuvef9AHpFSRatLFwZ | |
| AFArRCmnIs+WBMZ6c8LD+NdLSjnCTioGyJo7cX0ACj3Qy1H+mKKN+IHOksjZ4CIV | |
| /99zP9d6folDekhIb7EhsxuhCod1MqE4Ckr1uI/3Fa6TrUo2rV7mpoSC8BTrikhU | |
| v24D1Ug6/HTrXeUUPXrWwGP8j1siCNYbWAVOWcZ3jBzZsGrzE+wS7und0Y0kj192 | |
| ZhnLSNKXDr8F0pCdLAxzq+JTpSo6qDLFoWKZGmaIBsXr4qfbiYeMt6Nvd+aGmbJI | |
| cxzdEoHS3mJO41Al2R4vp7RIXBwkhl5/+3sEXOuHbz1pm58GS9NpWCV/5XgWg34F | |
| 8pSCxTVibdn9yY46OSlK/SjogRGYr0HZlA5qsR563LzxGkR/UA7eDq5bHfW44GRM |
| /** | |
| * Slate's schema has changed vastly under 2 years. The text editor is still | |
| * a better candidate than the other OSS editors out there, so we must live | |
| * with the major changes. | |
| * | |
| * Migrate a schema from the old version 0.33 to current version 0.6x | |
| * Inspiration taken wholly from | |
| * https://github.com/react-page/react-page/blob/b6c83a8650cfe9089e0c3eaf471ab58a0f7db761/packages/plugins/content/slate/src/migrations/v004.ts | |
| */ |
graphene-django-extras is great.
Here's a homegrown solution to getting the fields that can be selected and prefetched at the qs stage in FilterSet classes.
Simply inherit from it to automatically get the qs with any possible data selected/prefetched.
This is not the way to go! Which I figured out after digging around and jotting down my findings. Maybe this'll come in handy for someone else, though. The last link in references describes "the way"
I'll risk insulting your intelligence first thing, and just mention that this is for OS X only. Open the terminal and do the below to run the script:
> . {PATH-TO-SCRIPT}/set_defaults.sh