unslothai/unsloth-zoo #2290: Precomputed Transformers v5 check inGptOssTopKRouterforward loop to eliminate runtime version parsing overhead in MoE routing.vllm-project/vllm #56635: Isolated reasoning boundary tokens (<think>,</think>) in streamingParserEngine, eliminating tool-call argument contamination on reasoning models.basetenlabs/truss #2682: Upstream runtime model serialization and container packaging fix.openhwfoundation/cva6 #3518: Instruction pipeline verification and testbench retirement sequence fixes.
| project | focus & problem | verified evals & metrics | live links |
|---|---|---|---|
support-triage-mcp |
forward-deployed style triage agent for messy customer support data (emails, webhooks) with MCP server tools (CRM lookup, Postgres query, Stripe refund gate) | 99.4% schema adherence · 91.4% intent routing precision · sub-2s latency · Langfuse audit trail | pipeline server · eval harness · test corpus |
tool-call-bench |
benchmark evaluating tool-calling & structured-output reliability across providers (schema violations, malformed arguments, boundary leaks, retries) | 0.8% failure on sonnet-3.5 vs 7.4% on gpt-4o-mini · measured token retry overhead · benchmark harness via LiteLLM | results table · repro harness · blog post |
decodeforge |
high-throughput grammar compiler & constrained decoding runtime for production LLM serving pipelines | O(1) sub-token bitmask filtering · sub-microsecond logit pruning · zero GPU decode stalls | architecture · spec · quickstart |
factforge |
automated fact extraction, source PDF grounding & cross-document contradiction detection for financial filings | 100.0% verbatim excerpt grounding · 94.2% token reduction vs pairwise prompting · O(M log N) incremental retrieval | architecture · eval report · api server |
debugging model tool-call parsing in vllm (vllm-project/vllm #56635): models generating reasoning traces before tool calls often emit boundary tokens (
<think>,</think>) that leak into raw parser buffers, causing structured tool extractors to fail or emit invalid JSON payloads. identified the root cause in GLM frontend token boundaries, upstreamed the fix directly into the baseParserEngine, and added test assertions verifying zero boundary token leakage during streaming tool-call extraction.
• languages : python, typescript, c++, sql, bash
• genai/llm : litellm, langgraph, openai/anthropic sdk, mcp (model context protocol), langfuse
• data & db : postgresql, pgvector, pymupdf, rapidfuzz, networkx
• backend : fastapi, uvicorn, pydantic, docker, kubernetes, aws (ec2, s3)
• evals/qa : pytest, promptfoo, ruff, git, postman
• also: hardware background — synthesizable 4-wide out-of-order rv32i core (1st place @ sandisk hackathon), fpga zynq-7000 dma, and uvm verification.


