JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Architecture and workflow guide

A guide to speeding up AI assistants by splitting their work

This guide explains how to build AI software that divides its work. It shows how to use a fast tool for simple choices and a standard AI assistant for writing text and planning steps.

Original by ThinkFlowLabEvaluation

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“system1-agents” by ThinkFlowLab. Read the original source.

This expanded guide is an AI-narrated adaptation prepared by JevMade. It expands the source’s essential ideas, examples and caveats in JevMade’s own words and is not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

Our summary

This project provides instructions for building AI assistants that handle tasks like sorting incoming messages or browsing websites. People use this approach to make their software run faster and cost less by splitting the workload between two different types of AI.

The software uses a fast tool called Jev to pick from a set list of options, like choosing which button to click next. It leaves complex jobs, like writing text or planning the next steps, to a standard AI assistant. A shared connection links both tools to the task.

This guide is useful for people testing different AI tools on the exact same tasks. The speed and cost results happened in the author's specific tests. The software requires a private access code to run, and it cannot handle typing tasks without a standard AI assistant.

Key takeaways

  1. Use a fast AI tool for multiple-choice steps and a regular AI assistant for writing text.
  2. Test different AI tools fairly by recording and replaying them on the exact same tasks.
  3. A shared connection lets you swap out the AI tools without rewriting the whole program.

The speed and cost measurements were reported by the repository authors. A reviewer inspected the code and instructions but did not run the software to verify the claims.

Repository README and documentation · Source reviewed

Read the original guide Opens the author’s site in a new tab.