Skip to content

[Bug Report]: Update element index validation to properly handle zero index in browser tools #566

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 of 19 tasks
falconlee236 opened this issue May 3, 2025 · 0 comments · May be fixed by #567
Open
5 of 19 tasks
Labels
Agent TARS Bug Something isn't working

Comments

@falconlee236
Copy link

Version

UI-TARS-v0.1.0

Issue Type

  • Select a issue type 👇
  • Agent Core
  • MCP
  • Search
  • Browser
  • Setting
  • UI
  • Other (please specify in description)

Model Provider

  • Select a model provider 👇
  • Anthropic
  • OpenAI
  • Azure OpenAI
  • Other (please specify in description)

Search Provider

  • Select a model provider 👇
  • Local Browser Search
  • Travily
  • Duckduckgo
  • SearXNG
  • Other (please specify in description)

Problem Description

Expected

When agent perform browser-click method in browser-use mcp server,
Agent found highlighted DOM Element becoming index started 0,
but current code check only args.index is undefined of non zero index.
this if statement cannot pass only one clickable element such as this situation

Image

Actual

execute browser-click method whenever the clickable element has index 0.

Currently ChatGPT calls DOM elements about index 0. so this project must handle index 0 DOM elements.

Image

Error Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agent TARS Bug Something isn't working
Projects
None yet
1 participant