HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
qforge-dev
torque
TypeScript2025–2025
qforge-dev / torque

torque

Torque is a Declarative, typesafe DSL for building synthetic LLM datasets — compose conversations like React components

2Distinct people
3Mentions
0Explicit recommenders
96GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Torque is a Declarative, typesafe DSL for building synthetic LLM datasets — compose conversations like React components

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval3 dated mentions

Observed mentions: 2025-11-02 17:16:27 UTC to 2025-11-06 17:24:22 UTC.

012025-11-02 12:00:00 UTC to 2025-11-02 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsNov 2, 12:002025-11-02 18:00:00 UTC to 2025-11-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 00:00:00 UTC to 2025-11-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 06:00:00 UTC to 2025-11-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 12:00:00 UTC to 2025-11-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 18:00:00 UTC to 2025-11-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-11-04 00:00:00 UTC to 2025-11-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-04 06:00:00 UTC to 2025-11-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-04 12:00:00 UTC to 2025-11-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 4, 12:002025-11-04 18:00:00 UTC to 2025-11-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-05 00:00:00 UTC to 2025-11-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-05 06:00:00 UTC to 2025-11-05 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-05 12:00:00 UTC to 2025-11-05 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-05 18:00:00 UTC to 2025-11-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-06 00:00:00 UTC to 2025-11-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-06 06:00:00 UTC to 2025-11-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-06 12:00:00 UTC to 2025-11-06 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 6, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 2, 12:002025-11-02 12:00:00 UTC2025-11-02 18:00:00 UTC110
Nov 2, 18:002025-11-02 18:00:00 UTC2025-11-03 00:00:00 UTC000
Nov 3, 00:002025-11-03 00:00:00 UTC2025-11-03 06:00:00 UTC000
Nov 3, 06:002025-11-03 06:00:00 UTC2025-11-03 12:00:00 UTC000
Nov 3, 12:002025-11-03 12:00:00 UTC2025-11-03 18:00:00 UTC000
Nov 3, 18:002025-11-03 18:00:00 UTC2025-11-04 00:00:00 UTC110
Nov 4, 00:002025-11-04 00:00:00 UTC2025-11-04 06:00:00 UTC000
Nov 4, 06:002025-11-04 06:00:00 UTC2025-11-04 12:00:00 UTC000
Nov 4, 12:002025-11-04 12:00:00 UTC2025-11-04 18:00:00 UTC000
Nov 4, 18:002025-11-04 18:00:00 UTC2025-11-05 00:00:00 UTC000
Nov 5, 00:002025-11-05 00:00:00 UTC2025-11-05 06:00:00 UTC000
Nov 5, 06:002025-11-05 06:00:00 UTC2025-11-05 12:00:00 UTC000
Nov 5, 12:002025-11-05 12:00:00 UTC2025-11-05 18:00:00 UTC000
Nov 5, 18:002025-11-05 18:00:00 UTC2025-11-06 00:00:00 UTC000
Nov 6, 00:002025-11-06 00:00:00 UTC2025-11-06 06:00:00 UTC000
Nov 6, 06:002025-11-06 06:00:00 UTC2025-11-06 12:00:00 UTC000
Nov 6, 12:002025-11-06 12:00:00 UTC2025-11-06 18:00:00 UTC101

What Hacker News says

3 sources
We’ve spent a while trying to generate a very specific, complex, multi‑turn conversation dataset. Most tools pushed us toward glue scripts and one‑off pipelines that were hard to review or reuse. Torque is our attempt to make this boring and predictable: a small, MIT‑licensed framework that treats dataset generation like building a UI. You define small, declarative “components” and compose them into pipelines. The goal is clear code and repeatable runs, not another heavy DSL. It’s early and open source. We’d love feedback on the API design, examples you’d like to see, and rough edges we should fix first. Docs and code: https://github.com/qforge-dev/torque
In React for Datasets

Show HN: Torque – A declarative, typesafe DSL for LLM training datasets (MIT)

We were frustrated with dataset generation DX: ad‑hoc scripts and JSON templates break as flows branch, tool‑calls drift, and reproducibility is hard. So we built Torque: a schema‑first, declarative, fully typesafe DSL to generate conversational datasets. What it is: Declarative DSL - Compose conversations like React components Fully Typesafe - Zod schemas with complete type inference Provider Agnostic - Generate with any AI SDK provider (OpenAI, Anthropic, DeepSeek, vLLM, LLaMA.cpp etc.) AI-Powered Content - Generate realistic varied datasets automatically without complicated scripts Faker Integration - Built-in Faker.js with automatic seed synchronization for reproducible fake data Cache Optimized - Reuses context across generations to reduce costs Prompt Optimized - Concise, optimized structures, prompts and generation workflow
Read the rest
lets you use smaller, cheaper models Quick example Concurrent Generation - Beautiful async CLI with real-time progress tracking while generating concurrently import { generateDataset, generatedUser, generatedAssistant, oneOf, assistant } from “@qforge/torque”; import { openai } from “@ai-sdk/openai”; await generateDataset( () => [ generatedUser({ prompt: “Friendly greeting” }), oneOf([assistant({ content: “Hello!” }), generatedAssistant({ prompt: “Respond to greeting” })]), ], { count: 2, model: openai(“gpt-5-mini”), seed: 42 } ); Links • GitHub: https://github.com/qforge-dev/torque • Try in browser: https://stackblitz.com/github/qforge-dev/torque/tree/main/st... • npm: https://www.npmjs.com/package/@qforge/torque What feedback would help most: • What dataset would you like us to create / recreate? • Do you like the API? Any suggestions on how to change it? License: MIT. Happy to answer questions in the thread!
3 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.