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

# Tools, Files, and Generations

> What each desktop surface currently shows and which work can run in the background.

## Files

Files is the browser for the synced OSPRI Science workspace. Its current UI supports:

* Browsing and searching
* Opening and previewing
* Revealing a file in Finder or File Explorer
* Displaying workspace sync state

The Files UI does not currently provide move, rename, delete, or new-folder controls. Approval-gated agent file tools can perform those operations when a task requires them.

## The `@` picker

The composer picker shows files already attached to the draft and artifacts associated with the current chat. It does not search every known workspace file. Open Files or attach a file first when it is not in the current chat.

## Artifacts

Artifacts are outputs attached to one chat, such as reports, spreadsheets, charts, code files, and interactive HTML. Open the Artifacts panel to inspect those outputs beside the conversation.

## Generations

The Generations rail item opens the durable jobs tray. The current user-visible submission path places cloud agent runs there.

It can show queued, running, completed, failed, and cancelled jobs, and it links a job back to its chat. Local direct-provider agent runs are deliberately excluded because their lifecycle is controlled from the chat itself. Use the chat's Stop or Cancel control for those runs. Current local Python actions and **Push to Brain** execute directly rather than entering this tray.

<Info>
  **Run in background** is currently available for the cloud execution lane. It is hidden for local execution. Durable local software work uses **Deep build** and the Code panel instead.
</Info>

## Deep Research

Deep Research opens the cloud investigation workflow. Use it for source-driven work that needs a durable research plan. Its cloud execution and project context differ from an ordinary local direct-provider chat.

## Terminal and Code

* Terminal uses the managed local tool path and streams output.
* Code shows device-folder coding projects and Deep builds.
* Package installation remains approval-gated.
* Generated local files are not public unless you approve a separate upload or publish action.

## Browser and computer use

Managed Chromium and the computer-use driver are runtime components. macOS may require Accessibility and Screen Recording approval. Windows uses its own readiness checks and does not present those macOS permission prompts.