Tim Becker Profile picture
Aug 14 6 tweets 2 min read Read on X
The previous thread glossed over how our LLM Agents actually work.

The truth is, it took us a long time to figure out how to get reliable and impressive results from agents.

By the end, we learned general strategies to build effective LLM agents, which we're now sharing. 🧵
Strategy #1: Decompose the task

LLM agents excel at tasks generally requiring human intuition to solve, but they can't yet solve arbitrarily complex multi-step tasks. If the task can be solved in multiple parts, you should decompose it as a workflow of multiple agents.
Strategy #2: Curate the Toolset

LLM agents repeatedly call tools until they reach their goal, so curating the toolset is crucial.

The toolset should be as powerful, focused, and helpful as possible. Put up guardrails to prevent your agents from reaching known dead-ends!
Strategy #3: Structure Complex Outputs

Make sure your agent knows exactly what it needs to output, including the precise format of that output. Pro tip: you can ask them to output information which you don't plan to use, but that steers them towards certain ways of thinking!
Strategy #4: Adapt to the Models

Some models excel at precise instruction following; others need more flexibility to achieve a high-level goal.

Also, some models struggle with tool-calling, but you can explore custom tool call formats or (ab)use the `tool_choice` API parameter
This was just a quick summary! For many more details, including specific examples of each strategy in our CRS, check out our blog post:

theori.io/blog/building-…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Tim Becker

Tim Becker Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @tjbecker_

Aug 13
@theori_io's AIxCC CRS has already found dozens of 0day vulnerabilities, and we've barely scratched the surface! The best part: it's open source, so there's no secrets to hide (at least in the AIxCC version 😉)!

So, how does our CRS actually find these 0days? 🧵
We start by passing every function in the source code into LLMs, asking them to consider a wide-range of vulnerability classes and explicitly accept/reject each class. We also run off-the-shelf static analyzers.

Combined, we end up with 10k+ candidate vulns for each project.
Of course, most of these candidates are actually benign, so running our full suite of LLM agents on each report would be wasteful.

Instead, we developed techniques to filter out false-positives and cheaply narrow in on the most likely candidate vulns.
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(