Settings

The Settings tab is the setup hub for the Cloud Agents workspace. Unlike repository settings, which are per-repository, this area manages workspace-level surfaces such as integrations and custom-agent management.

Settings Navigation

The settings page includes a left-side settings navigator with a search field and sections such as:

• Overview
• Integrations
• Agents
• Approvals

Use the search field when the workspace has enough configuration depth that browsing by eye becomes inefficient.

Overview

The Overview pane gives a consolidated view of the workspace setup state. In the current interface it surfaces at least three categories:

This page is the fastest way to answer: is the workspace actually ready to operate?

Integrations

GitHub

GitHub is the primary repository connection for Cloud Agents. The settings overview shows connected repositories and may also display badges reflecting enabled automation capabilities on a per-repository basis.

Use Manage Repositories to change which repositories Cloud Agents can see.

Do not duplicate the GitHub OAuth flow here. Use GitHub Integration for the full authorization process and troubleshooting.

Slack

Slack appears in settings as a messaging and command-entry integration. When connected, it supports direct run initiation from Slack-driven workflows. When not connected, the interface shows the disconnected state and a Connect Slack action.

Because channel availability can vary by rollout, use the live settings page as the source of truth for which channels are enabled in your workspace.

Agents

The Agents area inside settings is where you manage custom-agent inventory.

Expect to use it for:

• creating a new custom agent
• enabling or disabling an agent
• editing an agent's instructions or model selection
• checking how many custom-agent slots are currently used

The presence of built-in agents in the overview helps operators see what is available without needing to edit them constantly.

For full design guidance, see Agents.

Approvals

The Approvals area exists to support the product's governance model. Exact configuration options can vary, but this is the settings surface to check when approval behavior needs to be aligned with how the team operates.

Use it when:

• approval flow is too loose or too strict
• you need to understand which actions stop for human review
• repository and run policy no longer match team ownership structure

For the operator workflow after a run pauses, see Approvals.

Recommended Setup Order

1. Confirm GitHub is connected.
2. Confirm channel integrations only if your team will actually dispatch from them.
3. Start with the built-in agents.
4. Add one or two custom agents only after a clear repeated use case emerges.
5. Revisit approval behavior after the first few repositories are active.

Related