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

# Messages and session actions: collapse, edit and rerun, fork, copy, and organize

> Actions on a single message (copy, edit and rerun, fork from here, timestamps), and actions on the whole session: browsing, the title, moving to a project, export and import, archiving, and deleting.

This page covers actions on individual messages in a session (collapse, copy, edit, fork, timestamps) and actions on the whole session (browsing long sessions, the title, the **…** menu, moving to a project, export and import, archiving, deleting). For the structure of the agent's replies, see [Reading agent output](https://docs.aihubmix.com/en/cloud/sessions/agent-output.md).

## Where this applies

| Form | Support | Notes |
| - | - | - |
| Desktop app | Supported | All features. Importing sessions from your computer is available only in the desktop app |
| Web app | Supported | Importing sessions from your computer is not available. `.cshare` import works as usual |
| Mobile web | Partial | Hover actions are always shown. The **…** menu is a bottom action sheet. No drag and drop, so moving to a project works only through the menu. Navigation markers are not shown |

## Long messages collapse automatically

Very long messages you send collapse automatically and show only the beginning. Click **Show more** to expand and **Show less** to collapse. The agent's replies do not collapse. Copy, edit, and find in chat always use the full text.

## Hover actions and timestamps

Message action buttons and timestamps appear when you hover (or keyboard focus enters). They are always shown on touch devices.

| Message type | Position | Content |
| - | - | - |
| Messages you send | Below the bubble | **Edited** label (only on edited messages, always shown) · send time · copy · edit |
| Agent replies | The last line of the run | Copy · Fork from here · completion time of the turn |

**Timestamps** show in your local time zone on a 24-hour clock: today shows only the time (`10:33`), yesterday shows "Yesterday 10:33", earlier this year shows "Nov 3, 10:33", and previous years include the year. Hover to see the full date.

## Edit a message and rerun from it

After you edit a message you sent, the agent reruns from that message, and the records after it are discarded.

### When you can edit

* The **Edit** button appears only when the agent used by the session supports rewinding.
* You can edit only messages you sent that contain text. System messages cannot be edited.
* Archived sessions, view-only sessions (for example, sessions on a device controlled by the client on another computer), and sessions waiting in the queue cannot be edited.

### Steps

1. Hover over your message and click **Edit** (pencil icon). You can also press ↑ when the message box is empty to edit your last message.
2. The message turns into an edit box in place.
3. After editing, click **Rerun** or press Enter (Shift+Enter adds a new line). Esc or **Cancel** discards the edit.

| Session state | After clicking **Rerun** |
| - | - |
| Idle | Reruns from this message immediately |
| Running or waiting for you | Stops the current turn first (file changes already made are not undone), then reruns automatically after stopping |
| Stop or edit failed | The reason is shown, and the edit stays in the edit box. You can click **Rerun** again later |

### After editing

* The original message and the records after it collapse into one line, "Edited, N records discarded". Click it for read-only viewing.
* The edited message has an **Edited** label.
* Editing does not undo file changes already written. If you need them undone, tell the agent in the session.

## Fork from here

**Fork from here** copies the session up to a given turn into a new session. You can continue in a different direction in the new session, and the original session stays unchanged.

### Entry points

* The fork icon in the agent reply action row. It appears only on **completed** turns.
* Session **…** menu → **Fork** → **Fork chat in same worktree**: forks from the last completed turn.
* **Fork from the last response** in the command menu (`⇧⌘P`, Windows `Ctrl+Shift+P`).

### Result

1. When the original session is running, you confirm first: both sessions share the same folder, and running them at the same time makes them overwrite each other.
2. The new session opens automatically, and you see **Forked into a new chat; the original is unchanged**.
3. The new session copies only records up to the fork point, and shares the same project folder and branch as the original session. Turns in progress, pending approvals, queued messages, and drafts are not copied.
4. A forked session is a regular session, not a child session.

### Limits

| Situation | What you see |
| - | - |
| No completed turns yet | The menu item is grayed out: **No finished turns yet. You can fork after one turn completes** |
| In the sidebar **…** menu, with the session not open | Grayed out: **Open this chat to fork it** |
| A session running on your computer | Cannot be forked from the middle. Use **New chat in this worktree** instead |
| The run environment version on the cloud server is too old | **Update the cloud server to fork from here** |

### Fork in the … menu

