How we teach you
to build your
own agent.

About the training · University Koans

Forty hours of one-on-one coaching and hands-on coding sessions with our instructor, using exercises and code you can read, change, and keep.

Discuss your 1-on-1 training week

Five eight-hour days · 1-on-1 coaching · Request the detailed curriculum →

An AI agent is an AI program that takes steps and uses tools under rules you set. You start on a practice example based on requirements for a university admissions system—handling applications, required documents, staff reviews, and admission decisions. Our instructor walks you through each exercise with pair programming (working together on the same code) and supported AI coding tools. Later in the week, he tailors the sessions to one focused part of the agent you want to make.

5focused days

401-on-1 hours

1focused agent part

Predict the outcome.
Explain why it works.

The koan teaching approach

What is a koan?

In our training, a koan is a short, hands-on exercise that teaches one practical skill at a time. You start with a small check that does not pass yet—or a short AI prompt that makes mistakes—and work through it step by step with your instructor.

In each koan, you make a prediction about what the system will do, run a test to check it, change one thing to fix the problem, and explain in plain words why your change works. Our University Koans training materials, exercises, and course code are open source, so you can read and change our course code and keep everything you build for your own work.

After mapping out the workflow in the first lesson, you practice every new step through the same six-step loop:

Follow one practice cycle

Choose any step to read what happens in that part of the exercise.

Predict what the system will do

Before running a check or a batch of AI prompts, say what the system should allow, what it should block, or where a short prompt might guess.

Run a test or a batch of AI prompts

Run the same prompt across repeated live AI tests, or run the exercise check to see where the current step fails.

Read why a step failed

Look at the clear error message or saved AI output to see what action was tried and why it did not work.

Change one thing to fix it

Change one thing at a time—clarify a prompt instruction, protect a saved record, add a stage rule, or check a tool’s inputs.

Re-run all checks so earlier steps stay working

Run your checks again to confirm that your new change works and all of your earlier steps still pass.

Explain why your change works in plain words

Finish the exercise by explaining in plain words what mistake your change prevents and how the rule keeps your agent on track.

High-level course overview

How the exercises build step by step

We start together on the admissions practice example, then apply the same building blocks to one focused part of the agent or workflow you choose to make.

Map the workflow & test live AI prompts

In the first lesson, we map out an admissions workflow in plain English—separating actions that read information, preview a possible move, or save a real change. In the next exercises, we run repeated live AI prompt tests to see where a model guesses or makes claims that do not match the facts when it lacks clear rules.

Build stage rules, tools & your agent’s observer part

You pair program in Python with your instructor to build the core parts of your agent. You define stage rules (state machines for what stage a task is in and what can happen next), tools (actions the agent is allowed to take), and diagrams (visual maps of your stages). You also add an observer part to your agent to see what it allows and blocks, while our provided read-only chat lets you ask questions about your files without changing them.

Shape the agent you choose to make

In the later sessions, your instructor tailors the examples to a focused part of your own agent or business workflow. You turn the rules and judgment you use in your work into clear rules for your agent, test how it handles bad requests, and practice explaining how each protection works.

Request the detailed curriculum

The 40-hour week

One week of personal, 1-on-1 training (40 hours)

You work directly with your instructor across five focused days. He walks you through each exercise and pair programs with you step by step—just as he has done with dozens of people in his career—so you can see what your agent is doing and why.

Early in the week: We work together through our University Koans exercises on the admissions practice example. Whether you are on the executive, contractor, or project-owner path, you learn how to turn plain-English requirements into clear stage rules, allowed actions, visual diagrams, and an observer part built into your agent.

Later in the week: Your instructor tailors the examples and one-on-one sessions to a focused part of the agent or workflow you choose to make. We focus on one clear part of your agent so you can test how it follows your rules, explain how it works, and keep improving it.

Included outside the 40 one-on-one training hours: Before Day 1, a 60–90 minute pre-week setup session prepares and checks your workspace (and lunch also sits outside the 40 hours). About two weeks after the final day, every learner joins one 60-minute group clinic (a live group help session). At 30 days, you also complete one repeat check: you make one small change on your own, send in your saved check results and a short explanation, and receive one written review. Post-week follow-up does not include ongoing support for company systems.

Request the detailed curriculum

What you leave with

What you keep after the week

You leave with your own working files, our course exercises, saved test results, and a clear guide for your next steps.

Course exercises & your agent code

Your own copy of our University Koans exercises and the code you write during the week—including the focused part of your own agent that you shaped with your instructor.

Your agent’s observer part, rules & diagrams

The stage rules (state machines), tools (allowed actions), visual diagrams, and observer part you built into your agent, showing what your agent allows and what it blocks.

Saved AI test runs & step-by-step records

Complete results from your repeated AI prompt experiments—keeping failed and incomplete runs visible alongside passing ones—plus a record showing how your system catches the first bad step in a failed run.

Your personal guide & next-steps checklist

An executive business-agent guide, a contractor client-handoff guide, or a project-owner operating guide—plus a realistic checklist of what else is needed before using a prototype with real customers or company data.

Your machine & models

Train on your Windows, Mac, or Linux machine

