← All AI Engineer talks

AI Engineer Europe 2026

Self-Training Agents: Hermes Agent, HF Traces, Skills, MCP & Finetuning — Merve Noyan, Hugging Face

Read the talk

An AI Engineer at Your Fingertips

Open models, agent traces, skills and managed compute turn a coding assistant into a tool for selecting models, launching training and processing research papers.

From a talk by Merve Noyan

Before you start: Basic familiarity with language models, coding agents and command-line tools will help; no prior Hugging Face experience is required.

What would it take to put an AI engineer at your fingertips?

An assistant that can write code is useful. What would let it also choose a model, adapt it to your data and run the infrastructure? Merve Noyan, introducing herself as a member of Hugging Face’s open source team, begins with the foundation: access to the models and the systems that run them.

Openness comes in layers. Noyan distinguishes downloadable weights with noncommercial restrictions from commercially usable releases, citing DeepSeek and licenses such as MIT and Apache 2.0. Beyond the weights, a project can expose its code and an agent’s harness—the software that manages its execution. Commercial permission is one licensing dimension, rather than a complete definition of open-source AI.

Noyan invokes reports of declining Claude performance to explain why visibility matters: when you control the model and harness, you can inspect and manage changes. Weight access also lets you shrink, quantize or fine-tune a model. Deploying it on an edge device or in a browser can keep inference data local, provided the surrounding application and tools do not send that data elsewhere. Control over deployment makes privacy possible; the full deployment determines whether it holds.

Slide listing control over models, cost reduction, customization and on-device or in-browser privacy, with the speaker at left.
Why open source matters: control, cost, customization and privacy.
0:000:25
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:00 · section reference included

Find a capable model, then choose how to serve it

Control would be less attractive if it required giving up too much capability. Noyan uses GLM 5.1 in her coding setup and points to an Artificial Analysis Intelligence Index chart with open models in green and closed models in black. Her reading of that displayed comparison is that open models have caught up; it is a talk-time comparison, not a claim about today’s changing leaderboard.

The Hugging Face Hub supplies the infrastructure for discovering and distributing those releases, alongside datasets and Spaces. Noyan estimates that the Hub hosts close to three million models at the time of the talk. Filtering for agentic models narrows that inventory. Within it, vision-language models add a useful capability: interpreting screenshots and locating where to click, which lets an agent operate a graphical interface.

Gemma 4 is her example of an omni model that is also agentic; Qwen 3.5 and Kimi K2.5 provide further examples of vision capabilities arriving with a model’s initial release. She expects that pattern to spread. Serving these models is a separate choice: vLLM, MLX and llama.cpp’s llama-server provide local runtime options.

Slide titled “models → agents, serve locally,” listing agentic language and vision models above MLX, vLLM and llama-server command examples.
Agentic models and examples of running them locally.

For a compatible Hub repository, the shell command can be as small as this:

bash

: "${HF_MODEL_ID:?Set HF_MODEL_ID to a llama.cpp-compatible Hub model ID}"
llama-server -hf "$HF_MODEL_ID"

The runtime still has to support the selected model and fit the available hardware. The useful change is that downloading and serving a supported model no longer requires building a serving stack yourself.

2:022:08
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:02 · section reference included

Narrow the choice with benchmarks and provider options

The Hub’s Benchmark Datasets filter offers a more focused starting point than browsing trending models. In the datasets sidebar, select the benchmark filter, then open a benchmark suited to the task. Noyan names SWE-bench Pro, Humanity’s Last Exam and AIME. For coding, she opens a SWE-bench comparison and reports GLM 5.1 at the top of the displayed open-model list.

After using a benchmark to make a shortlist, try the model on your own task. Hugging Face Inference Providers offers hosted access through providers including Groq, Cerebras and Novita. Its selection interface exposes cost and speed options, while a Tool Use column helps identify models suitable for an agent that must call tools.

Selection questionUseful signal
Can it handle this kind of task?Relevant benchmark results
How should requests be served?Cheapest or fastest provider options
Can it participate in an agent workflow?Tool-use support

These answer different questions: a strong benchmark result does not choose the serving provider or establish tool compatibility for you.

4:214:35
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:21 · section reference included

Connect the Hub to a coding agent

With a model selected, the next layer is the agent’s access to the ecosystem. The Hugging Face MCP server connects an assistant to Hub capabilities. Skills supply procedures for tasks such as training: instead of manually assembling every step, a user can ask an agent to train Qwen 3.5 on a dataset. Local coding agents provide another entry point, using models distributed through the Hub.

