What render, dev, logs, and scheduled tasks are for
- Render: view and use the current Space.
- Dev: change what the Space is made of.
- Logs: read runtime output and check the last change.
- Scheduled tasks: manage work that runs on a plan. They do not replace dev mode.
Stay in the render view for daily use. Open dev mode when you need to change the Space itself.
What dev mode contains
Dev mode can show:
- MCL view: the interface structure. MCL is the AI-native language used to describe a Space. The public language page is still being prepared, so this guide does not teach syntax.
- MCS logic: the Space’s logic.
- Data storage: the data the Space uses.
- Files: workspace files.
- Logs: runtime logs.
Select a file to edit and save it. If the server already has a newer version, load the latest version or keep the local draft. If there are no files, the workspace says so.
Let the agent edit, then check the result yourself
You can save manually, or ask the agent in a session to read and change these parts. Either way, verify the same way: return to the render view and do the real action. If it fails, read the runtime logs, tell the agent the difference, or edit the file yourself.
FAQ
Can the agent change a Space without dev mode?
Yes. The agent can modify the Space from a session. Dev mode is where you inspect and hand-edit the MCL view, logic, data, files, and logs.
Does this guide teach MCL syntax?
No. Syntax belongs on the MCL page. That page is still an opening introduction, not a tutorial.
What if saving fails?
Read the save error. If there is a version conflict, choose load latest version or keep the local draft, then save again.
Next step
Open dev mode in a Space, look at the files and logs, make one small change, and verify it in the render view.
Internal links
- How AI modifies a workspace
- Learn MCL
- How to schedule an AI workspace
- How to create an AI Agent Space