# Code and development machines

Inspect source code, understand how the preview runs, and keep your development work recoverable.

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

## Before you start

- A factory with development-machine access and available allowance.
- Permission to edit the source you intend to change.

<a id="machine"></a>

## What is a development machine?

Your [development machine](https://docs.rumata.dev/guides/development#machine) runs the tools and preview you use to build your application. It runs separately from the published frontend your users visit.

Opening a workspace can start or reconnect its machine. Follow the allocation, service startup, and chat connection stages on screen to identify where an issue occurs.

<a id="code"></a>

## Inspect and edit source

1. Open [Code](https://docs.rumata.dev/guides/controls-code#save-push) in the product tools, or use [Open code](https://docs.rumata.dev/guides/controls-code#save-push) from [Frontend](https://docs.rumata.dev/guides/controls-frontend#frontend).
2. Use the file explorer and search to find the relevant part of the app.
3. Read the surrounding code before making changes, or ask Rumata to explain the file’s role and make a focused change.
4. Run the project’s available checks and inspect the preview after the edit.
5. Save and reconcile your changes using the repository’s supported process, then check the source state before publishing.

Do not treat a working preview as a substitute for reviewing the code, permissions, or data changes behind it.

<a id="idle"></a>

## Idle warnings and suspension

The effective idle interval comes from your [billing account](https://docs.rumata.dev/guides/billing#account)’s development-machine policy. Open [Factory Settings](https://docs.rumata.dev/guides/controls-factory#factory-details) and read “[Stop an idle machine after](https://docs.rumata.dev/guides/controls-factory#persistence-idle)” for the available options, default, and plan maximum. Editor, terminal, file, build, and chat activity reset the timer; background polling does not count as human activity.

Use [Development machine resources](https://docs.rumata.dev/guides/controls-factory#machine-resources) in the workspace header to inspect the available capacity and settings. Choose a supported machine size there. The idle-timeout setting is in [Factory Settings](https://docs.rumata.dev/guides/controls-factory#factory-details) and applies account-wide.

> **Stopping use is different from deleting work**
> Suspension is intended to retain the development draft, but the machine does not promise a persistent filesystem. Put durable application files in [project storage](https://docs.rumata.dev/guides/system-explorer-storage) and use repository reconciliation for source work.

<a id="recover"></a>

## Return after suspension

1. Reopen the factory and inspect its machine state.
2. Use the available start/resume action if needed.
3. Wait for the machine, development services, and chat connection to become ready.
4. Check source and preview before continuing. If expected work is missing, investigate the draft/repository state instead of overwriting it with a fresh version.

## Related guides

- [Code editor, file browser, and Git controls](https://docs.rumata.dev/guides/controls-code)
- [Preview, network, and console controls](https://docs.rumata.dev/guides/controls-preview)
- [Navigate your workspace](https://docs.rumata.dev/guides/workspace)
- [Publish your app](https://docs.rumata.dev/guides/publishing)
- [Storage](https://docs.rumata.dev/guides/system-explorer-storage)
- [Troubleshoot with a clear next step](https://docs.rumata.dev/guides/troubleshooting)