Files

Files works like a code editor: the explorer on the left shows your project tree with Git status, and every file you open gets a tab. Close a tab with its × or a middle click; a file with an unsaved draft keeps its tab, marked with a dot, until you save or discard it. The bar above the code holds the file's path and actions, and the status bar below shows the branch, the selected lines and the file's encoding. The tree and its Git badges follow changes made outside Bud, and a reload shows the tree your browser last saw while Bud reads the latest.

To keep a project read-only, turn editing off. Files then only views code; Git review, staging and conflict resolution still work:

export default defineConfig({
  routes: ['/'],
  files: { edit: false },
})

Editing

Edits are drafts until you save with Ctrl/⌘+S. A save only succeeds if the file on disk is still the version you opened; if something else changed it, Bud keeps your draft and shows the conflict instead of overwriting.

New files, folders, renames and deletes are previewed before they apply. Deleted and moved originals stay recoverable.

Review

Compare the working file with the staged version, HEAD or any commit, and step through its history. Stage or unstage whole files, hunks or selected lines. Merge conflicts open in a resolver with both sides and the base.

Review actions never change branches or move refs, and every write is checked against the revision you were looking at.

Search

Search file names with Ctrl/⌘+P. Ctrl/⌘+Shift+F opens project search in the sidebar, with literal or regular-expression queries and include/exclude paths; its results stay beside the file you open from them.