Noyan favors Pi for its simple setup. In the local arrangement she describes, llama.cpp serves the model and Pi consumes that endpoint. She also suggests Inference Providers as a possible remote route for Pi, but does not establish that integration in the demonstration. Another option is llama-agent, which she describes as a llama.cpp binary that starts an agent from a Hugging Face model ID; the local-agent documentation is the practical reference for that path.

5:486:04
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:48 · section reference included

Hermes: setup, memory and a repaired Slack integration

Hermes Agent adds a persistent assistant around those model choices. Noyan prefers its memory management to OpenClaw’s. Here, learning through saved memory and reusable skills is distinct from fine-tuning: retaining knowledge or a procedure does not itself update model weights.

Hermes can use a local model or Hugging Face Inference Providers. Its setup wizard collects credentials and configures integrations such as Slack or WhatsApp. Noyan recommends GLM 5.1 based on her own experience: after she failed to get a Slack integration working, she asked Hermes running that model to repair it, and reports that it succeeded.

Her next experiments were still prospective: trying Gemma 4 and possibly a forthcoming MiniMax model she had seen rumored on Twitter. Those possibilities sit alongside the demonstrated setup experience, rather than serving as additional results.

7:387:50
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

7:38 · section reference included

Turn saved sessions into inspectable training material

An agent session also produces data. The Hub’s Agent Traces feature accepts sessions from Codex, Claude Code and Pi. Noyan introduces it as a traces repository type; current documentation describes traces stored in datasets or buckets with a dedicated viewer. In her walkthrough, clicking the traces column in Dataset Viewer opens a parsed session that can be explored rather than read as an undifferentiated log.

Those sessions can later become inputs to model training, but uploading them does not automatically train anything. The workflow starts with saved session files, followed by inspection and an optional training step. Review and redact secrets, private code and personal data before publishing traces. Hermes trace support is something Noyan expects to arrive, not something she demonstrates as available.

9:179:33
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

9:17 · section reference included

Match a local model to the application and hardware

For local inference, start with the application you intend to use. On the Hub, Other → Apps filters models by support in tools such as LM Studio, Jan and llama.cpp. That reverses the usual search: instead of discovering a model and then asking whether it runs in your setup, first restrict the inventory to compatible models.

The model repository then exposes format and hardware information. GGUF, associated with llama.cpp, is supported by applications including Ollama and LM Studio. Noyan says a larger Gemma 4 model quantized to four bits fits an L4 GPU with 24 GB of VRAM. The example does not specify the variant, context length, batch size or runtime overhead, so it is not a complete deployment memory budget.

Hardware compatibility information also appears for MLX repositories. Once a suitable model is selected, Use This Model lists supported local applications and provides installation or serving commands. The sequence is straightforward: filter for your application, inspect hardware fit, then obtain the command for that model and runtime.

10:1510:25
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:15 · section reference included

From a training request to a model on the Hub

Hugging Face Skills give coding agents procedures for operating across the ecosystem. The CLI skill handles repositories, jobs and demos. Other skills specialize in the work performed on those resources:

SkillWork it supports
Hugging Face CLIManage repositories, run jobs, launch demos
LLM trainerTrain language and vision-language models locally or remotely
GradioBuild demos
DatasetExplore datasets through the Dataset Viewer API

Claude and Gemini appear as integration examples, not as an exhaustive list of supported agents.

Noyan’s concrete request to Claude Code is to train Qwen2-VL on LLaVA-InstructMix, a vision-language dataset. The assistant does not go straight from that sentence to an opaque training run. It turns the request into configuration decisions:

  1. Ask which compute instance to use.
  2. Estimate the VRAM needed for the model and proposed batch size.
  3. Ask for the validation split and other training choices.
  4. Launch the training job after resolving those choices.
  5. Make the resulting model available on the Hub.

The engineering work has not disappeared: the agent performs the resource estimation and job setup, while the user supplies choices that affect the run.

“Skills in action” slide showing a Qwen2-VL training prompt, infrastructure questions, job-log retrieval, a Hub model card and terminal output reporting a submitted training job.
A training prompt alongside job output and a Hub model card.

The same approach extends beyond language models. Noyan describes skills for training object detectors and Segment Anything Model, including handling different bounding-box formats. That data-format work matters because a training request must ultimately become inputs the chosen model and trainer can consume.

