new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Cloudflare Workers · Wrangler · all subjects

bindings & secrets

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Binding declaration validation process

Every binding type has a specific top-level key and required sub-fields defined in the config-schema.json. To validate bindings, read the schema's RawConfig.properties to find the correct key name and shape for each binding type rather than memorizing them.

Common binding declaration validation errors

Common validation errors in binding declarations include: using the wrong top-level key (such as kv instead of the correct key, which must be verified in the schema), missing required sub-fields within a binding declaration, and mixing up singular versus plural key names.

Binding-code consistency validation

The binding or name field value in config must exactly match the property name used in code via env.X. During validation: every env.X reference in code must have a corresponding binding declaration in config, every binding in config should be referenced in code (warn if unused), names must match exactly (case-sensitive), and for Durable Objects the class_name value must match the exact exported class name.

Give your agent this brain