Skip to main content
Rork is not a black box. Open More → Code and you get the actual project: a file tree, the source of every file, and a panel of runtime logs underneath.
The Rork code editor showing a web project file tree and the contents of src/App.tsx with syntax highlighting

The Code section: the file tree on the left, the file on the right, and Copy in the corner.

You do not have to read code to use Rork. But four moments make it worth opening:
  1. A bug where you want to see what the agent actually wrote.
  2. A value you want to check, like a price or a piece of copy.
  3. Handing the project to a developer, so you know what they will get.
  4. Curiosity, which is how most people end up learning this.

​
Read the tree

The tree shows one folder per app in the project, so a project with an iPhone app and a web app has two. Inside is an ordinary codebase: src/, components/, pages/, package.json, and the config files a developer expects. One folder is hidden on purpose. Rork keeps its own bookkeeping in .rork/, and the tree leaves it out, except for .rork/DESIGN.md, the design decisions from Design mode. Copy in the top corner copies the whole open file, which is the fastest way to paste something into another tool.

​
Edit by hand

Editing code needs a paid plan. On the free plan the editor shows a banner: “Read-only. Upgrade to a paid plan to edit code.” You can still read every file.
On a paid plan the editor is writable. Change a line and the header gains Unsaved Changes, with Save and Reset All. Cmd + S on a Mac or Ctrl + S on Windows saves too. Two rules to know:
  • You cannot save while the agent is working. The header says Project updating… until the turn finishes.
  • Rork sees your edit. The next message works from the saved file, not from what it wrote earlier.
Hand edits are the one part of Rork with no undo of their own. Reset All throws away unsaved changes, and after Save your edit is part of the project. Ask the agent for the change instead when you can, because then it lands as a version you can revert. See Undo a change and go back a version.
For anything bigger than a one-line fix, ask in chat rather than typing:
The agent finds every place, not just the one you spotted.

​
Read the logs

The panel at the bottom of the Code section is titled Logs, with a count. It shows what your app printed while it ran in the preview, in real time, tagged by level: [log], [info], [warn], [error], [debug]. Scroll up for older lines, and the panel loads them as you go. The chevron on the right collapses it when you want the whole window for code. Logs are the fastest way out of a bug the agent cannot see. When something misbehaves without an error dialog, ask for logs first:
Then reproduce the problem, read the panel, and paste the interesting line into chat.
If the preview throws a visible error you do not need any of this. Press Fix with Rork on the error itself. See Undo a change and go back a version.

​
Take the code with you

The code in this tab is yours. Connect GitHub and you get it as a normal repository, with one commit per agent turn, which you can clone, run locally, and open in Xcode or Android Studio. See How to sync your project with GitHub and How to test & publish your Rork app via Xcode.

​
FAQ

No. Reading is free, editing needs a paid plan. See Plans & Subscriptions.
Not silently. It reads the saved file before it changes anything. Conflicts come from editing the same lines while a turn is running, which is why saving is blocked during a turn.
Hidden from the tree, because it is Rork’s own bookkeeping. .rork/DESIGN.md stays visible.
Not in this tab. Ask the agent instead: “which file sets the free delivery threshold?”.
It says “No logs yet. Logs from your app will appear here.” Interact with the preview, and anything your app prints will arrive.
Yes. Export to GitHub, then run it like any Vite, Swift, or Kotlin project.

​
Next steps

Sync with GitHub

Get the code into your own repository.

Undo and history

Review the diff of any change the agent made.

Get out of an error loop

Use logs to break a cycle of failed fixes.

Keys and secrets

Why keys do not belong in the code you just opened.