Code

A Code page is a dedicated editor for code and other plain-text formats. It uses Monaco — the same editor that powers VS Code — so you get syntax highlighting, bracket matching, folding, a minimap, and the keyboard shortcuts your fingers already know.

What you can do

• Create a Code page from the + button in the sidebar or from the slash menu inside another page; pick Code as the type.
• Write, paste, and edit code with Monaco's editing surface — multi-cursor, column selection, bracket matching, code folding, and a minimap are all on by default.
• Pick a language from the toolbar dropdown to set highlighting — 25 options ship in: JavaScript, TypeScript, Python, Go, Rust, Java, C, C++, C#, Ruby, PHP, Swift, Kotlin, SQL, Shell, HTML, CSS, SCSS, JSON, YAML, XML, GraphQL, Markdown, SudoLang, and plain text if you just want a text buffer.
• Name the page with a file extension like deploy.sh or parser.ts and the language is detected for you; change it any time from the dropdown.
• Save with Cmd/Ctrl + S for an immediate write, or keep typing and let autosave handle it — the page also saves on its own when the window loses focus.
• Open the page's Version History panel to see past saves, diff any two points, and roll back.
• Share a Code page to a specific teammate at view, edit, share, or delete level, separate from their drive access; viewers without edit rights see a read-only banner.
• Ask a workspace AI agent to drop a script into your tree — Code is one of the page types agents can create for you.

How it works

The editor is Monaco running in your browser. The toolbar language dropdown picks which tokenizer highlights your file. If you name the page with a known extension — .ts, .py, .go, .rs, .sh, and so on — the language is preselected for you from that extension. You can always override it. SudoLang, a pseudocode language for writing structured AI prompts, ships with a custom tokenizer so prompt specs render the way they're supposed to.

Your theme follows the workspace — the editor reads the same background, foreground, and accent colors as the rest of the app, so switching between light and dark modes carries the editor with it.

Saving is debounced: as you type, your changes are queued and written shortly after you stop. Hitting Cmd/Ctrl + S flushes immediately, and so does switching to another window. Every save carries the revision it started from, so if two people save at once the second save notices the first, refetches, and retries instead of silently overwriting. Other people looking at the page see your saved content refresh as you write, unless they're actively editing themselves.

Every save becomes an entry in version history. You can scroll the history, diff any two points, and roll back to any earlier version. Version entries are retained for 30 days by default; older ones are cleaned up in the background.

Permissions resolve from the drive role plus any per-page grant on this specific Code page. There is no inheritance from a parent folder. Every read and save re-checks them, so dropping someone's edit rights takes effect on their next save.

Related

• Pages — the container every Code page lives in, including how version history, trash, and permissions work across page types.
• Files & Uploads — the difference between a Code page and an uploaded code file, and when each one is the right home.
• AI in your Workspace — how agents create and edit Code pages on your behalf.
• Sharing & Permissions — controlling who can read or edit a Code page.