Three blue and white streams merging into one navy arrow for building a custom AI assistant
Three blue and white streams merging into one navy arrow for building a custom AI assistant

Assistants·6 min

Create Custom AI Assistants

Create and manage custom AI assistants, then equip them with tools, files, and instructions for the work you repeat.

Custom AI assistants let you save a specialist for work you do often: research, writing, coding support, analysis, customer prep, or a personal workflow with a clear job.

When you create an assistant, describe what you want and Losi drafts the name, instructions, and starters — or skip and fill the form yourself. Then add files, tools, and conversation starters before you rely on it.

What a custom assistant is good for

  • A repeating role with a stable job, tone, and checklist.
  • A specialist that should already know your files, docs, or collections.
  • A helper with tools like web browsing or other integrations attached.
  • A shared assistant teammates can pick up without re-explaining the brief.

Create an assistant

1

Open Assistants

Go to /assistants, or open the Assistants section in the sidebar and start a new assistant.

2

Describe the specialist you want

In the create dialog, write a plain description such as "research assistant for competitor briefs" or "draft product launch emails in a clear, calm voice." Or choose Skip and create manually to fill the fields yourself.

3

Review the generated setup

Losi fills in a name, description, instructions, image, and conversation starters. Edit anything that does not match how you work. Use Regenerate if the draft misses the job.

4

Save and try it

Save the assistant, open it from Assistants or with @ in chat, and run one concrete task before you refine the instructions.

Add tools, files, and instructions

After the first draft exists, attach files or collections it should know, choose tools it can use, and tighten the instructions so the job, tone, and limits are clear.

Keep the first version simple: one job, a few source files, and only the tools that matter.

  • Files and collections: manuals, briefs, style samples, research packs, or past examples.
  • Tools and integrations: web browsing and other capabilities the assistant should be allowed to use.
  • Instructions: what success looks like, what to ask before acting, and what not to invent.
  • Conversation starters: a few first prompts that make the assistant easy to open and use.

Use and manage assistants day to day

  • Open /assistants to browse, edit, or start from an existing assistant.
  • In chat, type @ to pick an assistant for the current conversation.
  • Update files and instructions when the project changes so the assistant stays current.
  • Create separate assistants for separate jobs instead of one overloaded generalist.