Workspaces

A workspace is your team’s shared environment. It connects to a GitHub repository and holds the agents your team has installed.

​

Creating a workspace

1. Go to app.guild.ai and open your organization
2. Open the workspace selector at the top of the left sidebar
3. Click New workspace and give it a name

​

What’s inside a workspace

Each workspace contains:

• Agents — installed from the Agent Hub or published by your team
• Sessions — conversations with agents
• Triggers — automated agent execution via webhooks or schedules
• Context — background knowledge shared with all agents in the workspace
• Variables — workspace-level configuration that agents read at runtime

​

Connecting a repository

Link a GitHub repository to your workspace so agents can access your code. Go to Settings in your workspace and connect a repository under GitHub.

​

Spend budget

A spend budget caps monthly LLM spend. Budgets are opt-in — with no budget set, spend has no ceiling. Set one from the Spend budget section in the workspace’s Settings. Budgets are admin-only. Only an admin or owner of the account can set, change, or remove one, and non-admins cannot read them either: the section shows only “Spend budgets are managed by org admins”, without revealing whether a budget exists. Once a budget is set, Guild acts as spend accumulates within the cycle: Each notification fires at most once per budget per cycle. The cycle is the calendar month, so a budget resets on the 1st. An agent can carry its own budget in addition to the workspace’s — see Agents. Track spend against a budget from the usage dashboard. Budgets also apply at the user scope. An admin can set a monthly budget for the session’s accountable user — the person who initiated the chat or agent test, or who created the firing trigger — to enforce a per-user spending limit, and spend accrues per user per cycle. Sessions that cannot be attributed to a human — API-key-initiated chats, API triggers, and legacy creatorless triggers — carry no user scope, so their user budgets fail open and do not block calls.

​

Find workspaces with the command palette

Open the command palette with Cmd+K / Ctrl+K and search the workspaces scope by name or owner. Your workspaces are also listed when you open the palette.

​

Archived workspaces

Archiving takes a workspace out of use without deleting it. Archiving also deactivates every trigger in the workspace, so scheduled and webhook agents stop firing — this is the part that outlives the archive, since unarchiving does not reactivate them. While a workspace is archived, every page in it is replaced by a Workspace Archived notice showing when it was archived and by whom. The URL you requested does not change — agents, sessions, triggers, context, and settings are simply unreachable until the workspace is restored. The notice includes an Unarchive Workspace button, which asks you to confirm. Restoring the workspace renders the page you originally asked for, in place.

​

Archiving metadata

Workspaces include two optional fields that record archiving history.

​

Next steps