create_canvas
ChatGPTMakes a new, empty canvas in the user’s personal workspace. Use it when they want a new board; to add to one they already have, find it with list_my_canvases instead. Then fill it with edit_canvas.
create_folder
ChatGPTCreate a folder in the user's Brik workspace, at the top level or inside a top-level folder (folders nest one level). If a folder with that name already exists in the same place, it is returned instead (created: false), so calling this twice is safe.
create_tool
ChatGPTSave a tool you wrote to the user's Brik account as a new draft. Read get_authoring_guide first. Brik checks the code and controls; if anything blocks, nothing is saved and you get the problems to fix. On success give the user the editor_url unless a Brik preview card already shows it, and keep the returned tool_id and version for update_tool.
design_tool
ChatGPTDesign one of the user's Brik tools without touching its code: set control values, save looks as presets, and animate controls over time. Call get_tool_design first and pass its design_version as expected_design_version. Everything in one call is saved together, or nothing is: if anything is wrong you get the problems to fix. Saves to the draft; the user publishes in Brik.
edit_canvas
ChatGPTChanges one canvas with a list of ops, applied in order and saved together: if any op fails, nothing is saved and the reply says which op and why. Ops: add_composition (a framed area with a size), add_tool (an instance of a tool, with its own control_values), add_text, update_layer (position, name, hidden, control_values, text and its style, version "newest"), remove_layer (a composition removed keeps its layers, loose), move_layer (into a composition or loose; index 0 is the front), update_tool_instances (every instance of a tool on this canvas to its newest version). Without a rect, Brik fits a layer into its composition or places it in free space, never over the user’s work. Use ref to name something you add and point later ops at it. The user’s own edits in Brik meanwhile are kept.
get_authoring_guide
ChatGPTThe rules for writing a Brik tool: the tool runtime, which controls to give the user and how to wire every control type, background and state rules, and the setup boilerplate for a render host. Call this before writing code for create_tool or update_tool, and again with render_host when you switch libraries.
get_canvas
ChatGPTAn outline of one canvas: its compositions (framed areas with a size, the part that is exported), the layers in each from front to back, and the loose layers outside any. Tool instances carry their control_values and version_state; text carries its words and style. Read it before edit_canvas, so you use real ids and positions.
get_folder
ChatGPTWhat one folder directly holds (tools, canvases, subfolders), newest first. folder_id null lists the items in no folder. Use the ids with move_to_folder (tools, canvases, folders) or rename_tool.
get_tool
ChatGPTFull detail for one public Brik tool: description, creator, stats, canvas size, and the controls a user can tune (names, types, ranges, defaults). Call before recommending a tool so you can say what is adjustable. Takes a slug or uuid from search_tools.
get_tool_design
ChatGPTRead the look of one of the user's Brik tools before changing it with design_tool: every control (key, type, range or options, current value, whether it can be animated), its presets, its animation timeline, and the design_version design_tool needs. Works for any tool the user owns, including ones made in Brik. No code is returned.
list_folders
ChatGPTThe folders in the user's Brik workspace, as a tree (folders nest one level), with how many tools, canvases and subfolders each holds and who it is shared with. Call this first whenever the user wants to organize, file, find or tidy their tools or canvases, and before moving anything: an item moved into a shared folder is shared with the same people.
list_my_canvases
ChatGPTThe signed-in user's own canvases in their personal workspace, most recently changed first. A canvas is the board where they lay out tools, text and compositions. Call this when the user names a canvas ("my Launch canvas") to find its canvas_id.
list_my_tools
ChatGPTThe signed-in user's own Brik tools, most recently changed first, including drafts and private ones. Call this when the user refers to "my tools" or wants to continue one of their own; give them the editor_url to keep working on it in Brik.
list_tags
ChatGPTThe closed vocabulary Brik uses to describe tools, with how many public tools carry each tag. visual_behavior says what the tool looks like or reacts to (Particle System, Typography, Mouse Interaction, 3D...). use_case says where it fits (Hero Backgrounds, Social Media, Posters...). Call this before search_tools and pass exact tag strings.
move_to_folder
ChatGPTFile the user's tools, canvases and folders into a folder, or out to the top level with target_folder_id null. Up to 50 items per call; each one moves or fails on its own (moved / failed). Folders nest one level, and a moved folder takes everything in it along (contains). Moving into a shared folder shares the item with the same people, and moving out stops that: whenever an item comes back with access_change, tell the user in your reply.
rename_folder
ChatGPTRename one of the user's Brik folders.
rename_tool
ChatGPTRename one of the user's own tools, including ones made in Brik. Only the name changes. A published tool shows the new name in Explore; search results can lag behind.
search_tools
ChatGPTFind public Brik tools: animated, interactive canvas pieces (hero backgrounds, particle systems, typography effects, generative art) that people drop into websites, decks and videos. Call list_tags first and pass exact tags for the best results; use query for names and free text. Call with no arguments for the gallery's featured picks. Each result has a viewer_url to open the tool in Brik; always give it to the user.
update_tool
ChatGPTSave a new version of a tool the user's AI apps created with create_tool, with the complete new code and controls. Pass the version from your last create_tool or update_tool as expected_version. Don't have it (a new conversation)? Send expected_version "" with empty code and controls: nothing is saved and you get the current code, controls and version. Tools made in Brik can't be changed here. If anything blocks, nothing is saved and you get the problems to fix.