HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
run-llama
llama_index
Python2023–2024
run-llama / llama_index

llama_index

LlamaIndex is the document processing platform for AI

36Distinct people
44Mentions
0Explicit recommenders
52.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

LlamaIndex is the document processing platform for AI

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, 3:16:21 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 month44 dated mentions

Observed mentions: 2023-01-08 10:29:26 UTC to 2024-05-22 22:27:49 UTC.

0510152023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 16 mentions; 5 submissions, 11 commentsJan 20232023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20232023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 2024

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
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC16511
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC202
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC606
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC422
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC312
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC101
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC303
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC110
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC101
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC211
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC110
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC211
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC101

What Hacker News says

16 sources

Ask HN: How are you building apps that use LLMs?

Iterating workflows such as the ones described here https://github.com/openai/openai-cookbook/blob/main/techniqu... is a bit tedious with Jupyter. I've been using https://natto.dev/ to try out different workflows side-by-side, but was curious to see what other HN users were up to. I'm looking for environments (Jupyter, Natto) more so than libraries like https://github.com/hwchase17/langchain or https://github.com/jerryjliu/gpt_index.
13 points · Open discussion
> Think of ingesting a whole novel that takes place over a few years. I did exactly that with Asimov's Let's Get Together using https://github.com/jerryjliu/gpt_index. It's a short story that's only 8,846 words, so it's not quite a novel, much less the whole of the Harry Potter series, but it was able to answer questions that required information from different parts of the text all at the same time. It requires multiple passes of incremental summarization so it is of course much slower than making a single call to the model, but I stand by my assertion that these things just aren't much problem in practice. They are only a problem if you're trying to paste them into ChatGPT or the GPT-3 playground window or something like that. People are solving the problems with building these systems in the real world almost as fast as the problems
Read the rest
arise in the first place.
In Show HN: Turning books into chatbots with GPT-3
The things I've seen all use hosted language models. For example https://github.com/jerryjliu/gpt_index depends on LangChain, which wraps APIs from hosted LLMs: https://langchain.readthedocs.io/en/latest/reference/modules... AFAIK there's no GPT-3-like LLM that's easy to run at home, because the number of parameters is so so large. Your gaming PC's GPU won't have enough RAM to hold the model. For example, gpt-neox-20b needs about 40GB of RAM: https://huggingface.co/EleutherAI/gpt-neox-20b/discussions/1...
In Ask HN: Is anyone building a question answering system using the HN corpus?
I don't think this kind of prompt leakage really matters from a strategy perspective. Pretty much every breakout internet biz in the past 20 years has been like "an HN comment poster can build that prototype". So what really matters is this thing is up live, it's being relatively widely used, it's integrated with Bing, it's pulling the right summaries of the search results into GPT's very length-constrained prompt context.. Here's yesterday's thread on this prompt context pattern: https://news.ycombinator.com/item?id=34477543 I've been experimenting with the 'gpt index' project <https://github.com/jerryjliu/gpt_index> and it doesn't seem like "oh just put summaries of stuff in the prompt" works for everything -- like I added all the Seinfeld scripts and was asking questions like "list every event related to a coat or jacket" and the insig
Read the rest
hts were not great -- so you have to find the situations in which this makes sense. I found one example output that was pretty good, by asking it to list inflation related news by date given a couple thousand snippets: https://twitter.com/firasd/status/1617405987710988288
In Perplexity.ai prompt leakage

Showing the 15 most recent of 16 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.