> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rebind.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Assistant

> Use the in-app Assistant to inspect scripts, edit files, run actions, and resume pending questions or event waits.

Assistant works with the scripts and running Rebind app on your computer.
It can inspect files, make edits, execute inline Luau, and use the Rebind CLI.
Sign in to use it.

## Open Assistant

Open a file in **Scripts**, click **Tools**, then choose **Assistant**. Describe
the task in the message box. You can attach files or images for context.

Opening another file changes the editor context without starting another chat.
Use **New chat** to start a separate conversation, or the chat menu to return
to an earlier one. Messages sent while a turn is working queue behind it.

## Plan and Build

Choose the mode before sending a request:

* **Plan** permits inspection tools and read-only CLI commands. It blocks file
  edits, inline Luau execution, script starts, shell commands, and page actions.
* **Build** permits those changes and actions. File edits and inline Luau can
  execute directly, without a separate confirmation.

The saved-script start tool asks for approval. The shell tool, CLI commands
outside the read-only allowlist, and page clicks, fills, or JavaScript also ask
first.
An inline Luau chunk uses the full SDK, including input output, networking, and
`System.Exec`. Choose Plan when you want inspection before execution.

## Review actions

Expand tool entries to inspect their result or error. Inline Luau entries show
the exact source sent to Rebind. File edits include a diff. For an immediate action,
Assistant can execute a chunk without creating a saved script.

Long-running CLI or shell commands have process controls for reading output,
sending input, or requesting a stop. A command that starts a Rebind script can
leave that script loaded after the command ends; inspect it in **Scripts** or
with [`rebind ps`](/reference/cli#ps).

## Stop a turn

Click **Stop** in Assistant, or press `Esc` while its message box is focused.
Stop prevents the next tool call or model request and requests interruption of
managed command processes. An operation already sent can still finish; its
result is retained while the conversation still belongs to the same account
session. Stop does not undo completed edits or input actions.

Stop also removes already-queued messages in that conversation. While
**Stopping** is shown, Assistant is waiting for dispatched work to settle
before another turn starts. To stop a loaded script, use its **Stop**
control in Scripts. For input recovery, use the
[global kill switch](/getting-started/quickstart#kill-switch).

## History and recovery

Chat history, attachments, drafts, and question forms are stored locally in the
app or browser, scoped to your signed-in account. They do not sync to another
computer. Clearing that local storage removes them.
Queued messages are not restored after reload.

A pending question or event wait can resume after reload when the account
session is still current. A saved answer stays with its original question,
ahead of a queued follow-up in that conversation. Event waits observe the
process locally without making model requests while waiting. Restarting Rebind
ends the process lifetime, so its old wait cannot continue.

Other unfinished operations are marked interrupted. Check the affected files,
scripts, or processes before retrying; an interrupted record does not prove
that the operation never ran. If history cannot be saved, keep the window open
and copy any messages you need before closing it.

## Other AI interfaces

[RebindGPT on the website](https://rebind.gg/chat) drafts code and explanations;
it has no live access to your Rebind app or CLI. The
[`rebind ai` terminal agent](/reference/cli#ai) has its own tool approvals and
saved-session workflow. This page describes the in-app Assistant.