The app's first-run setup downloads uv's generic CPython into
~/.config/VoiceStudio/runtime, which NixOS cannot execute (stub-ld).
Do the same frozen `uv sync` at build time against upstream's nixpkgs
python, in a fixed-output derivation, and point the app at it through
OMNIVOICE_BACKEND_CMD so it no longer manages a runtime of its own.
The ctranslate2 executable-stack flag is cleared at build time with
upstream's own repair, since the store is read-only.
CPU torch only. Adds an import-probe check.
Refs: nix-overlay-2r3
VoiceStudio ships its own flake that builds the Electron app, the Rust
dictation helper and the OmniVoice GGUF runtime. Re-export it instead of
repackaging: its package needs electron_44-bin, which our pinned nixpkgs
lacks, so the input keeps its own nixpkgs rather than following ours.
Build and upstream's six packaging checks pass on x86_64-linux.
Refs: nix-overlay-kk7
Give two-session Qwen serving a bounded, opt-in decode grace for large cold prompts. Returning to normal interleaving at the deadline bounds the wait when the running reply takes longer than expected.
Bead: nix-overlay-qfi
Update the upstream flake pin and correct version reporting docs.
Evaluation reports 1.8.26. Build and test verification remains pending
on a remote builder or CI; do not build on this workstation.
Strata 0.2.14 leaves llama.cpp's MMQ prompt kernels out by default, so
STRATA_MMQ_KQ does nothing and UD-Q5_K_XL's Q6_K layer runs on Strata's
int8 kernel. On ms-s1-max, 0.2.15 with the gfx1151 prompt set and
STRATA_MMQ_KQ=1 gives first-token logits bit-identical to 0.2.13 over
15 cold prompts at the same speed (~1180 tok/s at 16K); without MMQ an
agent prompt reached KL 0.199 against 0.2.13. The engine grows from 39
to 54 MB.
Bead: nix-overlay-481
Strata 0.2.14 runs the prompt on its own kernels and vendors llama.cpp
(third_party/strata-llama), so the separate llama.cpp fetch for the
vision encoder goes. The build keeps upstream's halo flags: MMQ stays
out (STRATA_MMQ defaults to OFF), 47 of 48 UD-Q5_K_XL layers run on the
fused kernels, and the ROCm 10.1 hipBLASLt table still ships.
UD-Q5_K_XL on ms-s1-max, 16K cold prompts: 715 -> ~810 tok/s on the
defaults, ~1180 tok/s with the gfx1151 prompt set (unchanged).
Bead: nix-overlay-ydg
Upstream's gfx1151-hipblaslt-100401.txt was calibrated on TheRock 7.14.1.
therock-rocm 10.1.0rc3 reports the same hipBLASLt version, so the engine
accepted the table, but its solution ids do not exist in that build and
every prompt GEMM fell back to the heuristic. The table now comes from
tools/hip/tune_hipblaslt run on gfx1151 against therock-rocm 10.1 and is
installed in bin/tuning/, where the engine finds it by itself.
UD-Q5_K_XL, 17.5K cold prompt on ms-s1-max: 418 -> 700-725 tok/s.
Bead: nix-overlay-2yv
Maintain the gfx1151 SDK locally using the official AMD archive. Use the TheRock patchelf pin and adapt LLVM auxiliary tools for pure Nix builds.
Verify SDK installation, HIP and rocBLAS GPU operations, and rebuild its consumers. Document the internal rc3 stamp and upstream migration findings.
nix-overlay-v09 keeps the completed migration evidence and the outstanding
ms-s1-max build gate; nix-overlay-y5r is tombstoned after the duplicate
codex-oauth-proxy work was superseded.
Editors and MCP clients need the language server and the MCP server, and
upstream's release job builds all three crates in one cargo invocation.
Build -p agnix-cli -p agnix-lsp -p agnix-mcp in the same derivation so the
workspace compiles once. Closes nix-overlay-ocf.
Add the agnix agent-config linter to the overlay. Built with
rustPlatform.buildRustPackage from the v0.60.3 source tarball
(cargoBuildFlags -p agnix-cli), so no upstream pre-built release
binaries are fetched. Closes nix-overlay-wfv.
Packages the storytold/pdfcraft Cargo workspace at tag v0.18.0: the pdfcraft
desktop app and pdfcraft-cli, with the desktop entry, AppStream metadata,
icons, licences and the two CC-BY-SA OCR models the app reads from
share/pdfcraft/models. No upstream binaries are downloaded.
Two deviations from upstream's build instructions:
- The three [patch.crates-io] entries upstream's own Cargo.lock records as
[[patch.unused]] (egui_demo_lib, egui_inspection, egui_system_font_provider)
have no package in nixpkgs' partial vendor tree to resolve against, so cargo
aborts. postPatch drops them; they are unused, and cargo drops the matching
lock entries itself, so the build runs without --locked.
- nixos-unstable's rustc 1.98.1 and 1.99.0 reject every AVX-VNNI intrinsic
("intrinsic signature mismatch for llvm.x86.avx512.vpdpbusd/vpwssd"), and
rten-gemm, pic-scale and zlib-rs all use one. The package therefore builds
against a new nixpkgs-rust195 input (nixos-26.05, rustc 1.95.0), the same
pattern as nixpkgs-torch211. Follow-up: nix-overlay-g4w.
Also adds a Home Manager module (programs.pdfcraft) to
homeManagerModules.default, and documents both in the README.
Upstream 1.8.4/1.8.5 are iGPU decode and returning-session speedups with no
packaging change: setup.py still reads EXL3_ROCM_DEV_INCLUDE/EXL3_HIP_DEFINES,
the pyproject runtime deps are unchanged, and tools/{glm,mimo,qwen}/serve.py
are still the serve entry points. Only the pin and source hash move.
Verified on gfx1151: nix build .#kyojin, importing exllamav3_ext against the
pinned ROCm torch 2.11, kyojin-serve-qwen --help, and nix build
.#kyojin.tests.jit.
Add guregodevo/memdoor, a Go coding/automation agent, built from source:
- the binary embeds the React UI through web/embed.go (`//go:embed
all:dist`), and upstream gitignores web/dist, so the bundle is built
with buildNpmPackage and copied into web/dist before the Go build
- CGO stays off: the SQLite driver is modernc.org/sqlite, so FTS5 needs
no C flags and the binary is static
- upstream's whole Go suite runs (buildGoModule would trim checks to
subPackages, where cmd/cli has no tests); it needs git on PATH and
separate scratch dirs for HOME and the Go temp root, because one test
writes ~/.memdoor and ProjectRoot walks up looking for that marker
Track the package in beads as nix-overlay-yxj.
Upstream tagged v0.3 (3d10c5f) in alex/awgen. The dependency set is
unchanged, so cargoHash stays the same; only the source hash needed a
recompute for the new tag.
Verified: nix build .#awgen is green, cargo checkPhase reports 29 passed
/ 0 failed, and the resulting binary runs. Upstream Cargo.toml still
declares 0.1.0, so `awgen --version` prints 0.1.0 while the derivation
version (taken from the tag) is 0.3.
Agents were told to run bd commands that beads_rust does not have (bd prime,
bd remember, bd dolt push, bd tag, bd note, bd children), and bd's git hooks
were still active, so bd could re-export its stale dolt state over br's
JSONL on commit.
- Rewrite AGENTS.md, docs/agents/issue-tracker.md, docs/agents/triage-labels.md
and the .serena memories around br's real CLI surface
- Replace bd's generated AGENTS.md block with br's (br agents --add)
- Point the .claude session hooks at `br robot-docs guide`
- Remove bd git hooks and unset core.hooksPath; br installs no hooks
- Ignore br runtime files (local SQLite DB, recovery and merge artifacts)
- Rewrite .beads/README.md, config.yaml and metadata.json for br
Issue: nix-overlay-6pp
Export carries the new nix-overlay-51o (closed) plus a stale
in_progress state for nix-overlay-8wl that the tracked JSONL never
picked up when the issue was actually closed.
nix-overlay-nn2 now points at Na1w/marmel#13, the upstream report filed for
the reqwest unwrap_or_default() panic on a missing CA trust store. The bead
stays open until upstream propagates the error, at which point
packages/marmel/session-boot-trust-store.patch can be dropped.
Export also carries the DB changes that were never exported before (9 issues
missing from the tracked JSONL).
Bump nixpkgs and nixpkgs-latest from 2026-05/2026-08 to current
nixos-unstable (2026-09-11); both inputs now resolve to the same rev.
Re-validated every package against the new inputs.
Fallout fixed:
- freetoken: upstream pins torch>=2.11,<2.12 and triton==3.6.0, but the new
nixpkgs only ships torch 2.13 / triton 3.7. Add a nixpkgs-torch211 input
pinned at the previous revision and build freetoken against it, keeping
the CUDA 12.9 / torch 2.11 stack unchanged.
- graphify: nixpkgs' pybloomfilter3 0.7.3 ships sdist metadata that still
says 0.7.2, tripping pythonMetadataCheckPhase; skip that check only.
All 22 packages build and `nix flake check --no-build` passes.