| Menu item | Result |
| - | - |
| Fork chat in same worktree | Same as **Fork from here**, forking from the last completed turn |
| Fork chat in new worktree | Not available yet |
| New chat in this worktree | Creates a blank session that keeps the project, agent, model, and permissions, without chat history |

## Copy

| What to copy | How |
| - | - |
| A message you sent | Hover the message → Copy (including the collapsed part) |
| One agent reply | Hover the reply → Copy (copies the summary text without Markdown syntax). For the last reply, you can also use **Copy the last response** in the command menu |
| A code block, command, or output | Copy at the top right of the code block or code box |
| Session link | **…** → **Copy** → **Copy link**, or `⌥⌘L` |
| The whole session | **…** → **Copy** → **Copy as Markdown**, or `⌥⇧⌘C`. Includes the title, what both sides said, steps, and changed files. The session must be open first |
| Working directory path | **…** → **Copy** → **Copy working directory**, or `⇧⌘C`. Sessions not in a project do not have this item |

On Windows, `⌘` corresponds to `Ctrl` and `⌥` to `Alt`. If copying fails, select and copy it manually.

## Browsing long sessions

* **Opens at the latest message**: a session opens at the latest message by default and follows to the bottom while output streams. When you scroll up, it stops following, and a **Jump to latest** button appears at the bottom right.
* **Find in chat**: press `⌘F` (Windows `Ctrl+F`), or choose **Find in chat** in the command menu, and use **Previous** and **Next** to move between matches. Find covers the whole session.

### Navigation markers

In longer sessions, a column of thin markers on the left of the session area provides quick jumps, with **one marker per turn**.

* The turns currently in view are darker. A bookmarked turn uses the theme color, and a turn waiting for your approval is orange.
* When you point at a marker, a card pops up: your message for that turn, a bookmark button (**Bookmark** / **Remove bookmark**), and an excerpt of the reply. Click a marker or the card to jump to that turn.
* Keyboard: press Tab to focus the marker column, and press Enter to open the **Turns** list.
* Bookmarks are saved only on the current device.
* Shown only with at least two turns. Not shown when the session area is narrow, in split view, or on mobile web.

## Session title

A new session's title is generated automatically after the first turn (**New chat** shows until then) and no longer changes automatically after that. A title you rename manually takes precedence.

### Rename

* On the session page, click the title in the top bar to edit it directly.
* **…** → **Rename**, or `⌥⌘R`.

## The … menu

The **…** in the session top bar and the **…** on a sidebar session row (or right-click) open the same menu. On mobile web, long-pressing a session opens a bottom action sheet:

| Group | Menu items |
| - | - |
| 1 | Rename (`⌥⌘R`) · Pin / Unpin (`⌥⌘P`) · Mark as unread / Mark as read (`⇧⌘U`) |
| 2 | New side chat (top bar menu only) · Fork ▸ · Copy ▸ · Move to project… · Open in new tab · Export as .cshare · Session timer (top bar menu only) |
| 3 | Archive (`⇧⌘A`) · Delete permanently |

