hammad 🔍

2.5K posts

hammad 🔍

hammad 🔍

@HammadTime

normal considered harmful | cto @trychroma

Berkeley, CA Katılım Eylül 2009
2.7K Takip Edilen2K Takipçiler
Sabitlenmiş Tweet
hammad 🔍
hammad 🔍@HammadTime·
Last year at @tryramp I laid out three predictions for how language models would evolve. I was trying to clarify which bets might actually be durable over time. A lot of it is now starting to take shape. Here’s an update. Thread 👇
English
3
7
138
28.6K
dave jan
dave jan@prometx3·
@HammadTime @trychroma @HammadTime is there any timeline on the harness release? Have been experimenting with a custom built, tried to stay as close as possible through reading the article, but the model keeps breaking on harder retrievals after some turns. (it starts to repead random sentences/words)
English
1
0
1
41
hammad 🔍
hammad 🔍@HammadTime·
My favorite part of working on the @trychroma Context-1 report was how easy interactive explanations have become with AI coding. As a longtime fan of sites like explorabl.es and ciechanow.ski the barrier to quickly iterating on and building interactive explainers is now so absurdly low. No excuse for every developer facing company to not invest in these.
English
1
1
21
910
hammad 🔍
hammad 🔍@HammadTime·
hammad 🔍@HammadTime

#3 - At first, capability gets discovered outside the model in prompts, chains, routers, tools, human supervision, and harnesses. As models improve, more of that gets trained in. This is part of why we bias toward giving models filesystem tools today. These tools are already being post-trained in. What happens when models get better at generic tool use and composition? (They will.) Is your system structured in a way that can accommodate that? Can you take advantage of it when it happens? We’ve seen similar patterns before — in computer vision, and in hardware (e.g. northbridge/southbridge consolidation). Component consolidation is a fairly natural outcome in engineering systems.

1
0
2
858
Viv
Viv@Vtrivedy10·
The Model-Harness Training Loop imo every great team in the world will use some version of this loop to build the best agents for their tasks this is now possible because: 1. Harness Engineering is becoming more democratized and accessible (we want it to be even easier) 2. Open models have crossed an intelligence threshold (ex: GLM 5) 3. We have mechanisms to collect traces and analyze them at massive scale (ex: LangSmith) 4. The infra to fine-tune models is becoming more accessible (ex: @PrimeIntellect) Open models give every team the opportunity to try this, not just frontier labs We’re entering a time where any obsessed team can pick a niche, understand model failure modes today, and build a killer harness that engineers around model issues to solve the task. That might mean spending a lot of compute today. As more data comes in, you build data moats and then train the best, most cost-efficient vertical model that improves over time The cycle of harness engineering —> finetuning with open models is gonna give us an explosion of task specific frontier level performance at a fraction of the cost + latency that we have today by using the frontier models for everything we’re gonna see some generational cooking at the intersection of open models & harnesses 🚀
Viv tweet media
English
14
39
295
62.2K
hammad 🔍
hammad 🔍@HammadTime·
@hvent90 @trychroma For id hallucination “virtual” simpler ids helps. So map the ids to something simpler like an integer by order of first appearance during the rollout before passing to the model
English
0
0
0
70
Henry Ventura
Henry Ventura@hvent90·
The failure modes I've ran into with my own equivalent are: - it folds the initial message - it hallucinates message IDs (I prepend "[id: {uuid}]" before each message) - it doesn't think to peek the folded contents when it gets lost Each of these has a potential solution which I'm excited to try. Did you run into similar challenges when training it? I'm having to create some wild UI so that I can play detective. It feels like at every step of the way in interpreting evals, something is misrepresenting what is actually happening.
Henry Ventura tweet mediaHenry Ventura tweet mediaHenry Ventura tweet media
English
1
0
0
70
hammad 🔍
hammad 🔍@HammadTime·
want to scale this idea up 100000x? - we're hiring @trychroma
Andrej Karpathy@karpathy

LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.

English
10
8
214
32.4K
hammad 🔍
hammad 🔍@HammadTime·
@hvent90 @trychroma context-1 is trained on using the prune tool, which edits context. Before training the base model is pretty inaccurate with using it
English
1
0
1
286
Henry Ventura
Henry Ventura@hvent90·
Props on getting effective context eviction. I’m experimenting with introducing some limited primitives to allow an agent to evict context (non destructively, it can query/peek original content) but initial findings are about a ~7% drop in success rate. I’ve identified some failure modes to see if I can reduce though.
English
2
0
2
362
hammad 🔍 retweetledi
Jeff Huber
Jeff Huber@jeffreyhuber·
Chroma Context-1 is #5 on Hugging Face
Jeff Huber tweet media
English
3
2
19
4K
will brown
will brown@willccbb·
common offenders: - context management - user sims - native tool parsing - harness-in-sandbox - harness-outside-of-sandbox - no sandbox at all - groupwise rewards - intermediate rewards - multiple environments - resource management - custom metrics/error handling - offline evals
English
7
4
126
5.8K
will brown
will brown@willccbb·
whenever i see a new RL framework pattern i’m like hey man this is a really nice pattern but what if i wanna do the niche but not that niche thing that your design fundamentally precludes
English
9
3
172
11.7K
hammad 🔍
hammad 🔍@HammadTime·
@xamgore @fire @trychroma we're working on it! we're a small team, we very much want to release it, it just requires some work to disentangle from our full internal codebase, which we're doing. ill reach out when its live!
English
0
0
3
45
Igor Strebz
Igor Strebz@xamgore·
@fire @trychroma > is trained to operate within a specific agent harness > the harness is not yet public. 🤨
English
1
0
1
190
Chroma
Chroma@trychroma·
Introducing Chroma Context-1, a 20B parameter search agent. > pushes the pareto frontier of agentic search > order of magnitude faster > order of magnitude cheaper > Apache 2.0, open-source
English
141
403
4.2K
1.1M