> ## Documentation Index
> Fetch the complete documentation index at: https://ara-90a60a07.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Session files

> Read Markdown and review saved memory, skill, and Project changes in the Files panel.

Markdown files open as rendered documents in the Files sidepanel. For writable files, select the floating **Edit** pill to switch to the source editor. **Save** stores your changes and returns to rendered view; **Cancel** discards the draft.

Completed responses show separate skill, memory, and Project icons for documents the agent updated. Hover over an icon to see the updated documents and available addition/deletion counts. Select a Markdown pill to open the complete saved document. These saved documents remain readable without a running session computer.

Personal memory is displayed as `USER.md`; existing `profile.md` links still open the same document and retain its history. Project instructions use `PROJECT.md`, and skill instructions use `SKILL.md`. Personal memory stays scoped to its owner. Authored skills and Project instructions retain their workspace permissions. Concurrent changes to a saved document require reopening it before saving, so a stale draft cannot overwrite newer content.

Saved Projects use the Project folder icon in the new-session picker regardless of whether their attached Resources include GitHub repositories or machine folders.

Pinned Project revisions and the combined `MEMORY.md` view opened from settings remain read-only. Repository snapshots, imported skill bundles, and documents you cannot modify also open rendered without an Edit control. Editing user memory becomes available after the owner-edit schema migration is installed.

Private browser login state is separate from session files. Its storage is encrypted and scoped to the signed-in user and workspace; it is not a repository file, Project document, or shared session attachment. Saving session files does not export browser logins.

Computer Use settings separate **Cloud Computer** from **Mac Computer**. Cloud settings report saved profile status and any active session; **Save and release browser** retains saved logins while releasing that session’s control. A profile that has not been created is shown as such. Mac settings continue to manage connected devices and local permissions.

When a session asks you to authenticate on its computer, **Open Computer** opens the live view. After you finish, return control to let the agent re-observe the page and continue. Recording attachments use the saved artifact workflow so they remain available in session history; a temporary recording path alone is not a saved attachment.

## Response widgets

Cloud Computer screenshots remain viewable in session history after a run completes or the page reloads. Completed page reads show **Fetched a page**, including while other work is still running.

File changes appear in a response widget below the assistant’s answer, with the first three files visible and **Show more files** for longer lists. **Undo** and **Review** sit together in the header. A separate web-preview widget offers **Open** with an adjacent menu for other browser destinations. Optional follow-up choices share one widget above the response’s copy action.

**Review**, **Open**, and **View PR** use prominent buttons. Pull-request widgets retain the branch and change summary. Session notices explain what failed and place recovery actions beside the message. Archived sessions replace the input composer with an opaque **Session archived** widget and an **Unarchive** action.

New-chat and session composers use the same theme colors. Switching sessions shows a centered loading animation. Panel tabs resize between 100 and 150 pixels, with separators between inactive tabs when several are open.

Composer selectors measure their final menu geometry before appearing and fade without changing geometry, so their panels remain fixed to their triggers while opening.

## Branch a conversation

Select **Branch** below a response to open a new conversation draft with history through that response. Sending your first message creates the fork and opens its own chat. Later source responses are excluded. This uses the Sidechat creation flow and requires Sidechat to be enabled for the workspace. The new conversation starts with independent resource permissions.

## Cloud and Mac computers

**Settings → Computer use** has separate **Cloud Computer** and **Mac Computer**
views. Cloud Computer shows your private browser profile in this workspace,
when it was last saved, and the session currently using it. An empty profile
means no browser state has been saved yet; a saved profile does not mean a
machine is currently running. Mac Computer shows your connected Macs and their
app and browser permissions. Mac browser profiles are not imported into Cloud.

The first cloud browser operation opens the browser profile in Computer. The
cloud agent and Computer pane then use the same visible browser. Shell work and
native app observations do not acquire the browser profile. When a site
requires sign-in, complete authentication yourself in Computer and answer the
sign-in card. Ara checks the page before continuing. Do not paste passwords,
one-time codes, cookies, or authentication URLs into chat.

Cloud browser state is saved privately for your user in this workspace and can
be restored on another cloud machine. Only one session controls the profile at
a time. Use **Open active session** to return to that work, or **Save and release
browser** to retain saved logins and allow the next session to use it. If saving
fails, the page offers a retry instead of claiming the browser was released.
Sites may still expire a login or require authentication again.

For an explicitly requested recording, Ara can capture up to 15 seconds of the
visible cloud desktop without audio. Authentication handoffs are not recorded.
A recording becomes shareable evidence after it has been finalized, inspected,
and uploaded; a temporary machine path is not a durable link.

Cloud browser screenshots can also be saved and attached. The agent captures
the observed page to a managed PNG artifact, then uploads it through the
session's evidence workflow. Browser observations alone are not saved attachments.