Lesson 8 of 8

Designing a Custom Assistant

The final lesson: how to design a Custom Assistant for a job that doesn't fit an existing template.

Start with a single, specific job

The clearer the job — 'answer questions about our warranty terms' rather than 'help with anything' — the more useful the Assistant will be. Vague jobs produce vague configurations.

Scope its Brain access

Decide what part of your Brain the Assistant actually needs. A narrower scope is often more accurate and easier to reason about than giving it everything.

Set its instructions and allowed actions

Write the approved instructions it should follow, and decide what actions it's allowed to take, such as capturing a structured outcome. Review its behavior once it's live and adjust as needed.

Key takeaways

  • Define one specific job, not a general-purpose assistant
  • Scope the Assistant to only the Brain content it needs
  • Set clear instructions and allowed actions, then review its behavior

Continue exploring

Put this lesson into practice