{"schemaVersion":"1","contentVersion":"2026-11-01.13","slug":"system-explorer-code","title":"Code","summary":"Browse source files, inspect changes, and save or push your application code.","category":"System Explorer","manual":true,"minutes":5,"prerequisites":["Access to the factory and the resources you want to inspect."],"technical":[],"sources":["Live Rumata workspace reviewed October 15, 2026; controls inspected without modifying resources."],"related":["controls-code"],"sections":[{"id":"open","title":"1. Open the source editor","blocks":[{"type":"steps","items":["Select Code under Build, or Open code from Frontend.","Wait for the embedded editor to load.","Use the file Explorer to expand folders and open a file."]},{"type":"paragraph","text":"The editor can show the project repository, not just a single screen’s source. Check the file path before editing."}]},{"id":"navigate","title":"2. Find the implementation you need","blocks":[{"type":"steps","items":["Browse the relevant frontend or service folder in Explorer.","Use Search to locate text, components, or symbols.","Open matching files and inspect surrounding code before changing it.","Use Source Control to review pending changes."]},{"type":"paragraph","text":"Other editor areas include Run and Debug, Extensions, Outline, and Timeline. Availability can depend on the editor environment."}]},{"id":"terminal","title":"Use the integrated terminal","blocks":[{"type":"paragraph","text":"You can also open an **integrated terminal** directly in the code editor to run commands, inspect your project, and use development tools without leaving your Rumata workspace."}]},{"id":"edit","title":"3. Make and save a focused change","blocks":[{"type":"steps","items":["Edit the intended file.","Review the diff and any reported problems.","Choose Save Changes in the outer toolbar.","Return to Preview Mode and test the affected feature and its main user flow."]},{"type":"note","title":"Good to know","text":"You can request source changes through the main Rumata chat. Direct editing is optional and best used when you need implementation-level control."}]},{"id":"push","title":"4. Push a reviewed version","blocks":[{"type":"steps","items":["Review all pending files and confirm they belong in the intended update.","Run the project’s relevant checks or ask the chat to run them.","Choose Push to Git when the version is ready to share with the repository.","Read the result and address any reported conflict or failed push."]},{"type":"paragraph","text":"Saving files, pushing to Git, and deploying a public release are separate operations. Follow the publishing guide after testing."}]},{"id":"trouble","title":"5. If the editor does not load","blocks":[{"type":"paragraph","text":"Allow the embedded editor to initialize and check the development-machine state. If it stays unavailable, report the loading message to the chat. Do not assume that the source files have been deleted."},{"type":"note","title":"Check your result","text":"Your intended change is saved, the application behaves correctly in Preview, and any required repository push has a confirmed result."}]}],"updated":"2026-09-29","audience":"general","media":[{"src":"https://docs.rumata.dev/media/system-explorer/code.png","sectionId":"open","width":885,"height":650,"alt":"The embedded code editor with file Explorer and editing panels.","caption":"The embedded code editor with file Explorer and editing panels. Illustrative interface reference; your resources and values may differ."}],"video":null,"url":"https://docs.rumata.dev/guides/system-explorer-code"}