-
Notifications
You must be signed in to change notification settings - Fork 0
LLM Configuration
AgentDesk can execute configured OpenAI and Anthropic model nodes in Cloud BYOK mode.
Supported cloud model providers:
- OpenAI Responses
- Anthropic Messages
The UI includes provider/model dropdowns plus editable base URL and model fields.
Cloud BYOK keys are held in browser session state only.
They are not:
- saved to localStorage
- written into replay-session exports
- written into trace bundle ZIP files
- intentionally included in debug payloads
However, prompts and model responses are trace evidence. Do not put secrets into prompts, labels, tool payloads, stdout/stderr, screenshots, or model responses.
Typical flow:
- Pick a workflow with OpenAI model nodes, such as
Local Research Agent. - Open
LLMs. - Select
OpenAI Responses. - Choose a model preset or enter a model ID.
- Paste your API key.
- Click
Use Cloud mode. - Click
Apply to nodesif you want model nodes updated. - Click
Run BYOK cloud.
Typical flow:
- Pick a workflow with Anthropic model nodes, such as
Repo QA Swarm. - Open
LLMs. - Select
Anthropic Messages. - Choose a model preset or enter a model ID.
- Paste your API key.
- Click
Use Cloud mode. - Click
Apply to nodes. - Click
Run BYOK cloud.
Cloud BYOK mode currently calls providers directly from the browser tab.
This can fail because of:
- provider CORS policy
- organization security policy
- browser extension interference
- invalid API key
- unsupported model ID
- network restrictions
Production applications should use a backend proxy or server-side secret boundary. AgentDesk keeps BYOK mode intentionally local and explicit.
When a cloud node runs successfully, AgentDesk may capture:
- prompt text
- model response text
- token usage
- cost estimate
- provider/model metadata
- error payloads if the provider returns one
This is useful for debugging, but it also means model prompts and responses should be treated as evidence, not as private vault contents.