HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bennyschmidt
ragdoll-studio
Python2024–2024
bennyschmidt / ragdoll-studio · Archived

ragdoll-studio

The creative suite for character-driven AI experiences.

4Distinct people
16Mentions
0Explicit recommenders
193GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The creative suite for character-driven AI experiences.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 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 week16 dated mentions

Observed mentions: 2024-03-19 01:59:31 UTC to 2024-09-06 19:21:04 UTC. Weeks start Monday, UTC.

01232024-03-18 00:00:00 UTC to 2024-03-25 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsMar 182024-03-25 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-04-01 00:00:00 UTC to 2024-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-08 00:00:00 UTC to 2024-04-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-04-15 00:00:00 UTC to 2024-04-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-04-22 00:00:00 UTC to 2024-04-29 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-04-29 00:00:00 UTC to 2024-05-06 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-05-06 00:00:00 UTC to 2024-05-13 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-05-13 00:00:00 UTC to 2024-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-20 00:00:00 UTC to 2024-05-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-27 00:00:00 UTC to 2024-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-03 00:00:00 UTC to 2024-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-10 00:00:00 UTC to 2024-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 102024-06-17 00:00:00 UTC to 2024-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-24 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-08 00:00:00 UTC to 2024-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-15 00:00:00 UTC to 2024-07-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-22 00:00:00 UTC to 2024-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-29 00:00:00 UTC to 2024-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-05 00:00:00 UTC to 2024-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-12 00:00:00 UTC to 2024-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-19 00:00:00 UTC to 2024-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 00:00:00 UTC to 2024-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-02 00:00:00 UTC to 2024-09-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2

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
Mar 182024-03-18 00:00:00 UTC2024-03-25 00:00:00 UTC321
Mar 252024-03-25 00:00:00 UTC2024-04-01 00:00:00 UTC101
Apr 12024-04-01 00:00:00 UTC2024-04-08 00:00:00 UTC000
Apr 82024-04-08 00:00:00 UTC2024-04-15 00:00:00 UTC110
Apr 152024-04-15 00:00:00 UTC2024-04-22 00:00:00 UTC101
Apr 222024-04-22 00:00:00 UTC2024-04-29 00:00:00 UTC303
Apr 292024-04-29 00:00:00 UTC2024-05-06 00:00:00 UTC303
May 62024-05-06 00:00:00 UTC2024-05-13 00:00:00 UTC312
May 132024-05-13 00:00:00 UTC2024-05-20 00:00:00 UTC000
May 202024-05-20 00:00:00 UTC2024-05-27 00:00:00 UTC000
May 272024-05-27 00:00:00 UTC2024-06-03 00:00:00 UTC000
Jun 32024-06-03 00:00:00 UTC2024-06-10 00:00:00 UTC000
Jun 102024-06-10 00:00:00 UTC2024-06-17 00:00:00 UTC000
Jun 172024-06-17 00:00:00 UTC2024-06-24 00:00:00 UTC000
Jun 242024-06-24 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 12024-07-01 00:00:00 UTC2024-07-08 00:00:00 UTC000
Jul 82024-07-08 00:00:00 UTC2024-07-15 00:00:00 UTC000
Jul 152024-07-15 00:00:00 UTC2024-07-22 00:00:00 UTC000
Jul 222024-07-22 00:00:00 UTC2024-07-29 00:00:00 UTC000
Jul 292024-07-29 00:00:00 UTC2024-08-05 00:00:00 UTC000
Aug 52024-08-05 00:00:00 UTC2024-08-12 00:00:00 UTC000
Aug 122024-08-12 00:00:00 UTC2024-08-19 00:00:00 UTC000
Aug 192024-08-19 00:00:00 UTC2024-08-26 00:00:00 UTC000
Aug 262024-08-26 00:00:00 UTC2024-09-02 00:00:00 UTC000
Sep 22024-09-02 00:00:00 UTC2024-09-09 00:00:00 UTC101

What Hacker News says

3 sources
I built a JavaScript library for creating LLM-based game NPCs, here's a video demo: https://github.com/bennyschmidt/ragdoll-studio/tree/master/e... You drop all their knowledge into a file, like .txt. or .html and it uses RAG to learn everything in the file, so if it's a vendor things like shop inventory, prices, or if it's a storyteller/questgiver you can give it knowledge the player must uncover, etc. It uses the LLM for natural sounding conversations and instructions ("speak in the style of..." etc.)
In Ask HN: Ideas for LLM-Based Games
> You would also need to load an enormous amount of precedential case law Very easily done. Is that it? > lack of common sense, false conclusions The AI tool doesn't replace the judge/DA/etc. it's just a very useful tool for them to use. Checkout the "RAG-based learning" section of this app I built (https://github.com/bennyschmidt/ragdoll-studio) there's a video that shows how you can effectively load new knowledge into it (I use LlamaIndex for RAG). For example, past cases that set legal precedents, and other information you want to be considered. It creates a database of the files you load in, so it's not making those assumptions like an LLM without RAG would. I think a human would be more error-prone than an LLM with vector DB of specific data + querying engine. > I don't see the utility Then you are not paying attention or haven't use
Read the rest
d LLMs that much. Maybe you're unfamiliar with the kind of work it's good at. > actual work involved in practicing law This is what it's best at, and what people are already using RAG for: Reading patient medical docs, technical documentation, etc. this is precisely what humans are bad at and will offload to technology. > actual research is required You have not tried RAG. > LLMs struggle to produce useful outputs You have not tried RAG. > LLMs are unlikely to identify issues You have not tried RAG. > the LLM by definition is creative analysis You have not tried RAG. You can load an entire product catalog into LlamaIndex and the LLM will have perfect knowledge of pricing, inventory, etc. This specific domain knowledge of inventory allows you to have the accurate, transactional conversations that a regular LLM isn't designed for.
In Answering Legal Questions with LLMs

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.