You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -157,37 +157,6 @@ OpenHands automatically exports a `GITLAB_TOKEN` to the shell environment if pro
157
157
158
158
</AccordionGroup>
159
159
160
-
161
-
#### Secrets Management
162
-
163
-
OpenHands provides a secrets manager that allows you to securely store and manage sensitive information that can be accessed by the agent during runtime, such as API keys. These secrets are automatically exported as environment variables in the agent's runtime environment.
164
-
165
-
1.**Accessing the Secrets Manager**:
166
-
- In the Settings page, navigate to the `Secrets` tab.
167
-
- You'll see a list of all your existing custom secrets (if any).
168
-
169
-
2.**Adding a New Secret**:
170
-
- Click the `Add New Secret` button.
171
-
- Fill in the following fields:
172
-
-**Name**: A unique identifier for your secret (e.g., `AWS_ACCESS_KEY`). This will be the environment variable name.
173
-
-**Value**: The sensitive information you want to store.
174
-
-**Description** (optional): A brief description of what the secret is used for, which is also provided to the agent.
175
-
- Click `Add Secret` to save.
176
-
177
-
3.**Editing a Secret**:
178
-
- Click the `Edit` button next to the secret you want to modify.
179
-
- You can update the name and description of the secret.
180
-
- Note: For security reasons, you cannot view or edit the value of an existing secret. If you need to change the value, delete the secret and create a new one.
181
-
182
-
4.**Deleting a Secret**:
183
-
- Click the `Delete` button next to the secret you want to remove.
184
-
- Confirm the deletion when prompted.
185
-
186
-
5.**Using Secrets in the Agent**:
187
-
- All custom secrets are automatically exported as environment variables in the agent's runtime environment.
188
-
- You can access them in your code using standard environment variable access methods (e.g., `os.environ['SECRET_NAME']` in Python).
189
-
- Example: If you create a secret named `OPENAI_API_KEY`, you can access it in your code as `process.env.OPENAI_API_KEY` in JavaScript or `os.environ['OPENAI_API_KEY']` in Python.
190
-
191
160
#### Advanced Settings
192
161
193
162
The `Advanced` settings allows configuration of additional LLM settings. Inside the Settings page, under the `LLM` tab,
@@ -208,11 +177,11 @@ section of the documentation.
208
177
The status indicator located in the bottom left of the screen will cycle through a number of states as a new conversation
209
178
is loaded. Typically these include:
210
179
211
-
*`Disconnected` : The frontend is not connected to any conversation
180
+
*`Disconnected` : The frontend is not connected to any conversation.
212
181
*`Connecting` : The frontend is connecting a websocket to a conversation.
213
182
*`Building Runtime...` : The server is building a runtime. This is typically in development mode only while building a docker image.
214
183
*`Starting Runtime...` : The server is starting a new runtime instance - probably a new docker container or remote runtime.
215
-
*`Initializing Agent...` : The server is starting the agent loop. (This step does not appear at present with Nested runtimes)
184
+
*`Initializing Agent...` : The server is starting the agent loop (This step does not appear at present with Nested runtimes).
216
185
*`Setting up workspace...` : Usually this means a `git clone ...` operation.
217
186
*`Setting up git hooks` : Setting up the git pre commit hooks for the workspace.
0 commit comments