12:0312:24
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:03 · section reference included

Use MCP to discover resources and call AI applications

MCP exposes another route into the same infrastructure: search for models, datasets and Spaces, including semantic search for Spaces. Noyan describes Spaces as an AI app store. Jobs add one-off compute: a job ends when it succeeds or fails, and billing follows its running time. An assistant can therefore discover a resource, invoke an application or launch work through tools connected to the Hub.

The demonstration makes this concrete with a request: “Generate image of a baklava made of yarn.” The assistant calls a remotely hosted Qwen-Image Space and returns the generated output. To broaden discovery beyond the initially configured Spaces, Noyan enables Dynamic Spaces, which she describes as experimental. Its scope is MCP-compatible Spaces, rather than every application hosted on the Hub.

15:0015:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

15:00 · section reference included

Put the pieces together: OCR for research papers

The final workflow begins with a missing input. Hugging Face hosts paper pages that people should be able to ask questions about and share, but not every paper has Markdown suitable for indexing. Noyan introduces a project by her colleague Nils that fills that gap with OCR.

Noyan reports OCR processing of 30,000 papers using Codex, open OCR models and Hugging Face Jobs through prompting. The workflow combines the capabilities introduced earlier: choose an inexpensive, capable OCR model; ask the agent to write the processing code; launch it on Hugging Face infrastructure; and use a skill to arrange the model-serving instance.

For model selection, she returns to Benchmark Datasets and opens olmOCR-Bench, where Chandra OCR appears first in the displayed results. A leading score is only one input to the choice. She also describes a newly released skill that recommends OCR models for fine-tuning, including smaller alternatives when those better suit the task.

This project uses Chandra. The agent writes the processing script, estimates the required instance and calculates the expected cost of running the job. That connects model selection to an operational plan: the output is code and a way to run it on provisioned compute, not merely a recommendation in chat.

Chat screenshot containing an OCR processing response and command block, beside bullets about using the model card, drafting a script and providing a command.
The agent drafts an OCR script and provides a command to run it.

The processing jobs are intended to run again, which makes storage part of the design. Noyan closes with Hugging Face Buckets: mountable storage, compared with S3, that the jobs can use across repeated runs. She describes it as cheaper and faster without supplying comparison conditions or measurements. The substantive endpoint is a repeatable workflow—an OCR model, generated processing code, managed jobs and mounted storage—followed by links for getting started.

16:2216:36
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:22 · section reference included

Resources

From the talk