* **Open in new tab** opens this session's web app in the browser.
* For side chat, see [Right drawer](https://docs.aihubmix.com/en/cloud/interface/right-drawer.md). For session timers, see [Scheduled tasks](https://docs.aihubmix.com/en/cloud/automation/scheduled-tasks.md). For pinning and unread, see [Sidebar](https://docs.aihubmix.com/en/cloud/interface/sidebar.md).

## Move to project

Drag a session onto a project in the sidebar, or choose a project through **…** → **Move to project…** (you can search, and choose **New project** at the bottom).

| Session → target | Result |
| - | - |
| Session not in any project → project | After you confirm, new messages run in this project, and files in the old temporary working directory are not brought over. This **cannot be undone**. You cannot move it while it is running |
| Already in a project → another project of the same kind (cloud / local), or **Recents** | Only the sidebar grouping changes, and it still runs in the original project's working directory and branch. The session adds a note, and the message offers **Undo** |
| Already in a project → a project of the other kind | Cannot be moved: sessions from cloud projects can only move to cloud projects, and the same applies to local projects |

* Child sessions move together with their parent session and cannot be moved separately.
* Projects you cannot choose (for example, those still being set up, or local projects on another computer) are grayed out with the reason. For drag and drop rules, see [Sidebar](https://docs.aihubmix.com/en/cloud/interface/sidebar.md).

## Export as .cshare

**…** → **Export as .cshare** exports the session as a `.cshare` session package and downloads it to your computer. When done, you see "Exported file name". You can import the exported file in another account or on another device.

## Import sessions

**Import sessions** brings sessions from other tools or other accounts into AIHubMix Cloud, so you can continue them here. The original sessions are not affected. Entry point: **Settings › Integrations › Import sessions**.

### Import from a .cshare file

Available in both the desktop app and the web app.

1. Click **Import from .cshare file** and choose a `.cshare` file.
2. Click **Preview sessions** and check the sessions to import.
3. Click **Import**, and wait for reading, uploading, and importing to finish.
4. The imported sessions appear in **Recents** in the sidebar.

* Only `.cshare` files are accepted, up to 50 MB. Session packages exported from Claude Code, Codex, and AIHubMix are supported.
* If the file is damaged or the version is incompatible, export it again with the latest app. The same session cannot be imported twice. If you are told there are too many imports, try again later.
* After you leave the page, the import continues in the background. Check the sidebar later.

### Import sessions on this computer

Available only in the desktop app. The page lists Claude Code and Codex sessions on this computer.

1. Choose the source tool from **All sources**, or search in **Search sessions or folders**.
2. The list is grouped by project folder. Check items one by one, check a whole group, or use **Select all results**.
3. Click **Import**. Successfully imported sessions are removed from the list. Failed ones stay checked, and you can click **Import** again to retry.

* **Where sessions go**: when a session's working directory matches a local project on this computer, it goes directly into that project. Otherwise, it is placed in **Recents**.
* **Privacy**: sensitive information in session records is removed on your device before import.
* **Limits**: a single session cannot exceed 50 MB. The number of imports per day is limited. When you reach the limit, the button is grayed out; try again the next day.
* **Sessions not in the list**: already imported sessions and internal tool tasks are not listed. Sessions run by AIHubMix and sessions in temporary folders are hidden by default; you can check them in "N hidden" above the list to show them.
* **Refresh sessions** at the top right scans again.

### Import at first sign-in

In the desktop app's first sign-in onboarding, **Bring in your projects** imports projects and sessions on this computer in one go. If the last import did not finish, the next time you open the app it returns to this step to continue.

## Archive and delete

Both are in the last group of the **…** menu in the session top bar and the sidebar.

| Action | Entry point | Result |
| - | - | - |
| Archive | **Archive**, or `⇧⌘A` | The session moves from the sidebar to **Settings › Archived chats**, and the message offers **Undo** |
| Delete permanently | **Delete permanently** | Deleted after you confirm. Chat history cannot be recovered, and project files are not affected |

* Sessions that are running, queued, or waiting for you cannot be deleted. Stop it first or wait for it to finish; you can also archive it first.
* For viewing, restoring, and deleting archived sessions, see [Archived chats](https://docs.aihubmix.com/en/cloud/settings/archived.md).

## FAQ

### Why does my message have no Edit button?

It is not shown when the agent used by the session does not support rewinding. Archived, view-only, and queued sessions cannot be edited either.

### Does editing a message undo files the agent already changed?

No. Editing only discards the earlier records and reruns from this message. File changes already written are kept.

### Why does the turn in progress have no Fork from here?

The fork point must be a completed turn. Wait for this turn to end, or fork from an earlier completed turn.

### Is a forked session a child session?

No. A forked session is a separate regular session. Child sessions are sessions the agent dispatches itself; see [Subagents and child sessions](https://docs.aihubmix.com/en/cloud/sessions/subagents.md).

### What if the generated title is not good?

Rename it. After that, the system no longer changes the title automatically.

## Related

* [Reading agent output](https://docs.aihubmix.com/en/cloud/sessions/agent-output.md)
* [Subagents and child sessions](https://docs.aihubmix.com/en/cloud/sessions/subagents.md)
* [Composer](https://docs.aihubmix.com/en/cloud/sessions/composer.md)
* [Errors and recovery](https://docs.aihubmix.com/en/cloud/sessions/errors-and-recovery.md)
* [Sidebar](https://docs.aihubmix.com/en/cloud/interface/sidebar.md)
* [Account menu and shared overlays](https://docs.aihubmix.com/en/cloud/interface/command-and-menus.md)
* [Keyboard shortcuts](https://docs.aihubmix.com/en/cloud/interface/keyboard-shortcuts.md)
* [Archived chats](https://docs.aihubmix.com/en/cloud/settings/archived.md)


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