Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Here is a huge trick to cut down on hallucinations: I have an agent that processes phone receipts using GPT-4o. Whenever I go to a restaurant or pay for something, I take a photo of the receipt and upload it to Google Drive. The agent goes through the folder...

233,915 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von Santiago
Santiagovor 1 Jahr

Unstract is open-source, and it takes 3 minutes to run locally. They partnered with me on this post. It's pretty popular: they process over 7 million pages monthly and turn them into actionable structured data. Here is their GitHub repository:

Profilbild von Santiago
Santiagovor 1 Jahr

Here is the video on YouTube, in case you want to watch it there:

Profilbild von eSignatures.com
eSignatures.comvor 1 Jahr

Discover Automate your document signing process in minutes. Try now!

Profilbild von tráp — e/acc 🏴‍☠️
tráp — e/acc 🏴‍☠️vor 1 Jahr

Does the cost balance against taking 10 seconds to manually punch these values into a basic form ?

Profilbild von Santiago
Santiagovor 1 Jahr

A company processing the receipts from its 1000 employees would like a word with you.

Profilbild von Adrien Brault-Lesage
Adrien Brault-Lesagevor 1 Jahr

What’s the advantage over using o3-mini alone with no 4o?

Profilbild von Wesley Higbee
Wesley Higbeevor 1 Jahr

Better solution is to abolish taxation this is 💯 a waste of human and AI potential... and they blow the money on shit that helps nobody anyways

Profilbild von Mike Renwick
Mike Renwickvor 1 Jahr

Add dspy to the loop. Train it on good receipts dspy will iteratively rewrite the prompt to optimise towards a metric

Profilbild von Student of Criminology
Student of Criminologyvor 1 Jahr

Alternatively you could try my way to get an accurate output - for free. Text only. But I might look at images when I can get v0-dev to do it right.

Profilbild von Jorge Pérez
Jorge Pérezvor 1 Jahr

Yeah I internally call this an “observer.” As Humans we make mistakes but can self-correct "hallucinations" on the fly. An on-the-fly observer in an Agent is slow/expensive, so it’s more efficient to run it at the end, using even a smaller model can be effective

Ähnliche Videos

I built an agent that answers machine-learning questions. It's autonomous, and the best part is that I built the whole thing without writing a single line of Python code. Here is what I did and how I did it: Over a year ago, a friend and I built a site that publishes multi-choice questions. You get a new one every day. I decided to have GPT-3.5 answer questions. Here is what I needed to build: 1. Connect to the site's API to retrieve today's question 2. Extract the question and the potential choices 3. Connect to OpenAI's API and ask GPT-3.5 to answer the question 4. Parse the answer from the model 5. Submit the answer back to the API to get the score Not difficult. Likely several hours of work. But I didn't have to write any code. I built the whole thing by dragging and dropping components using Vellum is a YC-backed platform for developers to build LLM applications. They are the only ones I've seen offering this functionality. They sponsored this post, and their team helped me with all my questions while I built this. I created a workflow. The platform supports several node types to build whatever you have in mind. I show how I put the whole thing together in the attached video. The only code I had to write was a few lines of Jinja to parse and transform the API and the LLM results. There are three lessons I want to share from this experience: First, the best possible code is the one you didn't write. I'm a big fan of no-code tools because they help me materialize my ideas fast. They help product people, designers, and no coders collaborate on the solution. Second, Large Language Models are sensitive to how you prompt them. Small changes to prompts can make a big difference in results. This is more pronounced when you are building a multi-step workflow. Third, automated testing and evaluation for prompts is critical. There aren't many companies thinking about this. They'll have a hard time moving from a demo phase. The attached video will show you what I did.

Santiago

309,825 Aufrufe • vor 2 Jahren

acpx v0.4 ships Agentic Workflows, or as I like to call them "Agentic Graphs" It let's you create node-based workflows on top of ACP (Agent Client Protocol), to drive any coding agent (Codex, Claude Code, pi) through deterministic steps This let's you automate routine, mechanical legwork like triaging incoming PRs, bugs in error reporting, and so on... For example, OpenClaw receives 300~500 new PRs per day. A lot of them are low quality, but they still relate to real issues, so you have to address them somehow You need to: - extract the intent - cluster them based on intent - figure out if the proposed changes are legit, or whether they are slop local solutions, like trying to catch flies instead of drying out the swamp - if the PR is too low quality or the intent is not clear, close them - run AI review on them them and address any issues that come up - refactor them if the changes are half-baked - resolve conflicts - and so on... So that when the PR is presented to the attention of the maintainer, all the routine legwork is done and the only remaining thing is the decision to (a) merge, (b) give feedback to the PR author, or (c) take over the PR work yourself I wanted to build this feature since a couple months now, since Codex got so good. OpenAI models are now good at judging implementation quality, so I found myself repeating the same steps I wrote above over and over I also tried putting all this in a single prompt. But I believe there are workflows that should not be a single prompt, but a sequence of prompts in the same session That is because like humans, LLMs are prone to PRIMING. I claim that putting all steps in the same prompt at the beginning of the context will generally give suboptimal results, compared to revealing the intention to the model step by step Creating such a workflow also gives more OBSERVABILITY into the each step that an agent is supposed to take. Agent generates JSON at the end of each step, and that structured data can be used to monitor thousands of agents running at the same time in an easier way, on a dashboard Similar features have been introduced in e.g. n8n, langflow. But AFAIK they are not integrating ACP like the way I do I wanted to have a fresh approach, and to build an API that I can develop freely the way I want, so I created a new workflow API inside acpx The video is from the workflow run viewer, but that is not where you build the workflow. You build it by using the acpx flow typescript API. See examples/pr-triage in acpx repo Before building that, I started from a Markdown file with a Mermaid chart of the flow I had in mind. The Markdown file acts as a spec for the flow, and I have built the workflow through trial and error. I call this process "workflow tuning" I started working on acpx repo PRs one by one, tuning the flow, slowly scaling to more PRs. Finally, when I felt confident, I ran it in parallel over all external open PRs in the acpx repo. I believe it already saved me hours this week My next goal, if well received, is to set this up on a cloud agent so that it can process the 300~500 PRs the OpenClaw repo receives every day, in real time, as they come in I believe this will save all open source maintainers around the world countless hours and make it much easier to herd and absorb external contributions from everyone!

Onur Solmaz

149,558 Aufrufe • vor 4 Monaten