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

cannot run browser tool #228

Closed
ibagur opened this issue Oct 25, 2024 · 1 comment
Closed

cannot run browser tool #228

ibagur opened this issue Oct 25, 2024 · 1 comment
Labels
bug Something isn't working tool

Comments

@ibagur
Copy link

ibagur commented Oct 25, 2024

I have followed the instructions and installed gptme on macos 14.6.1 as per:

pipx install gptme[browser]
gptme '/shell playwright install chromium'

The default model used is claude-3-5-sonnet-20241022 (latest). However when trying to run the example gptme 'find out which is the latest ActivityWatch version from superuserlabs.org', I get the following error:

WARNING:gptme.chat:Failed to read URL http://www....BrowserType.launch: Executable doesn't exist at /Users/inigo/Library/Caches/ms-playwright/chromium-1134/chrome-mac/Chromium.app/Contents/MacOS/Chromium

I checked the directory and apparently Chromium is installed, but there is a discrepancy in the directory path, as the installation is 1140 instead of 1134:

/Users/inigo/Library/Caches/ms-playwright/chromium-1140/...

Any suggestions on how to proceed?

Thanks!

UPDATE: I manually changed the directory name under .../ms-playwright/´from chromium-1140tochromium-1134` and now it's fine. A bit dirty but it worked.

@ErikBjare
Copy link
Owner

ErikBjare commented Oct 27, 2024

Weird.

I get the error whenever updating playwright, but doing a playwright install with the right version of playwright fixes it. I thought gptme '/shell playwright install chromium' would always use the same playwright version as the one in the venv used by gptme, but I guess not?

Side-note: I'm kinda tired of Playwright, as its a bit overkill for most browsing, so I've investigated adding lynx support instead, which is a lot faster, cleaner output, and more lightweight (but less capable): #205

Glad you found a workaround!

@ErikBjare ErikBjare closed this as not planned Won't fix, can't repro, duplicate, stale Oct 29, 2024
@ErikBjare ErikBjare added bug Something isn't working tool labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tool
Projects
None yet
Development

No branches or pull requests

2 participants