Bring the computer you already work on. In our 60–90 minute pre-week setup session, we prepare your workshop folder and check your AI model connections before Day 1.

Windows

Use your Windows laptop with a Linux coding workspace set up before Day 1—either Windows Subsystem for Linux (WSL2), which runs Linux inside Windows, or a private remote Linux computer you connect to from your laptop.

Mac

Use your Mac with a private remote Linux computer you connect to from your Mac, or a Linux virtual machine (a Linux system running in a window on your Mac) prepared in pre-week setup.

Linux

Run the coding workshop directly on your Linux computer. We set up the course tools in a new private practice folder during pre-week setup.

Hands-on setup for every learner: Whether you are an executive, contractor, or project owner, we prepare and test this workspace with you before Day 1 so you are ready to build.

Supported AI models & coding assistants

Each part of the workshop connects to supported AI model families. Which specific models you use depends on your account and the exercise, and we check your setup before Day 1:

  • Measured prompt experiments:
    Run repeated live AI tests with OpenAI models through Codex, Anthropic Claude models through Claude Code, or our selected Venice / DeepSeek connection (plus built-in sample replies for offline practice).
  • Read-only workshop chat:
    Use those same OpenAI, Claude, and Venice / DeepSeek connections, plus Gemini Flash and Pro, Claude Opus and Sonnet, and GPT-OSS through our built-in chat connection, and the Grok model family through our Grok chat connection.
  • Coding tutor & your own tools:
    Work with Codex or Claude Code in the coding tutor, or ask in advance to use OpenCode so we can check it in pre-week setup. You can also use your favorite code editor or AI assistant while working on your own agent.
  • Accounts & laptop hardware:
    These AI models run online through their providers using your own account login or private access key (which you enter yourself), so you do not need a powerful graphics card on your computer.

Prerequisites & FAQ

Prerequisites & common questions

What background or preparation do I need?

All three role paths are hands-on and tailored to your starting point. If you are an executive or process owner excited by tools like Claude Code, bring a business workflow you know well. No deep programming background is required—our instructor coaches you step by step as you turn your business rules and exceptions into tested code. If you are a contractor or consultant, you build on your Python and command-line experience to add stage rules (state machines), tool checks, diagrams, and an observer part for client workflows. If you are a project or product owner, you can start from a new idea or an existing project, and we match the coding support to your programming background. Before Day 1, we prepare your setup, select exercises for your background, and agree on one focused part of your agent to build.

How does setup work before Day 1?

About 10 to 14 days before the week, we have a short planning call and a 60–90 minute pre-week setup session outside the 40 training hours. You can train on your own Windows, Mac, or Linux computer. Together we set up your Linux coding workspace—directly on Linux, inside Windows using WSL2, in a Linux virtual machine on a Mac, or on a private remote Linux computer—and we check your AI model and coding assistant connections using access keys you enter yourself.

Are the training materials and code open source?

Our University Koans training materials, exercises, and course code are open source, so you can read, change, and keep our course code, and you keep everything you build for your own work. Hosted AI models (such as OpenAI, Claude, Gemini, Grok, and DeepSeek) and coding assistants run through their own providers under your account and are separate from our open-source course materials.

Can I work on my own agent idea or a company workflow?

Yes. We learn the core method together on the admissions practice example using sample records, and in the later part of the week your instructor tailors the examples to a focused part of the agent or workflow you choose to make. To protect privacy, please keep real customer, employee, client, and private company records out of the training workspace. Connecting directly to live company HR, finance, or customer systems requires a separate engineering project outside this training week.

Does this course finish my whole product or certify it for real-world company use?

No. Bitlemmas Agentic Systems Week is professional training focused on building and testing one clear part of an agent. Passing classroom checks and repeated AI prompt tests shows how your practice system behaves on those tests. Those tests cannot guarantee that a live AI model will never make a mistake. Passing classroom checks also does not make a prototype ready for unattended production use (running live with real people and company data). You leave with a plain-English checklist of what real-world rollout still needs, such as saving data permanently, handling outside service errors safely, and completing a security review.

How do 1-on-1 scheduling, pricing, and post-week follow-up work?

You train one-on-one with our instructor for 40 hours across five days, either in person in Austin or remote (ask us if you want to arrange a custom team week). Our first 40-hour one-on-one pilot with a project owner began in November 2026. Outside the 40 training hours, every learner receives a 60–90 minute pre-week setup session before Day 1. About two weeks after the final day, you join one 60-minute group clinic (a live group help session). At 30 days, you also complete one repeat check: you make one small change on your own, send in your saved check results and a short explanation, and receive one written review. Follow-up does not include ongoing support for live company systems. Talk with us to confirm dates and written pricing, or request the detailed curriculum below.

Discuss your starting point

Inquire

Talk about training or request the curriculum

Prepare an email draft here to ask about a 1-on-1 training week or request the detailed curriculum. Once you send your email, we reply within two business days (and send the detailed curriculum if you requested it).

info@bitlemmas.com

Training is delivered one-on-one with W. Watson (ask us if you want to arrange a custom team week). You can also connect in the Bitlemmas Discord ↗.