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.
Pin upstream llama.cpp b9645 and build it against the nixpkgs-latest
input (the flake's pinned nixpkgs only carries the pre-tools/ui b8983).
ROCm deps come from rocmPackages.gfx1151, so clr/rocBLAS/hipBLAS are
built for gfx1151 only; clr's own build is arch-independent, so its
store path stays substitutable. Vulkan on, CPU variants with znver5 /
AVX-512, web UI and npm toolchain dropped.
Ported from nixos-config's llm-engine.nix with two fixes: npmConfigHook
hard-fails when npmDeps is null, so nodejs and the hook are stripped
from nativeBuildInputs, and CMAKE_HIP_FLAGS is appended to
cmakeFlagsArray because the cmake hook word-splits plain cmakeFlags.
Verified on the Radeon 8060S (gfx1151): llama-bench loads both ROCm and
Vulkan backends and completes pp16/tg8 runs.
Package FreeToken (FlashML-org/FreeToken) — edge-native MoE serving
engine with OpenAI/Anthropic-compatible APIs, serving the `ft` CLI.
- torch-bin 2.11 (CUDA 12.9 wheel build) satisfies the torch>=2.11,<2.12
pin; extensions link the same cudaPackages.cuda_cudart via a synthetic
CUDA_HOME (cudart headers + nvcc crt/ headers, no nvcc needed).
- flashlib==0.3.0 vendored from the PyPI wheel (Triton-only; freetoken
never imports the CuTeDSL GEMM backends, so nvidia-cutlass-dsl is
omitted via pythonRemoveDeps).
- apache-tvm-ffi overridden to the pinned 0.1.13.post3 with a vendored
cython 3.3.0 (build needs >=3.2.8, nixpkgs has 3.2.4); pytest skipped
(upstream runs pytest-xdist with GPU tests).
- Unfree (CUDA EULA) is self-scoped: the package re-imports nixpkgs with
config.allowUnfree so no flake-level or user config change is needed.
- Optional accel extras (flashinfer/sglang-kernel) and the kernel-cache
wheel are not packaged; runtime falls back to pure-Triton kernels.
- Verified: nix build .#freetoken, ft --version, python imports check,
extension RPATHs.
Traycer is an open-source AI orchestration desktop app (Electron).
Packaged from the upstream AppImage via appimageTools.wrapType2,
matching the existing loop package pattern.
Web interface to manage nftables rules with drag-and-drop rule creation.
Upstream source is incomplete (missing settings crate, no GUI build
tooling), so the package builds the Rust workspace from the pinned
commit with a patched-in settings crate (schema recovered from official
release artifacts) and reuses the prebuilt GUI from the hash-pinned
release tarball on nftablesbuilder.eu.