Skip to content

Assistant Builder

Thorsten Sommer edited this page Oct 31, 2026 · 3 revisions

Deutsch: Assistenten-Builder

The "Assistant Builder" creates assistants of your own: you describe what the assistant should do, and AI Studio writes it as an assistant plugin, checks it for security risks, and installs it. Your assistant then appears on the "Assistants" page like the built-in ones.

The Assistant Builder is a beta feature. Switch it on in "Settings" → "App Options": choose "Also show features in beta: these are almost ready for release; expect some bugs" under "Preview feature visibility", then "Assistant Builder: Generate and install assistant plugins" under "Select preview features".

Two kinds of assistants

Under "What kind of assistant should this be?", you choose:

  • "A full assistant with its own input form": it asks for input through a form and builds its prompt from it, like the built-in assistants.
  • "A direct chat launcher tile that opens a preconfigured chat right away": a tile without a form. It opens a new chat with the provider, profile, chat template, data sources, and tools you choose, in a workspace of your choice or as a disappearing chat.

Step 1: Describe the assistant

  1. Open "Assistants" → "Assistant Builder".
  2. Describe the task, the inputs, and the output in your own words under "Describe your assistant", for example: "I need an assistant that turns meeting notes into clear tasks with owners and deadlines."
  3. Optional: in "Advanced Options", set the name, the category, typical inputs, the expected output, the kinds of fields, the output language, whether profiles are allowed, additional rules, and an example prompt. Anything you leave out, the model decides.
  4. Choose a provider, and click "Create assistant draft". Use a powerful model for this.

Step 2: Review the draft

AI Studio first writes a readable draft of the assistant: its name, inputs, output, prompt strategy, tools, and safety notes. It opens in the dialog "Assistant draft":

  • "Preview" shows the draft, "Edit" lets you change it.
  • "Use this draft" accepts it.

Under "Additional changes (Optional)", you can add further wishes. Then click "Generate Assistant". "Change description" takes you back to step 1.

Step 3: Check, install, and open

A progress bar leads you through five steps:

  1. "Validate plugin": AI Studio checks that the generated plugin works.
  2. "Install assistant": AI Studio installs the plugin.
  3. "Security audit": an AI model checks the plugin for risks, such as hidden instructions, leaking data, or tools that don't fit its purpose. The result is "Safe", "Concerning", or "Dangerous".
  4. "Enable assistant": switches the assistant on. By default, AI Studio doesn't enable an assistant rated "Dangerous".
  5. "Open assistant": opens your new assistant, or the chat of a launcher tile.

Not happy with the result? "Edit draft" returns to the draft, and "Regenerate Assistant" creates the plugin again. The new version replaces the installed one.

Changing your assistant later

  • On the page of your assistant, "Revise assistant" lets you describe what should change. AI Studio revises the plugin and keeps it the same assistant.
  • On the "Plugins" page, you can edit, revise, switch off, or delete the plugin; see Plugins.

Every change to the plugin needs a new security audit.

Security settings

The settings of the security audit are in "Settings" → "Agent: Security Audit for external Assistants":

  • "Require a security audit before activating external Assistants?": on by default.
  • "Preselected provider": the model that runs the audits. By default, the provider preselected for the whole app.
  • "Minimum required audit level": "Concerning" by default.
  • "Block activation below the minimum Audit-Level?": on by default.
  • "Automatically audit new or updated plugins in the background?": off by default.

These settings also apply to assistant plugins from other sources. Your organization may set them for you.

Options

In "Assistant: Assistant Builder defaults", you set the provider and the output language the builder starts with.

Where to go next

Clone this wiki locally