Connected folders

A connected folder links an external directory of markdown — a code repository, a project wiki, a shared docs folder — to a product in Bedrock. Bedrock imports those docs so you can edit them with the full editor, then mirrors your changes back to the source when you’re ready. It’s how you bring existing documentation under Bedrock’s roof without moving it.

Connecting a folder

1. Click the product switcher at the top of the rail.
2. Click … next to a product and choose Connected folders.
3. Click Add folder and pick the external directory.
4. Choose a role: - Docs — import and sync markdown docs. - Storage — treat as a read-only reference. - Project — becomes the Claude CLI working directory for this product.
5. Click Connect.

Bedrock imports the folder’s markdown into the product’s docs tree (products/<slug>/<folder-name>/). The original files are left untouched — your Bedrock copy is yours to edit freely.

Syncing changes

A connected folder is two-way, but always on your command — Bedrock never writes to the source automatically:

• Sync back — mirrors your Bedrock edits to the external folder: new and changed files are written, and files you removed in Bedrock are deleted at the source.
• Re-import — pulls the latest from the source, overwriting the Bedrock copy. Use this when the external folder has changed underneath you.

Each connected folder shows its status — up to date, or how many files are ahead (e.g. “3 to push · 1 to delete”) — so you always know which direction work is pending. Click Sync all in the top bar to push all of a product’s connected folders at once.

Connected folder docs in the library

Docs from connected folders appear in the library with a badge showing their origin (the folder name). They behave like any other doc — you can edit, pin, and link them with wikilinks.

Use cases

• Component library docs — connect a shared design system’s docs/ folder. Edit in Bedrock, sync back so the component repo always has the latest.
• Handbook — connect your company handbook repo. Pull updates when policies change; push your edits back when you improve something.
• Project working directory — connect the repo root as a Project role so Claude CLI runs from there when you send a prompt.

What to read next

• Products and the portfolio — connected folders belong to a product.
• The library and files — how docs are organised once imported.
• Privacy and your data — nothing syncs without your action.