Skip to content
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

TYPE Action Execution Logic Optimization #41

Open
Hua-Wen opened this issue Feb 19, 2025 · 1 comment
Open

TYPE Action Execution Logic Optimization #41

Hua-Wen opened this issue Feb 19, 2025 · 1 comment
Assignees

Comments

@Hua-Wen
Copy link

Hua-Wen commented Feb 19, 2025

Feature request / 功能建议

At present, in many scenarios, "input box text input" is divided into "CLICK" first, and then "TYPE".
It's a human input habit.
However, in fact, this is not necessary for computers. The coordinates output by "CLICK" and "TYPE" are the same. If the operation logic is put into Type Action to realize the theory, there is no problem, and the time and coast of a model call can be saved.

Motivation / 动机

Improve Action Execution Efficiency

Your contribution / 您的贡献

If necessary, I can prepare the training data set under simple guidance.

@sixsixcoder
Copy link
Collaborator

Because cogagent simulates human interface operations, it needs to locate the input box first before calling TYPE for input, so it needs to be executed step by step. But if you have a better solution, we'd like to hear it.

@sixsixcoder sixsixcoder self-assigned this Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants