> ## Documentation Index
> Fetch the complete documentation index at: https://beta-docs.replo.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Sessions & Mentions
> Conversations persist, you can attach files, and you can point Replo at specific things with @-mentions.
export const Screenshot = ({src, altText, width, shadow = true}) => {
const generateAltText = imageSrc => {
if (!imageSrc) return "Screenshot";
const filename = imageSrc.split("/").pop() ?? "";
const nameWithoutExt = filename.replace(/\.[^/.]+$/, "");
const readable = nameWithoutExt.replace(/[-_]/g, " ").replace(/\b\w/g, char => char.toUpperCase());
return readable === "" ? "Screenshot" : readable;
};
const finalAltText = altText ?? generateAltText(src);
const imageWidth = width ? `${width}px` : "100%";
return ;
};
Your work with Replo happens in conversations that stick around. You can leave and come back, start a fresh conversation for new work, attach files to your messages, and point Replo at specific things with mentions.
## Sessions
Every conversation is saved to your project. Close the tab, come back tomorrow, and Replo is right where you left off, with the full history of what you asked and what it did. Use the chat history menu to browse past conversations, grouped by date.
Start a new session when you begin a separate piece of work. Keeping unrelated work in its own session makes the history easier to follow and gives Replo cleaner context to work from.
## While Replo works
Replo streams its work back as it happens, and the chat stays responsive while it does.
* **Keep typing.** Messages you send while Replo is mid-response are queued and sent automatically when it finishes.
* **Stop it.** Use the stop button to abort a response that is heading the wrong way, then redirect with a new prompt.
* **Step away.** When you tab away from a running session, Replo lets you know when it needs you: an ascending chime (and a "finished" notification) when it completes your request, and a descending chime (and a "needs your input" notification) when it has a question. These only fire when you are not actively watching the session, so they pull you back at the right moment.
## Attachments
Drop files into the chat to give Replo something to work from. Drag and drop works anywhere in the chat. You can attach images and PDFs, video and audio, documents and spreadsheets, and code or text files.
## Mentions
Type `@` in the chat to reference something specific. The mention menu groups what you can point at, including your **pages**, **products**, **assets** (uploaded files and images Replo generated), **integrations**, and **skills**. Mentions remove ambiguity: instead of describing which thing you mean, you point at it, and Replo acts on exactly that.
You can also mention a specific **page** to scope a change to it. The menu has a Pages section (with a search box) listing every page in your site by its route, so you can point Replo at exactly the one you mean.
```text theme={null}
Tighten the hero copy on @/viveks-cat-food/about
```
## Approvals
For sensitive actions, such as using a connected integration or changing who can access a project, Replo pauses and asks first with an approval card in the chat. The card names the action and the tool it uses, and gives you:
* **Allow** to run it this once,
* **Skip** to pass on it this time, or
* a dropdown to change the standing rule for that action: **Always allow** it, keep being asked (**Ask each time**), or **Never allow** it.
Standing rules are remembered per project, so once you have set an action to always allow, Replo keeps moving without interrupting you. Everyday edits, like building pages or adding tracking, run without a prompt. You can review and change all of these rules anytime in [Settings under Permissions](/apps/settings#permissions).