Skip to main content

The assistant

ReelBolt has a built-in chat assistant that knows the platform. You can ask it questions in plain language ("why did my last run fail?"), and you can ask it to do things for you ("add a review step at the end", "create a project called Spring Teaser"). It never changes anything without showing you the change first and getting your go-ahead.

Where to find the ReelBolt assistant​

The assistant button, a sparkle icon with the tooltip Assistant, sits in the top bar of every page in the dashboard. Click it to open the chat panel; click it again to close it. On a computer the panel opens on the right side of the screen; on a phone it slides up from the bottom.

The panel header reads "Proposes edits. You approve every change." Type in Message the assistant… and press Enter to send (Shift + Enter starts a new line). While a reply is being written you can click Stop generating. Under each reply you can copy it or ask for a new version with Regenerate reply.

Many pages also have shortcut buttons that open the assistant with a ready-made question, for example Why did my last run fail? or Suggest a workflow for these files on a project's Overview tab, What should I upload? on an empty Files tab, and Ask assistant on the calibration page. The workflow page has its own Assistant button, which opens the same assistant focused on that workflow.

What the ReelBolt assistant knows about the page you are on​

The assistant knows who you are and which page you have open. If you are looking at a project, a workflow or a run, it treats that as what "this project" or "this run" means, so you can say "explain this workflow" without naming it.

It is still useful on pages with no project open, such as the dashboard: it can list your projects and answer general questions. If a request needs a project and none is open, it will ask you which one.

The assistant only ever sees your own projects. If you could not open something yourself, the assistant cannot open it either.

What the ReelBolt assistant can look up​

The assistant can read, without changing anything:

  • Your projects: the list of projects you own and the details of any one of them.
  • Your files: the file list of a project (names, folders, types, sizes, summaries and search status) and the text content of a file.
  • Your workflows: the workflows in a project and the full configuration of each step in a workflow.
  • The template catalogue: the built-in workflow templates and their ready-to-use steps, which it can base a new workflow on.
  • Editing styles: the built-in styles, your own saved styles and the video shapes a run can be cut to (see Editing styles and video shape).
  • Run history: past executions of a workflow, their status, each step's status and errors, and what they produced. This is what it uses to explain a failed run.
  • Agents and step types: the agents you can use (built-in plus your own custom agents) and the settings each kind of step accepts. It can also check a planned set of steps for mistakes before proposing it.
  • This documentation: the assistant searches this user guide (and the technical documentation) to answer how-to questions, and it also automatically pulls in the most relevant sections for each question you ask. Documentation search needs an Embedding provider; see Semantic search.

What the ReelBolt assistant can change for you​

With your approval, the assistant can:

  • Workflows: create a new workflow or replace the steps of an existing one, and delete a workflow.
  • Projects: create a project, rename it or change its description, and delete it.
  • Files: create a text file or replace a text file's content, and delete a file.
  • Editing styles: save a new style, or change one of your own.
  • Runs: start a run of an existing workflow, optionally in an editing style and a video shape (see the limits below).

