deco Studio

Library

A Drive-like browser for your organization's shared filesystem

What is the Library?

Library is a file browser for your organization’s shared filesystem — reachable from the top of the left sidebar. It’s the human-facing window onto the same files your agents read and write: anything an agent saves to the org filesystem shows up here, and anything you drop here is available to your agents.

Think of it as your organization’s shared drive, with a few well-known areas.

Volumes

The Library is organized into volumes:

  • Home — the org’s shared, free-form home folder. This is where agents record durable knowledge and where you keep context you want every agent to be able to reach. Editable by everyone.
  • Uploads — files attached to conversations land here automatically. When you drop a file into a chat, it’s available to the agent without a copy step.
  • Outputs — the shared output folder for agent runs. Files an agent produces during a run surface here.
  • Public sets — curated, read-only skill sets synced from versioned repositories, exposed for agents to reference.

A Recently added feed across all volumes sits at the top so you can jump back to whatever you (or your agents) touched last. Navigate with breadcrumbs; the current location is reflected in the page URL, so you can link a teammate straight to a folder.

You can drag and drop files directly into any editable volume to upload them.

Brands

The Library has first-class support for org brands — a structured identity folder your agents and the slides skill use to produce on-brand output.

A brand lives at org/home/brands/<name>/ and contains four files:

File Purpose
tokens.css CSS variables for colors, typography, spacing, radius, and shadow
brand.md Written brand guidelines: voice, tone, and visual identity notes
logo Logo file (SVG, PNG, or similar)
slides-theme.html A sample deck that doubles as the generation shell for the slides skill

Creating and editing a brand

Brands appear as cards directly in the Library. Click a brand card to open the side-panel editor, which lets you:

  • Edit color ramps (primary, secondary, neutrals) with a live band preview
  • Adjust typography, spacing, radius, and shadow values
  • Write or refine the brand’s voice and tone guidelines
  • Preview the brand applied to a sample deck and UI components in real time

To create a brand from scratch, ask any agent: “Create a brand for [name]” — agents with access to the core/brand skill will scaffold the full folder structure and populate it with sensible defaults.

The slides-theme.html file in a brand folder acts as both the generation shell and an editable sample deck. Modifying it directly changes the starting point for every deck the slides skill generates under that brand.

Sharing

Files and folders in the Home volume can be shared outside your organization. Each node has a share mode, set from its context menu or the share icon on its card:

Mode Who can access
Org only Organization members only (default)
Public Anyone with the link — no sign-in required
Password Anyone with the link who enters the correct password

A badge on the card reflects the current share mode. For password-protected nodes, the shared link opens an interstitial password form before serving content; one successful unlock covers the node and its entire subtree (for folders) for the browser session.

A password is set at the folder level and covers everything inside it. Files inside a password-protected folder inherit the parent’s password — you cannot override it with a different password on a child node.

Files that inherit sharing from a parent show a read-only “shared via a parent folder” indicator instead of the share controls. Change the parent’s share mode to affect them.

How it maps to the sandbox

The Library and the agent sandbox are two views of the same filesystem. Inside a sandbox these volumes are mounted under org/ :

Library volume Sandbox path
Home org/home/
Uploads org/upload
Outputs org/output
Public sets org/public/<set>

Files written to the Home folder and to Outputs sync to your organization’s cloud storage and are visible to every member and agent. External changes appear inside a running sandbox within about a second.

For how agents use these folders at runtime — recording durable knowledge, reading chat attachments, writing run output — see Decopilot → Overview.

Found an error or want to improve this page?

Edit this page