Repository navigation
Merged
Conversation
system.gpus: each card's name, use, memory, temperature and power, from nvidia-smi at most once a second, for the monitors that poll /health every second or two. A machine without nvidia-smi gets no block and no second look.
c/tui.c, one C file with no libraries: a grid of cells in 24-bit colour sent as a diff inside one synchronized update, the keyboard and the mouse read raw (VT on POSIX terminals, console records on Windows). It talks to coli serve as the chat page does: the answer streamed from /v1/chat/completions with its reasoning folded, the monitor from /health and /profile (the page's Overview and Profiling, plus the GPU), the expert map from /experts. The chat page's hummingbird, its poses generated from ui/index.html (tools/make_tui_mascot.py) and its moves and timings, drawn as a sixel picture where the terminal says it can, in half blocks elsewhere. With no server it plays a demo that says so. `make colibri-tui` builds it everywhere; `coli tui` attaches to a running server or starts one for --model, its log in a file; the release archives carry it next to coli and the verify step runs it. Tests: it builds with -Werror, the demo draws and quits, and against a fake server it streams, sends the conversation and the API key, and shows /health in the monitor.
docs/tui.md and a section in each README, pictures of the TUI on Qwen3.8-Flash- Next through coli serve. The long-context table measured again on v2.1.0 the same way (bench_serve.py, 452-token prompt, 128 tokens, better of two): 65,536 tokens 208 / 52.2 tok/s, 131,072 190 / 51.9, 262,144 151 / 42.9.
…heck The release's engine loop is read by test_family_registry as engine names ([a-z0-9_]); the TUI is not an engine and builds in a step of its own, with none of the engines' ARCH or GPU flags. coli tui starts the gateway, so it checks the family's adapter like tune, chat and serve: four checks, not three.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
colibri's chat in a terminal:
coli tui, one C file with no libraries (c/tui.c), a client ofcoli serve. Tried live on Qwen3.8-Flash-Next (CUDA chain, RTX PRO 4000, 256K context) throughcoli serve.What it does
/v1/chat/completionswith its markdown drawn and the reasoning folded (ctrl+r), its tokens, tok/s and seconds.F2): the chat page's Overview and Profiling, from/healthand/profile, plus the GPU and its VRAM.ctrl+e): from/experts, the live steps where the engine publishes them, else the experts the last turn used (theHITSbitmap).ui/index.html(c/tools/make_tui_mascot.py), with the page's moves and timings (it reads, leans, flies and cheers with the model; sleeps after 90 s; click, double click, drag). A 60 x 60 sixel picture where the terminal answers that it draws sixel (Windows Terminal 1.22+, foot, WezTerm), half blocks elsewhere.--demoforces it). The demo has no tool runs and no System One card: the live client has neither yet.Around it
make colibri-tui(Linux, macOS, Windows/MSYS2 UCRT64;-lws2_32 -staticthere), its version fromversion.py.coli tuiattaches to a running server (--attach URL, else127.0.0.1:8000) or starts one for--model, the server's log in the temp directory;--api-key/COLI_API_KEY.coli, and the verify step runscolibri-tui --versionfrom the unpacked archive./healthreports the NVIDIA cards (system.gpus: use, memory, temperature, power), fromnvidia-smiat most once a second; nothing, and no second look, where there is none.docs/tui.md, a section in each of the seven READMEs, pictures indocs/media/tui/. Qwen3.8's long-context table measured again on 2.1.0 the same way (bench_serve.py, 452-token prompt, 128 tokens, better of two): 65,536 tokens 208 / 52.2 tok/s, 131,072 190 / 51.9, 262,144 151 / 42.9.Tests
tests/test_tui.py: it builds with-Werror; the demo draws and quits, giving the terminal its screen back; against a fake server it streams the answer, sends the conversation, the model and the bearer key on every request, and shows/health's GPU in the monitor.tests/test_health_gpus.py: the GPU block from a fakenvidia-smi, and none without it.test_family_registry:coli tuichecks the family's gateway adapter like tune, chat and serve (four checks).make -C c checkon Linux: 3008 tests OK. Windows: built with MSYS2 UCRT64 gcc and-Werror,--versionruns.