Spaces:
Build error
Build error
| --- | |
| title: GUI Mode | |
| description: OpenHands provides a Graphical User Interface (GUI) mode for interacting with the AI assistant. | |
| --- | |
| ## Installation and Setup | |
| 1. Follow the installation instructions to install OpenHands. | |
| 2. After running the command, access OpenHands at [http://localhost:3000](http://localhost:3000). | |
| ## Interacting with the GUI | |
| ### Initial Setup | |
| 1. Upon first launch, you'll see a settings popup. | |
| 2. Select an `LLM Provider` and `LLM Model` from the dropdown menus. If the required model does not exist in the list, | |
| select `see advanced settings`. Then toggle `Advanced` options and enter it with the correct prefix in the | |
| `Custom Model` text box. | |
| 3. Enter the corresponding `API Key` for your chosen provider. | |
| 4. Click `Save Changes` to apply the settings. | |
| ### Version Control Tokens | |
| OpenHands supports multiple version control providers. You can configure tokens for multiple providers simultaneously. | |
| #### GitHub Token Setup | |
| OpenHands automatically exports a `GITHUB_TOKEN` to the shell environment if provided: | |
| <details> | |
| <summary>Setting Up a GitHub Token</summary> | |
| 1. **Generate a Personal Access Token (PAT)**: | |
| - On GitHub, go to Settings > Developer Settings > Personal Access Tokens > Tokens (classic). | |
| - **New token (classic)** | |
| - Required scopes: | |
| - `repo` (Full control of private repositories) | |
| - **Fine-Grained Tokens** | |
| - All Repositories (You can select specific repositories, but this will impact what returns in repo search) | |
| - Minimal Permissions ( Select `Meta Data = Read-only` read for search, `Pull Requests = Read and Write` and `Content = Read and Write` for branch creation) | |
| 2. **Enter Token in OpenHands**: | |
| - Click the Settings button (gear icon). | |
| - Navigate to the `Git` tab. | |
| - Paste your token in the `GitHub Token` field. | |
| - Click `Save Changes` to apply the changes. | |
| </details> | |
| <details> | |
| <summary>Organizational Token Policies</summary> | |
| If you're working with organizational repositories, additional setup may be required: | |
| 1. **Check Organization Requirements**: | |
| - Organization admins may enforce specific token policies. | |
| - Some organizations require tokens to be created with SSO enabled. | |
| - Review your organization's [token policy settings](https://docs.github.com/en/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization). | |
| 2. **Verify Organization Access**: | |
| - Go to your token settings on GitHub. | |
| - Look for the organization under `Organization access`. | |
| - If required, click `Enable SSO` next to your organization. | |
| - Complete the SSO authorization process. | |
| </details> | |
| <details> | |
| <summary>Troubleshooting</summary> | |
| Common issues and solutions: | |
| - **Token Not Recognized**: | |
| - Ensure the token is properly saved in settings. | |
| - Check that the token hasn't expired. | |
| - Verify the token has the required scopes. | |
| - Try regenerating the token. | |
| - **Organization Access Denied**: | |
| - Check if SSO is required but not enabled. | |
| - Verify organization membership. | |
| - Contact organization admin if token policies are blocking access. | |
| - **Verifying Token Works**: | |
| - The app will show a green checkmark if the token is valid. | |
| - Try accessing a repository to confirm permissions. | |
| - Check the browser console for any error messages. | |
| </details> | |
| #### GitLab Token Setup | |
| OpenHands automatically exports a `GITLAB_TOKEN` to the shell environment if provided: | |
| <details> | |
| <summary>Setting Up a GitLab Token</summary> | |
| 1. **Generate a Personal Access Token (PAT)**: | |
| - On GitLab, go to User Settings > Access Tokens. | |
| - Create a new token with the following scopes: | |
| - `api` (API access) | |
| - `read_user` (Read user information) | |
| - `read_repository` (Read repository) | |
| - `write_repository` (Write repository) | |
| - Set an expiration date or leave it blank for a non-expiring token. | |
| 2. **Enter Token in OpenHands**: | |
| - Click the Settings button (gear icon). | |
| - Navigate to the `Git` tab. | |
| - Paste your token in the `GitLab Token` field. | |
| - Click `Save Changes` to apply the changes. | |
| </details> | |
| <details> | |
| <summary>Troubleshooting</summary> | |
| Common issues and solutions: | |
| - **Token Not Recognized**: | |
| - Ensure the token is properly saved in settings. | |
| - Check that the token hasn't expired. | |
| - Verify the token has the required scopes. | |
| - **Access Denied**: | |
| - Verify project access permissions. | |
| - Check if the token has the necessary scopes. | |
| - For group/organization repositories, ensure you have proper access. | |
| </details> | |
| ### Advanced Settings | |
| 1. Inside the Settings page, under the `LLM` tab, toggle `Advanced` options to access additional settings. | |
| 2. Use the `Custom Model` text box to manually enter a model if it's not in the list. | |
| 3. Specify a `Base URL` if required by your LLM provider. | |
| ### Interacting with the AI | |
| 1. Type your prompt in the input box. | |
| 2. Click the send button or press Enter to submit your message. | |
| 3. The AI will process your input and provide a response in the chat window. | |
| 4. You can continue the conversation by asking follow-up questions or providing additional information. | |
| ## Tips for Effective Use | |
| - Be specific in your requests to get the most accurate and helpful responses, as described in the [prompting best practices](../prompting/prompting-best-practices). | |
| - Use one of the recommended models, as described in the [LLMs section](usage/llms/llms.md). | |
| Remember, the GUI mode of OpenHands is designed to make your interaction with the AI assistant as smooth and intuitive | |
| as possible. Don't hesitate to explore its features to maximize your productivity. | |