--workspace use your default workspace when you leave it out. Set the default with select.
agent
Manage the agents installed in a workspace. Each command uses--workspace if you pass it, and your default workspace otherwise.
agent add
Install an agent in a workspace. By default, the installed agent updates automatically.agent list
List the agents installed in a workspace.agent remove
Remove an agent from a workspace.agent set-default
Set the workspace’s default chat agent. The agent must already be installed in the workspace.chat
Start a session with an agent in a workspace. Without--agent, you chat with the Guild assistant.
To chat with the agent you’re currently developing, use
guild agent chat from inside the agent directory.
clear
Remove the default workspace setting from configuration.- In an agent directory (contains
guild.json): removesworkspace_idfromguild.jsonand prints✓ Cleared workspace setting for this agent. - Outside an agent directory: removes
default_workspaceanddefault_workspace_namefrom~/.guild/config.jsonand prints✓ Default workspace cleared.
No default workspace was set. to stderr and exits successfully. It isn’t an error.
Exit codes: 0 on success or no-op; 1 on filesystem error only.
context
Manage a workspace’s context versions. You edit context as a draft, then publish it.context edit
Open the workspace context in your editor and save the result as a new draft version. By default, you start from the published version. The CLI uses$EDITOR, then $VISUAL, then $GIT_EDITOR, and fails if none is set.
publish command to run next.
context get
Show a context version.context list
List a workspace’s context versions.context publish
Publish a draft context version.create
Create a new workspace.current
Show the current default workspace and where it’s set:guild.json in the current agent directory, or ~/.guild/config.json.
export
Export a workspace’s configuration to a JSON file. The export includes installed agents, time and webhook triggers, and the published context.get
Show a workspace’s details.import
Create a new workspace from a file made byexport. The CLI installs the exported agents, recreates time triggers, and creates the context, publishing it if it was published in the export.
--yes.
list
List the workspaces you can access, across every organization you belong to.member
Restrict a workspace to an allow list of organization members. When restriction is on, only listed members and organization admins can access the workspace. Each command uses--workspace if you pass it, and your default workspace otherwise.
To add or remove members, restriction must be on. Turn it on with member restrict --on.
member add
Add members to the workspace’s allow list. Each member must exactly match one eligible organization member by username, full name, or user ID.member list
List the members on the workspace’s allow list.member remove
Remove members from the workspace’s allow list. Each member must exactly match one listed member.member restrict
Turn member restriction on or off. Pass exactly one of--on or --off.
member search
Search the organization members who are eligible for workspace access.select
Set the default workspace. In an agent directory (containsguild.json), it sets workspace_id in guild.json. Otherwise, it sets the default in ~/.guild/config.json.
After a successful global workspace selection,
guild workspace select prints to stderr: To clear the default, run: guild workspace clear. Pass --quiet to suppress it.variable
Manage workspace variables: plain configuration values, not secrets. Each command uses--workspace if you pass it, and your default workspace otherwise.
Keys must start with an uppercase letter and contain only uppercase letters, numbers, and underscores, up to 64 characters. Values can be up to 4096 characters.
variable delete
Delete a workspace variable.variable get
Print a workspace variable’s value.variable list
List the variables set in a workspace.variable set
Set a workspace variable. The CLI splits the assignment on the first=, so the value can contain =.