Skip to content

fix: incorrect typing speed unit of computer type tool#272

Open
philipph-askui wants to merge 1 commit intomainfrom
fix/chars-per-minute
Open

fix: incorrect typing speed unit of computer type tool#272
philipph-askui wants to merge 1 commit intomainfrom
fix/chars-per-minute

Conversation

@philipph-askui
Copy link
Copy Markdown
Contributor

the description stated that typing speed was character per minute, in fact, the parameter controls the typing speed in characters per second.

@philipph-askui philipph-askui changed the title fix: correct typing speed unit of computer type tool fix: incorrect typing speed unit of computer type tool May 4, 2026
"description": (
"The speed of typing in characters per minute."
"The speed of typing in characters per second."
" Defaults to 50"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@programminx-askui should we increase the default value?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice, if we could set the default as a a config value so that it can be easily set per project. For example when operating a VNC window, a too high typing speed will lead to some characters being not typed....

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the agent can modify the value, even changing the default doesn’t guarantee it will be used.
btw, are you sure that the value is per second ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The agent usually does not modify the value unless it is specifically prompted to do so. Also, it would make more sense to set it once for these specific scenarios so that the agent does not need to do it for every type call. However, this is a low priority issue in my opinion so I would not add it to this PR for now.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the feeling something is off. And either the typeing speed in the API, the gloabl config is not working or the Agent is randomly changing the speed which leads in chars which are not recognized by the application.

We need first to do a proper testing, but I woul do it in another bug ticket.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems to work as expected on mac, so this might be a windows issue?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyways, the descriptions should be changed from minutes to seconds (as done in this PR) in order to align with the definition of the API.

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

Successfully merging this pull request may close these issues.

3 participants