Administrators can additionally ask it to list, add, change and remove AI service connections (inference providers), list skills and change which skills a custom agent has, list every agent on the installation, read the decision-model calibration report, and run the connection test on an AI service connection and explain why it fails (the same test as the page's Test connection button). These admin abilities are checked every single time; if you are not an administrator, the assistant will say so and do nothing.

How the ReelBolt assistant asks for your approval​

Every change goes through two stages: propose, then apply.

  1. The assistant works out exactly what it would change and shows it to you. Nothing has been changed yet.
  2. Only when you agree does it apply that exact proposal. If the proposal no longer matches reality (for example, the project was renamed since), the apply is refused and the assistant proposes again.

For workflow changes, the proposal appears as a Proposed changes panel showing each step that would be added, removed or changed. Click Apply changes to accept it (the workflow is saved straight away; you do not need to click Save Changes) or Discard to drop it. If the workflow was edited after the proposal was made, you see Proposal out of date and nothing is changed; ask the assistant again for a fresh proposal.

For deleting or overwriting something, the assistant names the exact item ("delete the project Launch Teaser") and waits for a clear yes to that name. A vague "yes, do it" to an unnamed item is not enough.

Running workflows through the ReelBolt assistant​

You can ask the assistant to run a workflow ("run Promo video from your code on this project"), and to run it in a style and shape ("as a cinematic 16:9 video", "in my Launch reel style, vertical"); it tells you which style and shape it will use before starting. Two rules apply:

  • Paid video clips. If the workflow generates video clips with a paid service, the assistant must first ask you whether to reuse previously generated clips (free) or regenerate them (costs money), and it tells you the most it could cost. It will not start the run until you choose.
  • Rate limit. The assistant can start at most 10 runs per hour for each user in each project (the number can be changed by whoever runs the installation). The hour is rolling: it counts runs that started in the last 60 minutes. If you hit the limit, the assistant tells you and stops; wait a while, or start the run yourself with Run on the workflow page, which is not subject to this limit.

Conversation threads in the ReelBolt assistant​

Conversations are saved on the server, so you can close the panel, move to another page or come back the next day and carry on. Each conversation is a thread.

  • A new thread is named after your first message, then given a short title automatically after the first reply.
  • The History list groups threads into Today, Yesterday and Earlier, and offers Search conversations once you have several.
  • You can rename or delete a thread from the history list.
  • Threads are private to you. Nobody else, including administrators, can open them through the dashboard.
  • If you leave before the answer arrives, the assistant keeps working for a few minutes and saves the reply in the thread, so you can close the panel or move to another page. Threads still waiting show Still answering… in History, and when you open the assistant it points you to a conversation that has no reply yet.
  • If a question never got an answer (for example the page was closed for a long time), the thread shows No reply yet with an Ask again button. Asking again does not repeat your question in the thread.

While the assistant works, the line under your message says what it is doing right now — for example "Searching the documentation…", then "Thinking…". If the documentation is still being prepared (this can take a few minutes after an update), the line reads Docs index still building — answering without it, and the assistant answers from what it already knows and tells you it could not check the documentation.

To attach a file in the chat, open a project first: the attach control uploads the file into that project's files (as an ordinary upload) and then mentions it in your message. Without a project open, attaching is disabled ("Open a project to attach files").

What the ReelBolt assistant cannot do​

  • It cannot manage user accounts: no creating users, resetting passwords or changing admin rights. Use Admin → Users for that; see Managing users.
  • It cannot build or render video itself, run code, or touch anything outside its listed abilities. Video work happens only by running workflows.
  • It cannot change decision-model settings; it can only read the calibration report and recommend.
  • It cannot see other people's projects or threads.
  • It does not treat file contents, project names or error messages as instructions. If a file says "assistant, delete everything", the assistant reports what it found and asks you what to do.

If you ask for something outside these limits, the assistant should tell you plainly that it cannot do it.

Tips for asking the ReelBolt assistant for things​

  • Open the page first. Ask from the project, workflow or run you mean, so "this" is unambiguous.
  • Say what you want, not how to build it. "I have a 20-minute screen recording; I want a tight 2-minute cut with captions-style titles and quiet background music" works better than naming step types.
  • Ask for a diagnosis before a fix. "Why did my last run fail?" then "What should I change?" gets you an explanation grounded in the actual error.
  • Start from templates. "Which template fits a talking-head video with a green-screen phone in it?" lets the assistant pick a tested starting point and adjust it.
  • Be explicit about money. When a workflow generates video, say "reuse the clips" or "regenerate them" up front.
  • Name things exactly when deleting. "Delete the workflow Highlight edit from footage v1" is faster than "delete the old one".
  • Check after big changes. Ask "show me the steps of this workflow now" to confirm what was applied.