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

# Conversations

> Folders, sessions, worktrees, and what you can type in the message field.

## Folders and sessions

Every conversation belongs to a folder. The sidebar lists your folders, each with its own conversations (in the app, also called sessions). **Add folder** puts another one on the list. **General Chats** is for conversations that are not about a folder.

Each folder keeps its own records: its conversations, schedules and notes stay with it.

## Starting a session

| Where | How |
| - | - |
| Any page | **⌘N** or `/new` opens [Arch](https://docs.archetype.ing/en/use/arch.md). Write what you want done, and Arch finds the right folder and computer for it. |
| A folder | Press **+** on the folder to start the session right there. |
| Terminal | `archetype` in a folder. `archetype --session NAME` opens or creates the session `NAME`. |

`/new NAME` creates a session with that name in the open folder. `/fork [NAME]` starts a new session that picks up from this conversation. The original stays as it is.

## In this folder, or in a copy

If the folder is a Git repository with at least one commit, **+** asks **Work where?**:

* **In this folder**: the session works on your files as they are.
* **In a copy**: the session works in its own Git worktree, which stays apart until you bring the work back. The worktree has its own branch, `archetype/<session>`, made from the newest commit on the repository's default branch. Only committed work comes along.

Tick **Remember** and the folder won't ask again. To be asked again, use the folder's menu. A copy has no ignored files such as `node_modules`, so a session that builds there installs them first.

When you archive a session that worked in a copy, the app shows what the copy has that the folder doesn't:

* **Merge into \<branch>** commits what's left and merges it into the folder's branch.
* **Delete it** removes the worktree and its branch. Anything uncommitted is lost.
* **Keep for later** archives the session and leaves the worktree on disk.

## Continuing

Open any conversation in the sidebar and keep writing. Each conversation keeps its own engine and model ([Engines](https://docs.archetype.ing/en/use/engines.md)). In the terminal, `archetype -c` reopens the conversation you used last.

## The message field

| Type | What it does |
| - | - |
| `@` | Mention a file, another session, or a company's note, project or discussion. Mentioned items are read as they are when you send, and go with your request. |
| `/` | Run a command: `/new`, `/fork`, `/model`, `/permissions`, `/compact`, `/rewind`, `/undo`, `/archive`, `/schedules`, `/help` and more. `//text` sends a message that starts with a slash. |
| `!command` | Runs the command in the folder, if the host allows it. Its output goes with your next request. |

**Enter** sends your message. **Shift+Enter** starts a new line.

## Attachments

Press **Attach files**, or paste or drop files into the field. One request can carry:

* up to 8 files, 30 MiB in total
* images (PNG, JPEG, GIF or WebP) up to 5 MiB each
* other files up to 25 MiB each

**Speak** records a voice message, which the host transcribes when you send it. On the phone, you can attach photos and voice notes.

## While it works

If you send a message while the agent is working, it's added to the running request (**Add to the running request**). Files you send then wait until the request ends.

**Stop** (or **Esc** in an empty field) stops the request. In the terminal, press **Esc** or **Ctrl+C**. If a request was cut off because the host stopped, you can choose **Go on** to pick up from its last step, or **Let it go**.

## Drafts

Anything you've written but not sent stays in that conversation's field, even when you switch to another one. A reload keeps the text, but not attached files. The phone also keeps a draft for each conversation until you send it. If a message fails to send, it goes back into the field so you can try again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.