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

# The editor

> Seeing and changing the files yourself

The Computer panel sits beside the conversation. It has the project's files, the
running preview, and the machine's output, and you can work in it directly
rather than only through the agent.

## Files

A full editor over the project, laid out the way a code editor is: a file tree
on one side and the open file beside it. Edits you make are the same files the
agent reads, so it picks them up on its next look rather than overwriting them
blindly.

Writing a file from the agent's side makes it appear in the tree as it lands,
one file at a time, so you can watch a project take shape instead of waiting for
everything at once.

## Preview

The running project at its own address. It is the development server, so a
change to a file is visible without a rebuild.

Previews are private by default. See [Publishing](/computer/publishing).

## Output

Everything the machine prints: install output, build output, and whatever the
running server logs. When something breaks this is where the reason is, and it
is what the agent reads when you tell it something is not working.

`/logs` brings it up from the composer.

## Actions

The toolbar carries buttons the agent sets for you, not a fixed set. When there
is an obvious next step it puts one there: build, start, stop, restart, or a
suggested prompt. They do the same thing as asking, with one click.

## Commands

| Command    | What it does                           |
| ---------- | -------------------------------------- |
| `/logs`    | Show the machine's output              |
| `/stop`    | Stop the machine and the meter with it |
| `/upgrade` | Move the project to a larger size      |
| `/publish` | Change who can reach the preview       |

The panel remembers its layout per chat, so a project you come back to opens the
way you left it.