HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dottxt-ai
outlines
Python2023–2026
dottxt-ai / outlines

outlines

Structured Outputs

46Distinct people
53Mentions
0Explicit recommenders
16KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Structured Outputs

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:58:53 AM 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 year53 dated mentions

Observed mentions: 2023-07-21 23:46:24 UTC to 2026-10-16 19:42:56 UTC.

05101520252023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 19 mentions; 3 submissions, 16 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 24 mentions; 3 submissions, 21 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC19316
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC24321
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC514
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC514

What Hacker News says

24 sources
This is awesome, and simplifies lot of my workflows when using their APIs directly. I also want to give a shout out to Outlines team, https://github.com/outlines-dev/outlines, they've been doing structured outputs for the last 12 months, and their open source lib can be applied across all open weight and closed/API-based models. Most likely, Outlines heavily inspired the OpenAI team, maybe even using some of their codebase.
In Structured Outputs in the API
> It's coming! CMUSphinx used to have something like this, and there are some [1] solutions [2] on the horizon. > > [1]: https://github.com/alphacep/vosk-api/issues/55 > > [2]: https://github.com/outlines-dev/outlines?tab=readme-ov-file#... It's interesting as speech recognition has become more popular than ever through services like Alexa, and other iot devices support for OS speech recognition has very little development. Don't get me started with accessibility apis either... Unfortunately most implementations (especially those that are iot focused) don't have very important features for robust speech recognition. 1. Ability to enable and disable a grammar 2. Modify grammars while the engine is loaded 3. Scoped grammars that are context-specific 4. Recognition callbacks 5. Multiple grammars active simultaneously. Unfortunately I don't t
Read the rest
hink vosk api will ever support those features. I know there's a few PRs that address a few of those points but have not been merged for years. Given the criteria above there's very little open source that allows for complex grammars that's easy to run for an end user locally.
In Infini-Gram: Scaling unbounded n-gram language models to a trillion tokens
Tantris·Apr 30, 2024Submission

Show HN: LLM-powered NPCs running on your hardware

Hey HN, My team is open-sourcing the inference stack and fined-tuned models we use to create LLM-powered NPCs: https://github.com/GigaxGames/gigax The generative agents paper [1] pioneered the idea of prompting LLMs to create autonomous NPCs. But existing implementations require multiple calls to an LLM to make the agent plan its day, chat with people, and interact with its environment [2]. Our approach allows NPCs to be stepped at runtime with a single pass on consumer-grade hardware, with reasonable latency. To achieve this, we've fine-tuned open-source LLMs [3] to parse a text description of a 3d scene, and respond with custom actions like `greet <someone>`, `grab <item>`, or `say <utterance>`. This simple whitespace-separated « function calling » format is less verbose than json and thus helps with inference speed. We're also using th
Read the rest
e Outlines library [4] to force the model to adhere to this format. We're launching an API and we're looking for partnerships with studios to integrate our tech into upcoming games. Would love to connect if this is of any interest to you! Thanks in advance for your feedback :) [1] https://arxiv.org/abs/2304.03442 [2] https://github.com/joonspk-research/generative_agents/tree/m... [3] https://huggingface.co/Gigax (phi-3 fine-tune) [4] https://github.com/outlines-dev/outlines/tree/main
24 points · Open discussion

Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.

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.