Omni-Codespace

1. Open the sidebar.
2. Use New File or New Folder.
3. Click a file to open it in a tab.
4. Type — autosave runs automatically.
5. If continuous auto indent is enabled, formatting runs immediately when you turn it on and again after autosave.

1. Open New Project.
2. Choose a template, then enter a required unique project name.
3. Omni-Codespace creates starter files and auto-loads the right context for files inside that project.

Tabs show a small dot:

• Yellow: changes are pending save.
• Green: saved successfully.

For linked files, a green dot means it saved to the browser AND wrote back to the original device file.

• Autocomplete shows while typing (no “dot-only” requirement).
• Semantic highlighting improves as you install the right type packs.
• File extension influences language mode (e.g. .ts vs .js).

• Create new files/folders. New script files inside a project folder inherit that project's codebase automatically. Script files outside project roots ask which codebase they belong to.
• Rename, delete (workspace files only).
• Click a file to open it; on mobile the sidebar auto-hides after opening.

At the top of the explorer you’ll see Linked. This area is for device-linked folders/files and virtual linked folders you create.

1. Open the project picker from first run or the New Project button.
2. Select a template such as HTML, Node.js, Minecraft Bedrock, Discord.js, Tauri, Capacitor, Python, Godot, Rust, C#, C++, or GameMaker.
3. Enter a unique required project name, then create it. Files inside that root inherit the project context automatically.

JavaScript and TypeScript files inside a project root inherit that project's environment immediately and do not re-prompt on open or autosave. Standalone script files outside project roots ask what codebase they belong to so suggestions stay accurate.

1. Open GitHub → Settings and enter a fine-grained PAT/access key.
2. Optionally enable Remember this key to keep it in local Omni-Codespace storage.
3. Choose an accessible repository or type any owner/repository path the PAT can access.
4. Choose a branch and workspace folder, then Pull.

1. Open Changes to see added, modified, and deleted files.
2. Select a file to view a Monaco before/after diff.
3. Enter a commit message and Commit. This creates a real Git commit without moving the remote branch yet.
4. Push advances the selected branch using a non-force fast-forward update. If GitHub changed remotely, Omni-Codespace stops and asks you to pull first.

1. In the explorer, open Linked.
2. Click Link Folder and pick a folder on your device.
3. Expand the folder tree. Click a file to open it.
4. Edits autosave. If permission is granted, it writes back to the same file on disk.

Tip: The first time, the browser may ask for permission. Grant read/write to enable true IDE-style saving.

1. Click New Linked Folder.
2. Name it (e.g. “Addon A”, “Addon B”).
3. Open that folder and click the existing Link Files control/link icon to choose one or more files from your device in the same picker.
4. Those files will appear under the folder and autosave back to the originals.

This matches the “two addons” workflow: one linked folder per addon, each containing the linked files you edit most. On desktop, use Shift/Ctrl/Cmd selection in the file picker to link many files at once.

• Edits code in your browser using Monaco.
• Saves workspace files into your browser (IndexedDB).
• If you link device files, writes back only to the specific files you explicitly linked/opened.

• No Omni-Science server upload is required for workspace storage. GitHub traffic goes directly to GitHub's API only when you use GitHub Source Control.
• No GitHub account is required unless you choose to use GitHub Source Control.
• No background Git push/pull: repository mutations require an explicit Commit/Push action.
• No silent access to your device: linking requires an explicit picker + permission.