# Code editor, file browser, and Git controls

Understand the full development editor, the read-only source viewer, and the actions that save files or push them to Git.

Source: https://docs.rumata.dev/guides/controls-code
Reviewed: 2026-09-06

## Before you start

- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.

<a id="save-push"></a>

## Rumata’s code actions

Open [System Explorer](https://docs.rumata.dev/guides/controls-preview#navigation) → [Code](https://docs.rumata.dev/guides/controls-code#save-push). Eligible accounts get the full editor connected to the [development machine](https://docs.rumata.dev/guides/development#machine); the fallback frontend source viewer is read-only.

| Control | What it does |
| --- | --- |
| Save Changes | When unsaved files are detected, ask the editor to save them to the [development machine](https://docs.rumata.dev/guides/development#machine). Saving does not publish the website. |
| Push to Git | Request the [development machine](https://docs.rumata.dev/guides/development#machine)’s Git push flow. Wait for its completion message and inspect errors before deploying. |
| Editor Unavailable → Try Again | Retry starting or reconnecting the development editor. |
| Upgrade / dismiss overlay | Review the plan required for full code access or dismiss the upgrade overlay to browse the available read-only files. |

<a id="full-editor"></a>

## Full development editor

The [Code](https://docs.rumata.dev/guides/controls-code#save-push) screen uses code-server, an editor based on the open-source VS Code interface. Its menus can vary with the installed version and extensions. Use the reference below for the editor’s main controls. [Extensions](https://docs.rumata.dev/guides/controls-code-menus#navigation) provide their own commands.

| Control | What it does |
| --- | --- |
| Application Menu | Open the editor’s file, edit, view, navigation, and terminal commands. |
| Explorer | Browse workspace folders. Expand a folder or open a file; the selected file appears in an editor tab. |
| Search | Find text across the workspace. Review matches before using replacement actions, which edit files. |
| Source Control | Inspect changed files and Git differences. Commit records a version; push sends commits to the remote repository. |
| Run and Debug | Open the editor’s debugging tools. Starting a program can execute code in the [development machine](https://docs.rumata.dev/guides/development#machine). |
| Extensions | Inspect or manage editor add-ons. Availability can differ from desktop VS Code. |
| Open Quick Access | Find files and commands from the editor’s top bar. |
| Go Back / Go Forward | Move through editor navigation history, independently of the app preview history. |
| Customize Layout / Toggle Primary Side Bar / Toggle Panel / Toggle Secondary Side Bar | Arrange the editor’s file sidebar, lower panel, and secondary sidebar. |
| Explorer → Views and More Actions / Outline / Timeline | Choose explorer views, inspect the current file’s structure, or review its available history. |
| Manage / Accounts | Open editor settings or editor-provider account controls. These are separate from your Rumata account menu. |
| Branch name / Synchronize Changes | Inspect or change the Git branch, or synchronize with the remote. Synchronizing can pull and push changes; inspect the repository state first. |
| No Problems / problem counts | Open the editor’s reported diagnostics. |
| Forwarded Ports | Inspect exposed development services. These addresses are not the published frontend address. |
| Notifications / keyboard layout | Read editor notifications or inspect the keyboard-layout setting. |

<a id="editor-chat"></a>

## The editor’s own chat panel

A code-server installation can show an additional provider chat panel inside the editor. Rumata’s factory assistant remains in the main workspace conversation.

| Control | What it does |
| --- | --- |
| Toggle Chat / New Chat / Hide Secondary Side Bar | Show, start, or hide a conversation in the embedded editor’s chat interface. |
| Open Customizations / Views and More Actions | Inspect the editor chat’s available customization and layout commands. |
| Add Context / Set Agent / Models / Configure Tools | Configure the editor chat’s context, mode, provider model, and tools. Provider sign-in may be required. |
| Session Target / Permission picker / Send | Choose where the editor agent works, review its permissions, and submit its request. Sending can start work in the same files used by Rumata. |

<a id="source-viewer"></a>

## Rumata’s compact file browser

The compact browser appears in read-only frontend source and activity code screens. Editing controls are available only in editable contexts such as an activity draft.

| Control | What it does |
| --- | --- |
| Files / Content / search field | Search filenames or file contents. Selecting a result opens its file. |
| Folder row / chevron | Expand or collapse a directory. |
| Explorer toggle / resize divider | Hide or show the file list, or change its width. |
| File tab / X / middle-click | Select an open file or close its tab. Closing a tab is not a file deletion. |
| Modified dot | Identify a file with pending editor changes. |
| Save Changes / Discard Changes in an editable activity draft | Apply or discard the current file’s edits in that draft. Creating or publishing the activity is a separate step. |

## Further reading

- [code-server documentation and differences from VS Code](https://coder.com/docs/code-server/FAQ)
- [VS Code layout and navigation reference](https://code.visualstudio.com/docs/configure/custom-layout)

## Related guides

- [Embedded editor menu reference](https://docs.rumata.dev/guides/controls-code-menus)
- [Code and development machines](https://docs.rumata.dev/guides/development)
- [Frontend publishing and traffic controls](https://docs.rumata.dev/guides/controls-frontend)
- [Activity creation and deployment controls](https://docs.rumata.dev/guides/controls-activities)