How much does zuzu.codes cost?

The starter track is free — read all lessons and practice for free. Full access to every track (current and future) is $14.99/month. Cancel anytime.

How long does each track take?

Each track is designed as a 30-day challenge — one lesson per day, about 15 minutes each. Go at your own pace, but the structure is built around daily consistency.

What's the lesson format?

Each lesson is a student-teacher dialogue with code examples, followed by a hands-on code challenge in an in-browser editor. You read, you understand, then you write real code.

Do I need prior coding experience?

Our beginner track starts from absolute zero — no prior experience needed. Advanced tracks build on earlier ones, and the platform tells you exactly where to start.

How is zuzu.codes different from freeCodeCamp or Codecademy?

zuzu.codes uses a structured 30-day track format with dialogue-based teaching, an in-browser code editor, and gamification (XP, streaks, progress tracking). The format builds genuine understanding through daily practice.

Day 22 · ~11 min●

Last quiz of the track. Ten questions on the composition primitives — read→write, filter→act, time windows, error handling per step, step logging. 80% to pass.

When you pass: you can wire any pair of Composio tools together, filter what passes between them, scope by time, log every step, and recover from per-step failures. The full primitive set for everyday automation.

What week 3 covered

Lesson	Concept
15	Read → Write — fetch from one API, send to another
16	Filter → Act — conditional side effect
17	Time windows — `datetime` + Gmail's server-side `query`
18	Errors in chains — per-step `try/except` + `raise`
19	Step logging — print before and after each step
20	Synthesis — 4 primitives composed cleanly

What the full track covered

By passing this quiz, you've worked through the Automation primitives kit:

Calling tools: toolset.execute_action(Action.X, {args}), runtime-injected
Reading: list and dict response shapes, .get(key, default) defensive reading
Filtering: Python-side and server-side
Side effects: send, create, append, update — and the IDs they return
Idempotency mindset: predicting whether a write-loop doubles on re-run
Dedup: in-memory set of seen keys + continue to skip
Composition: read → write, filter → act, time-windowed reads
Reliability: per-step try/except, step logging

Auto Intermediate (deferred for v1) goes deeper: retries with backoff, persistent state across runs, multi-tool chains, scheduled triggers, observability. AI Beginner adds LLMs to the same shape — same execute_action-style call, with complete() injected alongside toolset.

Sign up to practice

Create a free account to get started. Paid plans unlock all tracks.

Day 22 · ~11 min●

Last quiz of the track. Ten questions on the composition primitives — read→write, filter→act, time windows, error handling per step, step logging. 80% to pass.

What week 3 covered

Lesson	Concept
15	Read → Write — fetch from one API, send to another
16	Filter → Act — conditional side effect
17	Time windows — `datetime` + Gmail's server-side `query`
18	Errors in chains — per-step `try/except` + `raise`
19	Step logging — print before and after each step
20	Synthesis — 4 primitives composed cleanly

What the full track covered

By passing this quiz, you've worked through the Automation primitives kit:

Calling tools: toolset.execute_action(Action.X, {args}), runtime-injected
Reading: list and dict response shapes, .get(key, default) defensive reading
Filtering: Python-side and server-side
Side effects: send, create, append, update — and the IDs they return
Idempotency mindset: predicting whether a write-loop doubles on re-run
Dedup: in-memory set of seen keys + continue to skip
Composition: read → write, filter → act, time-windowed reads
Reliability: per-step try/except, step logging

What week 3 covered

Lesson	Concept
15	Read → Write — fetch from one API, send to another
16	Filter → Act — conditional side effect
17	Time windows — `datetime` + Gmail's server-side `query`
18	Errors in chains — per-step `try/except` + `raise`
19	Step logging — print before and after each step
20	Synthesis — 4 primitives composed cleanly

What the full track covered

By passing this quiz, you've worked through the Automation primitives kit:

Calling tools: toolset.execute_action(Action.X, {args}), runtime-injected

Reading: list and dict response shapes, .get(key, default) defensive reading

Filtering: Python-side and server-side

Side effects: send, create, append, update — and the IDs they return

Idempotency mindset: predicting whether a write-loop doubles on re-run

Dedup: in-memory set of seen keys + continue to skip

Composition: read → write, filter → act, time-windowed reads

Reliability: per-step try/except, step logging

What week 3 covered

Lesson	Concept
15	Read → Write — fetch from one API, send to another
16	Filter → Act — conditional side effect
17	Time windows — `datetime` + Gmail's server-side `query`
18	Errors in chains — per-step `try/except` + `raise`
19	Step logging — print before and after each step
20	Synthesis — 4 primitives composed cleanly

What the full track covered

By passing this quiz, you've worked through the Automation primitives kit:

Calling tools: toolset.execute_action(Action.X, {args}), runtime-injected

Reading: list and dict response shapes, .get(key, default) defensive reading

Filtering: Python-side and server-side

Side effects: send, create, append, update — and the IDs they return

Idempotency mindset: predicting whether a write-loop doubles on re-run

Dedup: in-memory set of seen keys + continue to skip

Composition: read → write, filter → act, time-windowed reads

Reliability: per-step try/except, step logging