Read the complete timestamped transcript
  1. 0:00

    [on hold music] Hello, everyone, and welcome to this talk in, uh, Open Agent, uh, Ecosystem, and, uh, I would like to call it Having an AI Engineer at Your Fingertips.

  2. 0:25

    Um, I'm Merve, and I work in the open source team of Hugging Face. How many of you are hugging f- using Hugging Face on daily basis?

  3. 0:33

    Oh, let's change that. This is not okay. Um, but first, let's talk a bit about open source and what it is. So when it comes to machine learning, open source is absolutely differential.

  4. 0:45

    Basically, you have the open-weight models, um, that go in with non-commercial licenses. We call them open-weight. And then we have open source models that have, uh, commercially available licenses, such as this one from DeepSeek.

  5. 1:00

    It's called, uh, uh, MIT License or Apache 2.0. And then there is, like, even more open license, uh, models that have the code open. If you have, like, agents there, the harness is open, everything is open, and this matters even more by the fact that, like, yesterday or the other day, it was revealed that the cloud, uh,

  6. 1:21

    performance was going down. Uh, so if you, if you have everything in the open, nothing changes without you knowing, no performance degradation without you knowing. Everything's great. Uh, but on top of it, if you have access to the weights, you can shrink them, you can quantize them, you can fine-tune them if you feel like it.

  7. 1:44

    And it's absolute guaranteed privacy for your end user because, uh, you can deploy it to edge devices, browsers without the data going somewhere else. Uh, this matters a lot, in my opinion, even more these days with the security breaches and everything.

  8. 2:02

    And there was this argument maybe a few years ago that open source models aren't as good as closed.

  9. 2:08

    No, no, no, no. No, this is not the case. Like you see, for instance, the latest, uh, GLM 5.1 is absolutely crushing it, and I'm actually using it in my coding setup.

  10. 2:17

    Uh, the, this is the, uh, Artificial Analysis Intelligence Index, and the green ones are open models, meanwhile the black ones are the closed models. And we are-- we just catched up, and we will catch up even more with the upcoming models and stuff.

  11. 2:35

    And let's go back to Hugging Face Hub. So everything is facilitated through Hugging Face Hub, all of the open releases. It's the infra layer for all of your open source, uh, workflows.

  12. 2:48

    And as of now, it's hosting even more models. I should have updated the number. It's probably close to three million. A lot of datasets, spaces, and everything, but that's not all when it comes to the agentic ecosystem, and this is what we are gonna talk about today.

  13. 3:03

    So when you go to the models, uh, you can filter for agentic models. Uh, they are mostly the trending ones. And there is, like, two types of models, in my opinion.

  14. 3:15

    There is the v-vision LMs, and then there is the LLMs. And the vision LMs can also act as, like, a computer use agent over the screenshots. They know where to click, et cetera, which is pretty cool.

  15. 3:27

    And one trend I have recently noticed is the fact that you have, uh, labs releasing their LLMs as vision, uh, with vision capabilities day zero. Like, for instance, the Gemma 4 was an omni model, and still it's an agentic model.

  16. 3:45

    There is a Qwen 3.5. Uh, there is Kimi Ki- uh, Kimi K2.5. These were VLMs. So I foresee that all of these models will be, over time, uh, released day zero with vision capabilities.

  17. 4:00

    And, uh, it's super easy to run this actually. Like, you can just use, like, vLLM, uh, MLX, or, like, llama.cpp, llama-server, uh, from the get go with, like, few lines of code.

  18. 4:13

    Like, it used to be much more, um, friction-y, but these days, this is, uh, not a big deal.

  19. 4:21

    And if you want to compare open models, we have recently launched this feature called Benchmark Datasets. So when you go to the datasets, on the left-hand side, there is like, uh, on the bottom, there is a bench-benchmark button.

  20. 4:35

    You just click it, and then you can see the popular benchmarks such as SWE, uh, SWE-bench Pro or Humanity's Last Exam or AIME and others. And when you go to, for instance, SWE-bench to see, like, how your agent is, like, good in coding and stuff, uh, you see the open models ranked according to the scores.

  21. 4:59

    So, like, currently, GLM 5.1 is top of the list.

  22. 5:04

    So it's also easy to pick an open model these days because there's three million models out there, and it used to be a challenge to pick different models.

  23. 5:14

    And if you actually want to vibe check it, Hugging Face has this ser- uh, service called Inference Providers, uh, which does routing for the best models to best providers, like all of the providers out there.

  24. 5:26

    There's Groq, Cerebras, I don't know, Novita, ev-everything. And then it's super easy to compare them as well if you see, like, uh, you have the cheapest or the fastest option.

  25. 5:39

    Actually, I had to truncate it, but also there is the Tool Used column, so you can actually pick one of the open source models for the agentic use case and stuff.

  26. 5:48

    And going back to agents after all of these, uh, Hugging Face Hub shill, uh, Hugging Face Hub actually recently has shipped a ton of, uh, features for you to use open models with agents, agents and stuff.

  27. 6:04

    And first off, like, there is the MCP server where you can plug the hub into your LLM And there is, uh, skills, uh, which allow you to even vibe train models.

  28. 6:16

    Like, you just go to your agent and say, "Train Qwen two-- three point five on this data set for me," and then it just trains. Which to me is like a sci-fi at this point because it used to not exist and, like, there is so many things going on in the back and, uh, and the a-agent actually

  29. 6:34

    handles them very well. And then there is the local agents, so you can run full coding agents, uh, locally from models with Hugging Face Hub because we integrate very well to them.

  30. 6:48

    And coming to the first one, so basically my talk will be consisting about all of these. Uh, coming to the first one, there is the local coding agents and your options, you have, like, actually many, many options, but, like, one of my favorites is Pi because it's, like, super simple to set up.

  31. 7:06

    Uh, basically you can... I, I think you can also use it with inference providers remotely, but also if you want to serve, like, a local coding agent, you can use llama.cpp to serve it, and then Pi will directly consume that.

  32. 7:19

    And, uh, something very cool is also llama-agent, which is baked into llama.cpp as a binary that you can just directly execute and start a model by giving Hugging Face Hub ID.

  33. 7:32

    So it's super easy as well to get a local agent running.

  34. 7:38

    Uh, I will share my slides on my Twitter account after, so no need to take pictures. [chuckles] My-- one of my most favorite things these days is Hermes Agent, and I will just die on this hill.

  35. 7:50

    So this is like, this is a bit one step even further to, uh, from the, uh, OpenClau by means of memory management and everything, and it's actually super easy to get started with that.

  36. 8:03

    And, uh, it is you can either use it locally or with Hugging Face inference providers. So for instance, I was playing with that. Uh, like, the setup wizard does everything for you.

  37. 8:15

    You just give the keys and stuff and then integrate into your Slack or WhatsApp or whatever, and you're good to go. And I absolutely recommend using this. If you want to use it with an open model, I absolutely recommend GL-GLM five point one.

  38. 8:30

    For instance, I actually failed initially to integrate into Slack. I have witnesses in here, my colleague, uh, Nils is here. And, um, I asked GLM five point one to fix it, uh, with the Hermes Agent, and it's fixed on its own and it's, uh, it was a good day.

  39. 8:49

    Like, uh, I, I think GLM five point one is a very good model and I cannot... I can't absolutely wait to use it with Gemma Four. But also this weekend, there was, like, on Twitter, there was a rumored, uh, MiniMax model coming up, so I will also probably try with that and share my findings.

  40. 9:10

    So I absolutely recommend using Hermes Agent with the open models.

  41. 9:17

    And one more thing, so basically, uh, Hugging Face Hub now has a new dataset repository type called traces, and this is basically all of your, uh, Codex, uh, Claude Code or Pi traces, they host it.

  42. 9:33

    And for instance, if you go to your, um, if you pushed, uh, a trace, uh, and then you go over there, you will see in the dataset viewer, if you click on the traces column, uh, it pops up like this.

  43. 9:50

    It is very nicely parsed, and you can just explore your data. And then later, if you want, you can even train a model on that, which is pretty cool in my opinion.

  44. 10:00

    And, uh, if you want to push your agent traces, you, you can just upload your sessions from, uh, these, uh, paths and nothing else is needed. And we will also probably have Hermes Agent very soon for traces.

  45. 10:15

    Uh, going back, if you want to use-- i-if you want more options to serve LLM behind the agent locally, so some tips and tricks in finding a good model.

  46. 10:25

    You just go to Hugging Face. There is an Other tab. Under the Other tab, there is the Apps. So these apps are like LM Studio, Jeanne, um, llama.cpp, everything that is for local serving is over there.

  47. 10:40

    And when you filter for them, you have the models that are supported by these, uh, by these, uh, local apps. So whatever you want to serve, we have you covered.

  48. 10:52

    And when you go to the model repository, something very cool in my opinion is that on the left-hand, right-hand side, there is GGUF, uh, section. So basically GGUF, if you don't know, it's supported.

  49. 11:04

    It's, it's basically comes in llama.cpp, the file, uh, format, uh, that is supported in many things like Ollama, LM Studio, everything. And you have the hardware compatibility. For instance, the Gemma Four larger model, if you quantize it to four-bit, it fits inside an L4 GPU, uh, with the twenty-four gigabyte of VRAM.

  50. 11:29

    So I think this is very cool, and this is also served to, uh, MLX repositories as well. And when you go to the, again, to the model repository, if you have absolutely zero clue on how to serve this model, on top right there is Use This Model, and you have the options of the local apps that the

  51. 11:46

    model is supported in. And when you click that, you see, like, only with few lines of command, uh, that you can run, you install, you get the model served, and voila.

  52. 11:57

    It's very, very convenient to run the open models these days.

  53. 12:03

    And lastly, supercharging your coding agents using Hugging Face skills. So there is-- we have like bunch of skills in order to get you started with training, uh, I don't know, inferring with the open models, using open models, exploring open datasets, using AI apps, everything.

  54. 12:24

    And, uh, we have this thing called Hugging Face CLI skill, which allows coding agents to manage repositories, uh, run jobs, launch demos and everything. And this is how you can install it.

  55. 12:37

    Uh, you can just, uh, type HF skills on Google, and you will find the, uh, commands. Uh, but we have more skills than that. So basically, this allows you to plug Hub in into your agent, like give you all of the, uh, Hugging Face Hub exploration.

  56. 12:53

    But rest of the skills are super cool. There is LLM trainer skill. Basically, this is, uh, this is not only for LLMs, but also vision-language models. You can just tell the model to, okay, train this model on this dataset, and it will just kick off the job remotely, uh, on our infra or like y-locally, wherever you want.

  57. 13:16

    And there is Gradio skill, which allows you to build demos, and there is Hugging Face dataset skill, which allows you to, um, explore datasets, uh, through our Dataset Viewer API, and you can install it very easily.

  58. 13:32

    Again, we come with more integrations. I just put, uh, Claude and Gemini here.

  59. 13:39

    So putting this into action, for instance, I asked the model, uh, to... I, I asked Claude Code to say, "Hey, can you train Qwen2 VL on LLaVA-InstructMix?" Which is like a vision-language dataset.

  60. 13:54

    And it asked me a few questions. It said, "Okay, which instance would you like this to go in?" Because you have multiple options. Uh, the model actually, like in the backend, the agent actually, uh, calculates the amount of VRAM required to run, uh, fine-tune that model in a given batch size and everything.

  61. 14:13

    So it handles everything for you. It just asks you a few questions, "Okay, what is your validation split?" Blah, blah. And then it just l-launches the job, which to me is absolute sci-fi still to this day as a person who have been training models since, I don't know, beginning of my career, like, uh, six, six years. [chuckles]

  62. 14:33

    And you-- at the end, you just find your model on Hub. And this is not limited to LLMs and VLMs. I have recently shipped, um, skills for, for instance, training object detectors or, I don't know, s-segment anything model and everything for vision.

  63. 14:51

    It handles, for instance, different bounding box types and everything. You just give the command and let it handle everything.

  64. 15:00

    And going back to MCP, what do we serve? Uh, we have models, dataset, spaces, search for your task, uh, semantic search for spaces. So if you don't know spaces, it's like the App Store of AI.

  65. 15:13

    You have a ton of, uh, apps over there for absolutely everything you could see. And also we have something called jobs, which allows you to kick off, uh, one of jobs that ends like, uh, if it fails or if it succeeds, and you pay for the amount of time it was up.

  66. 15:32

    And also you can query these apps from MCP. Like, I'm gonna show you shortly, but it plays nicely with all of your favorite platforms.

  67. 15:43

    And so for instance, in here I ask the model, "Generate image of a baklava made of yarn," and then it will call, uh, the Hugging Face space of Qwen image, which is an image generation model hosted remotely, and then it will query that and it will bring, um, the output of that.

  68. 16:02

    It's works very nice. Look. But you need to turn on, there is a setting in the MCP called dynamic spaces. If you want more options of like... If you want absolutely all of the spaces, you need to turn that on, which is a bit of, b-bit experimental.

  69. 16:22

    And here is some few ideas that you can use spaces MCP, uh, but you're absolutely not limited to those. And tying it all together, my colleague, Nils, has built, uh, something, I, which I found cool, so I wanted to share.

  70. 16:36

    So basically, on Hugging Face Hub, there is papers and these papers, basically AI-related papers. We want people to be able to ask questions to these papers or share. Uh, but not all of the papers come with markdown, uh, which the model, which we can index and stuff.

  71. 16:56

    So we OCR thirty, thirty thousand papers, uh, using Codex, Open OCR models and jobs all through prompting, which is a bit crazy. So the steps to do that is firstly, pick an OCR model that is cheap and nice and performant.

  72. 17:12

    Ask the LLM to kick off a processing job and actually write the code for that and then kick it off on Hugging Face infra, and then let the skill set up the instance of hosting that model and everything without you going through the pain of the napkin math, and then profits.

  73. 17:31

    So to pick an OCR model, you need to, um, you need-- you can go to All OCR Bench, which is a benchmark dataset that I have previously shown you.

  74. 17:40

    The first result is Chandra OCR. But don't be fooled by this. We have just today shipped a skill that you can just ask the model, "Okay, what is the best model on OCR for fine-tuning?"

  75. 17:54

    And it will also make recommendations around fine-tuning and stuff. So i-if you need like smaller models, et cetera, it will handle everything for you with this skill. So it's pretty cool.

  76. 18:04

    Check it out. Um, once you pick the model, okay, we, in this case, we use Chandra. Uh, we ask model to write the script, and it did. And then the agent just does the la-napkin math for the instance and, uh, calculates the cost of the running job and everything.

  77. 18:25

    And then these jobs will be... So, so basically, these jobs will be rerun. So we have recently launched this infra, uh, product called Buckets, uh, which is like, uh, S3 buckets, but much cheaper and faster, um, that you can use with, uh, mounting.

  78. 18:42

    And yeah, basically, um, you can just use that. And you can get started, uh, in these links. I hope you like this talk. Thank you so much. [audience clapping] [outro jingle]