Docs / Workspaces and windows

Workspaces and windows

What is a workspace?

A workspace is the folder you open in Bedrock. It contains all your markdown docs, and a hidden .bedrock/ sidecar that holds version history, saved bundles, and product data. You can open any folder — a repo root, a docs/ subfolder, a dedicated .ai/ context directory, or anything else.

Switching projects

Click the project switcher at the top of the global rail to open a different folder in the current window. If you have unsaved changes, Bedrock asks before switching.

Recent workspaces appear on the welcome screen — click any entry to jump back in, or click the small × to remove it from the list.

Opening a second project (new window)

To work on two projects side by side:

  • Press ⇧⌘N, or
  • click the new-window button (⧉) next to the project switcher, or
  • run New window from the command palette (⌘K).

A new window opens on the welcome screen so you can pick a different folder. Each window is completely independent — its own library, editor, prompt board, and product data. Global settings (theme, integrations, recent folders) are shared across all windows.

Example: keep your backend workspace in one window and your documentation workspace in another. Use Mission Control or the app switcher to move between them.

How the project name is shown

The top bar shows a project name derived from the folder you opened:

  • my-app/ → project name is my-app
  • my-app/docs/ → project name is my-app with a small docs tag (Bedrock recognises docs, doc, .ai, context, notes, .github as docs-like subfolders and shows the parent name instead)

The native window title updates to match, so you can tell windows apart in Mission Control.

The .bedrock/ sidecar

Bedrock keeps its own data in a hidden .bedrock/ folder inside the workspace:

Path Contents
.bedrock/history/ Version snapshots for every doc
.bedrock/bundles.json Saved Context Composer selections
.bedrock/products.json Product definitions
.bedrock/releases.json Release data
.bedrock/features.json Feature board data
.bedrock/tasks.json Task list data
.bedrock/inbox.json Inbox captures
.bedrock/prompts.json Prompt card data
.bedrock/projectLink.json Linked project directory path
.bedrock/.gitignore Auto-generated to keep .bedrock/ out of git

This folder never appears in the Library and is safe to commit or gitignore. The .gitignore inside it is created automatically.

Get release notes

An email when a new build ships or a major feature lands. A few times a quarter — never your inbox sold.

You're on the list — watch for a confirmation email.