{"schemaVersion":"1","contentVersion":"2026-10-18.1","slug":"development","title":"Code and development machines","summary":"Inspect source code, understand how the preview runs, and keep your development work recoverable.","category":"Go deeper","minutes":9,"prerequisites":["A factory with development-machine access and available allowance.","Permission to edit the source you intend to change."],"sections":[{"id":"machine","title":"What is a development machine?","blocks":[{"type":"paragraph","text":"Your [development machine](/guides/development#machine) runs the tools and preview you use to build your application. It runs separately from the published frontend your users visit."},{"type":"paragraph","text":"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."}]},{"id":"code","title":"Inspect and edit source","blocks":[{"type":"steps","items":["Open [Code](/guides/controls-code#save-push) in the product tools, or use [Open code](/guides/controls-code#save-push) from [Frontend](/guides/controls-frontend#frontend).","Use the file explorer and search to find the relevant part of the app.","Read the surrounding code before making changes, or ask Rumata to explain the file’s role and make a focused change.","Run the project’s available checks and inspect the preview after the edit.","Save and reconcile your changes using the repository’s supported process, then check the source state before publishing."]},{"type":"paragraph","text":"Do not treat a working preview as a substitute for reviewing the code, permissions, or data changes behind it."}]},{"id":"idle","title":"Idle warnings and suspension","blocks":[{"type":"paragraph","text":"The effective idle interval comes from your [billing account](/guides/billing#account)’s development-machine policy. Open [Factory Settings](/guides/controls-factory#factory-details) and read “[Stop an idle machine after](/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."},{"type":"paragraph","text":"Use [Development machine resources](/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](/guides/controls-factory#factory-details) and applies account-wide."},{"type":"note","title":"Stopping use is different from deleting work","text":"Suspension is intended to retain the development draft, but the machine does not promise a persistent filesystem. Put durable application files in [project storage](/guides/system-explorer-storage) and use repository reconciliation for source work."}]},{"id":"recover","title":"Return after suspension","blocks":[{"type":"steps","items":["Reopen the factory and inspect its machine state.","Use the available start/resume action if needed.","Wait for the machine, development services, and chat connection to become ready.","Check source and preview before continuing. If expected work is missing, investigate the draft/repository state instead of overwriting it with a fresh version."]}]}],"technical":[],"related":["controls-code","controls-preview","workspace","publishing","system-explorer-storage","troubleshooting"],"sources":["CONTEXT.md","frontend-preview/README.md","kondor_frontend/rumata_studio/src/components/workspace/DevMachineResourcesDialog.tsx"],"updated":"2026-09-06","audience":"general","media":[],"video":null,"url":"https://docs.rumata.dev/guides/development"}