> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openhands.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Settings

> Configure application-level settings for OpenHands.

## Overview

The Application settings allows you to customize various application-level behaviors in OpenHands, including
language preferences, notification settings, custom Git author configuration and more.

## Supported Languages

The Agent Canvas interface is available in the following languages. Choose one from the language selector in `Settings > Application`.

| Language | Code |
| - | - |
| English | `en` |
| 日本語 | `ja` |
| 简体中文 | `zh-CN` |
| 繁體中文 | `zh-TW` |
| 한국어 | `ko-KR` |
| Norsk | `no` |
| Arabic | `ar` |
| Deutsch | `de` |
| Français | `fr` |
| Italiano | `it` |
| Português | `pt` |
| Español | `es` |
| Català | `ca` |
| Türkçe | `tr` |
| Українська | `uk` |
| Bahasa Indonesia | `id` |

The selected language persists across sessions.

## Setting Maximum Budget Per Conversation

To limit spending, go to `Settings > Application` and set a maximum budget per conversation (in USD)
in the `Maximum Budget Per Conversation` field. OpenHands will stop the conversation once the budget is reached, but
you can choose to continue the conversation with a prompt.

## Git Author Settings

OpenHands provides the ability to customize the Git author information used when making commits and creating
pull requests on your behalf.

By default, OpenHands uses the following Git author information for all commits and pull requests:

* **Username**: `openhands`
* **Email**: `openhands@all-hands.dev`

To override the defaults:

1. Navigate to the `Settings > Application` page.
2. Under the `Git Settings` section, enter your preferred `Git Username` and `Git Email`.
3. Click `Save Changes`

> [!NOTE]
>
> When you configure a custom Git author, OpenHands will use your specified username and email as the primary author
> for commits and pull requests. OpenHands will remain as a co-author.

## Getting Started Checklist

The sidebar shows a **Getting Started** checklist after first-run onboarding. Toggle `Show getting started checklist` in `Settings > Application` to hide or show it. The setting persists across sessions. On a canvas locked to an OpenHands Cloud host (OpenHands Cloud and OpenHands Enterprise), the checklist is never shown. See [First Time Setup](https://docs.openhands.dev/openhands/usage/agent-canvas/first-time-setup.md#getting-started-checklist) for details.

## Recommended Automations

Home shows a **Recommended automations** discovery rail below the composer. Dismiss the rail from Home with the `X` control on its header, which appears on hover or when you focus it.

To restore or hide the rail from settings, toggle `Show Recommended automations` in `Settings > Application`, next to `Show getting started checklist`. The setting persists across sessions. Dismissing the rail affects only Home; the automations empty-state rail and the onboarding section are unchanged.

## Sandbox Grouping Strategy

The `Sandbox Grouping Strategy` setting controls where OpenHands places new
conversations started with your application settings.

| Setting | Placement Behavior |
| - | - |
| No grouping | Start a new sandbox for each conversation |
| Group by newest | Use the newest available sandbox |
| Least recently used | Use the least recently used available sandbox |
| Fewest conversations | Use the available sandbox with the fewest conversations |
| Add to any | Use the first available sandbox |

To change the setting:

1. Navigate to `Settings > Application`.
2. Select a value under `Sandbox Grouping Strategy`.
3. Click `Save Changes`.

Grouping can reduce sandbox startup time and sandbox count. Conversations in
one sandbox share its filesystem, credentials, compute limits, and failure
domain. The setting does not check whether a sandbox has enough CPU, memory, or
disk for another conversation.

For API placement and sandbox lifecycle options, see
[Conversations And Sandboxes](https://docs.openhands.dev/enterprise/conversations-and-sandboxes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.