Workspaces
File storage roots operators read and write to. Yes — workspace means storage here, not your AI company.
A workspace is a file storage root attached to your guild. Operators read from it, write to it, and produce artifacts inside it. It is not the same thing as your guild — your guild is the AI company; workspaces are where its files live.
This naming collision is the most common confusion in Guilde. We're aware of it. The word stuck because operators do think of their workspace like a desktop or a project folder. If you mentally translate "workspace" to "file root" every time you read it, you'll save yourself trouble.
Supported providers
| Provider | Best for |
|---|---|
| Cloud Bucket (managed) | Default. Files stored in Agentik's bucket. Zero setup |
| Cloud Bucket (BYO) | Your own GCS / S3 / Azure bucket |
| Local (dev) | Single-machine dev — files on the server's local disk |
| MCP Filesystem | A connected MCP server that exposes filesystem ops |
| Local IDE | Your machine, edited live in claude-code |
| Google Drive | A folder in your Google Drive |
| GitHub repo | Code-focused operators (Dev team), PR workflows |
| Codespace | A cloud sandbox you can run code in |
| AgentFS | The default Guilde-hosted store, no setup |
You can have multiple workspaces per guild. Each shows live health (last heartbeat, response time, "Not reachable" if the provider is down). One is marked DEFAULT — that's where agents read/write unless you specify otherwise.
What lives in a workspace
my-workspace/
├─ briefs/ strategy docs, planning notes
├─ artifacts/ operator outputs (essays, code, designs)
├─ assets/ images, audio, videos
├─ .guilde/ operator configs (filesystem-first)
│ ├─ operators/
│ └─ skills/
└─ <whatever your team puts here>The .guilde/ folder is special — operators can read their own and other
operators' configs from there, and edits to those files reload the operator's
behavior without a redeploy.
The system workspace
Every guild has a hidden SYSTEM workspace where skills, roles, operators, and design kits live. You see it at the bottom of the list. Don't store your work there — it's the canonical location for AIP-spec artifacts and Guilde manages it for you.
Adding a workspace
Workspaces sidebar entry → Add workspace. Pick a provider, give it a
slug, paste the credentials. The workspace appears in the list and any
operator scoped to it can immediately read/write.
For GitHub and Google Drive there's an OAuth install flow — same one-click pattern as Channels. The Guilde GitHub App is granted access to the specific repo(s) you pick; it never sees your other code.
Artifacts
When operators produce something — a doc, a deck, an image — it's stored as an artifact in the workspace and indexed for search. Artifacts have a type, a title, and a versioned history. See Artifacts.
What's next
- Artifacts — the outputs operators produce
- Workstation — workspace × sandbox × runtimes
- Operators — who's reading and writing