JWT Token not sent as Authorization header in VoltOps LLM Observability dashboard

[wayneg123]

Describe the bug:

When using the VoltOps LLM Observability dashboard at https://voltagent.dev/voltops-llm-observability-docs/, the JWT token configured in the "Context" tab is not being sent as an Authorization header in HTTP requests. Instead, the token is included in the request payload under options.context.jwtToken, which prevents proper authentication with the agent endpoint.

Steps To Reproduce:

1. Navigate to https://voltagent.dev/voltops-llm-observability-docs/
2. Go to the "Context" tab in the dashboard
3. Add a JWT token (e.g., "ABC") in the "JWT Token (Optional)" field
4. Send a message to the agent (e.g., "Hi")
5. Monitor network requests in browser developer tools
6. Observe that the Authorization header is missing from the request

Expected behavior:

The JWT token should be sent as an Authorization header in the format: Authorization: Bearer ABC

Actual behavior:
The JWT token is sent in the request payload instead:

{
  "input": [...],
  "options": {
    "conversationId": "wv3gsjaf5i",
    "temperature": 0.7,
    "maxTokens": 4000,
    "maxSteps": 10,
    "context": {
      "jwtToken": "ABC"
    }
  }
}

Request headers observed:
POST /agents/my-voltagent-app/chat HTTP/1.1
Accept: /
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9,zh-TW;q=0.8,zh-CN;q=0.7,zh;q=0.6
Connection: keep-alive
Content-Length: 209
Content-Type: application/json
DNT: 1
Host: localhost:3141
Origin: https://console.voltagent.dev
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36

This appears to be a VoltOps-specific issue (not related to VoltAgent), but since I’m not sure where to officially report it, I’m submitting it here for visibility.

[wayneg123]

By the way, love this project! ❤

[omeraplak]

Thank you <3

[omeraplak]

Hey @wayneg123 ,
Thank you! I've fixed this issue