Ctrlk
Log in|Playground
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring Settings

How to configure Agent Mode access, LLM providers, instructions, and budgets for your workspace

Workspace administrators control Agent Mode availability, organization-wide instructions, and budget settings from the Settings page.

Accessing AI Settings

Navigate to Settings > AI & Agents in the groundcover UI. The page is split into three sections:

  • Management: enable or disable Agent Mode and choose an LLM provider per backend

  • Org Instructions: set backend-wide guidance the Agent follows for everyone

  • Cost Control: set monthly spending limits at the organization and per-user level

Admin role required. Only users with the Admin role can view and modify AI settings. If you don't see the AI & Agents option in the Settings sidebar, contact your workspace administrator.

Management

The Management section controls whether Agent Mode is available and which LLM provider it uses for each backend. Expand a backend to view its settings.

When enabled:

  • The Agent panel appears in the sidebar

  • Users can open the Agent with Cmd/Ctrl + Shift + A

  • All AI-related UI elements are visible

When disabled:

  • The Agent panel and all AI-related UI elements are hidden

  • Keyboard shortcuts for the Agent are inactive

This setting is per backend. You can enable Agent Mode for some backends while keeping it disabled for others, and each enabled backend can use a different LLM provider.

Choose an LLM provider

Provider
When to use it

Native Cloud Provider

Use the LLM service included with your deployment, such as AWS Bedrock, Google Cloud Vertex AI, or Microsoft Foundry. See Requirements & Compatibility.

Anthropic Key

Send requests directly to Anthropic and bill usage to your Anthropic account.

Custom Anthropic Domain

Send requests to an Anthropic-compatible proxy or gateway, such as LiteLLM, Bifrost, or another service that implements the Anthropic Messages API.

Anthropic API key

You can bring your own Anthropic API key and configure Agent Mode to send inference requests directly to Anthropic. The provider selection and key are configured separately for each backend.

To configure an Anthropic API key:

  1. Go to Settings > AI & Agents > Management.

  2. Find the backend you want to configure and make sure AI enabled is turned on.

  3. Expand the backend settings.

  4. Under Choose your LLM Provider, select Anthropic Key.

  5. Enter your Anthropic API key.

  6. Select Save.

groundcover validates the key before activating it. A valid key takes effect without restarting the backend. If validation fails, the existing provider configuration remains active.

After the key is saved, the API key field displays a masked value. To rotate the key, expand the backend settings, select Edit next to the API key field, enter the replacement key, and select Save.

To return to the LLM provider configured for your deployment, select Native Cloud Provider and then select Save. A native provider must already be configured for the backend.

See Requirements & Compatibility for deployment support and Privacy & Security for data handling and key storage details.

Configure a custom Anthropic domain

Use Custom Anthropic Domain to route Claude traffic through an internal gateway, centralized model proxy, or another Anthropic-compatible endpoint.

Before you begin, make sure the proxy:

  • Is accessible from your groundcover deployment

  • Implements the Anthropic Messages API, including streaming responses

  • Supports API key authentication

To configure the endpoint:

  1. Go to Settings > AI & Agents > Management.

  2. Expand the backend you want to configure.

  3. Select Custom Anthropic Domain under Choose your LLM Provider.

  4. Enter the proxy's Anthropic base URL in Endpoint URL, including any required path.

    • The /v1/messages path is added automatically.

    • Use HTTPS for external endpoints. Use HTTP only for internal endpoints protected by authenticated encryption, such as a TLS service mesh.

    • Use a URL without query parameters or fragments.

  5. Enter the API key accepted by the proxy.

  6. Click Save.

For example, depending on how your proxy is exposed, the base URL could be:

When you save, groundcover makes a model request to validate the endpoint, API key, and model access before applying the change. If validation fails, the existing provider remains active. Successful validation confirms access only at save time. Later availability depends on the proxy and its upstream provider.

Org Instructions

The Org Instructions section lets admins set guidance the Agent follows in Agent Mode for everyone in the selected backend. Use Org Instructions for broad defaults that should apply across the team, such as:

  • Preferred terminology and service names

  • Default response structure

  • Systems or namespaces the Agent should prioritize

  • Organization-wide investigation or escalation expectations

Org Instructions are included alongside each user's Personal Instructions and any active Skills. Keep Org Instructions broad and stable; use Organizational Skills for reusable runbooks or workflows that should activate only for specific prompts.

To update Org Instructions, edit the text and click Save. To remove them, clear the editor and save the empty value.

Cost Control

The Cost Control section lets admins set monthly spending limits. See Cost Management for full details on configuring organization budgets, default per-user budgets, and per-user overrides.

Related

  • Getting Started - Configure Personal Instructions for your own Agent conversations

  • Skills - Create personal or Organizational Skills for reusable Agent guidance

  • Cost Management - Set monthly spending limits at the organization and per-user level

  • Privacy & Security - Data handling and access control details

Last updated