set_brand_kit stores hex and type, not standing behavioral rules

set_brand_kit stores hex and type. Colors, fonts, voice/tone, tagline, logo, product shots, caption style, default aspect ratio. It is a partial upsert: only fields you pass change; colors and fonts merge by key. It is not a standing rule like "never use stock VO." It is not a character turnaround. It is not a one-off "make this one blue." Save the wrong thing here, or save the hex only in chat memory, and every later generate either ignores the value or interpolates it as prose.

Set my brand kit is the named agent job. Say it once; it is applied to everything after. Saving does not use generation credits. After a write, the kit is auto-injected into context so future generations and workflows default to it. Brand kit is the concept. This capability is the write.

No required params. You can share "our color is #FF5733" in conversation and the agent should offer the save. That offer exists because brand details arrive as asides.

What the job is

Canonical brand facts that should be applied literally. A hex is not a vibe. A logo URL is not a description of a logo. Default 9:16 as a kit field is an aspect the renderer can use, which is adjacent to — not the same as — a memory that says you prefer 9:16 when choosing a job.

Read it back with get_brand_kit when you need the full current object. Clear one field with clear_brand_kit_field rather than overwriting the kit. Partial updates are the reason you can add an accent without deleting the logo.

What it is not

• Long-term behavioral memory. Teach the agent a lasting preference is remember: audience, "keep captions minimal," "always plan with this brain." The tool descriptions split this on purpose. Brand assets do not belong in remember. Preferences do not belong in kit fields that cannot hold them.
• Reusable scene characters. Set up reusable characters and products binds reference images to a workflow. A kit product shot is a default still for branding, not a twelve-angle SKU stack for reference-to-video.
• A generate. Setting the kit does not render a branded ad. The next generate_images or workflow run consumes the kit. Confirm that generate separately.
• A disclosure policy the platform will enforce. You can store a caption-style preference. You cannot store Instagram's AI label. Posting still will not flip that toggle.

The waste shows up later: ten people, ten slightly different reds, ten rerolls. A kit is cheaper than a style-guide PDF nobody pastes into the prompt.

The test

Is it a brand value (hex, font, logo file, tone sentence, default ratio, tagline) that should apply until you change it?

Yes: this job. Partial save. Read it back once.

If it is how to decide ("never go over 15 seconds," "always clone my voice"), use remember. If it is a face that must match across scenes, upload an asset. If it is only for this image, put it in the prompt and do not pollute the kit.

FAQ

If I tell the agent the color in a generate request, is it saved?

Not unless set_brand_kit runs. A one-off prompt uses the hex once. Ask to save it, or expect the aside to be offered as a kit update. Do not assume chat history is the kit.

Will adding a new color wipe the old ones?

No. Colors and fonts key-merge. Other fields you omit keep their values. Whole-object replace is the thing this tool was built not to do.

Can the kit pin the video model?

It does not persist model identity. Palette and aspect can match while grain and motion cadence do not. If a house look needs a named model, that is a preference or a saved workflow setting, not a hex.

How do I remove just the logo?

clear_brand_kit_field on the logo. Do not "set a new kit" from scratch to delete one file.