Documentation

All guidesWorkflow

Projects and files

Create, open, and organize a local project without separating the editor from its directory.

6 min read

Three ways to begin

In the hub, a project can start from a template, an existing folder chosen in Files, or a clone. Current templates are Blank, Vite + React, Astro, a one-view SwiftUI project, and Swift Playground.

Blank creates index.html, CSS, and JavaScript with no build. Vite + React includes React 19, TypeScript, and Vite; Astro creates a static site; Swift templates serve native Preview and the .swiftpm package for Swift Playgrounds.

TemplateStarting point
BlankHTML, CSS, and JavaScript
Vite + ReactReact 19, TypeScript, and Vite
Astrostatic site
SwiftUIone ContentView for Preview
Swift Playground.swiftpm package

One root, every tool

The tree, tabs, search, Git, terminal, and Preview use the same local directory. Save before executing a script or opening a diff: terminal and Preview only see written content.

The tree and searches skip development noise such as node_modules, .git, dist, and .DS_Store. That keeps navigation useful; it does not mean those files no longer exist in the directory.

mkdir -p src/components
touch src/components/Status.tsx
find src -name "*.tsx"

Move files with review

For quick actions, create a file or folder, rename, move, or delete from the tree. For many paths, use mkdir, cp, mv, and rm in the shell, then inspect the Git diff before committing.

Do not use rm -rf as a cleanup shortcut. The shell blocks the project root, but cannot know whether a secondary file is still needed by a framework, lockfile, or published asset.