RumataFactory settings & machine controls
Rename a factory, choose its coding agent, manage machine resources, and understand deletion scope.
Step-by-step guidance.
Before you start
- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.
Factory identity and coding agent
Open Factory Settings from Home (opens in a new tab) or the workspace header. Existing factories also have editable name and description fields.
| Control | What it does |
|---|---|
| Frontend source → Source | On Home (opens in a new tab), choose whether to create a new Rumata frontend or work on frontend code already in the connected repository. The new-frontend option creates an owned folder for the factory. Review this choice before saving settings. |
| Factory name / Description | Edit how the factory is identified. Both values are required when editing an existing factory. Save settings applies the changes. |
| Codex / Codex connection | Choose Codex and use the supported sign-in flow when its machine is running. Never paste account credentials into the project chat. |
| OpenCode | Choose Rumata’s managed coding-agent option, which uses Rumata-managed models and platform AI credits. |
| Restart after agent change | When changing the coding agent on an active machine, choose whether to restart it so the new agent can take effect. Saving with restart interrupts that machine’s current work. |
| Save settings / Save & restart machine | Save the selected factory settings. The label changes when the save also restarts the machine. Read it before confirming. |
| Cancel / Close | Dismiss the dialog without applying unsaved field changes. |
Workspace persistence and idle timeout
A development machine is the environment used to build and preview the product. Its shutdown behavior matters even when a deployed frontend continues to run.
| Control | What it does |
|---|---|
| Workspace persistence / Workspace disk | Source and Git history are saved automatically to the retained workspace disk. Inspect its allocated storage separately from active machine compute. |
| Stop an idle machine after | Choose an idle interval from the options allowed by the plan. Editor, terminal, file, build, and chat activity reset the timer. Saving changes this account-wide timer, even though the control appears in Factory Settings. |
| Default / plan maximum labels | Identify which idle option is the account default and which is the longest allowed interval. These are explanatory labels, not separate settings. |
Development machine resources and logs
Open Development machine resources in the workspace header. Wait for the live metrics to finish loading.
| Control | What it does |
|---|---|
| Resources / Logs | Switch between capacity metrics and recent development-machine logs. The Logs view refreshes periodically while open. |
| Refresh logs / Restart machine | Refresh recent logs or open the restart confirmation. A restart interrupts active work and reconnects the machine afterward. |
| Ask agent to fix | Send recent log entries to the factory chat for diagnosis; this can start agent work. Review the information being shared. |
| Restart history | When available, inspect recovered restart count, previous exit reason and last stop time. It is diagnostic history, not a separate restart action. |
| CPU / Memory / Storage cards | Inspect current resource usage and health. Warning colors begin at 80%; critical starts at 95% or after an out-of-memory event. |
| Machine size selector | Choose a supported machine size. Options may be disabled when the account does not have enough machine units. |
| Apply size | Apply a different selected machine size. Rumata saves workspace changes before applying the replacement. Chat, preview, and editor connections can be interrupted while the environment changes. The button is disabled when the selection is unchanged or unavailable. |
| Refresh | Fetch current resource metrics without changing the machine size. |
| Restart machine | Open restart confirmation. The final Restart machine saves workspace changes and replaces the running machine; Chat, preview, and the editor reconnect afterwards. Cancel returns to metrics without restarting. |
| Close | Dismiss the metrics dialog. Closing the dialog does not stop the machine. |
Delete factory confirmation
Delete opens a confirmation. Review it before continuing. Opening or cancelling the dialog leaves the factory unchanged.
| Control | What it does |
|---|---|
| Delete everything this factory owns | Choose whether deletion also removes owned resources. It is selected by default. The listed scope includes workflows and runs, database schema and saved queries, file storage, secrets, production frontend, and the Git frontend folder. |
| Factory name to confirm | Enter the exact factory name shown, without quotation marks. The final action stays disabled until the required confirmation matches. |
| Delete factory and everything / final delete action | Perform the irreversible deletion with the selected scope. The active development machine is stopped before deletion. |
| Cancel | Abort deletion and return to the prior screen or settings dialog. |