pickfit

BrowseLocal AI tools

GLiNER Browser Use

Browser agent that scores page controls with local GLiNER2 and performs actions in Chrome.

Use it

Before you install: known vulnerabilities

pickfit found 42 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • pypi:pillow 12.3.0 Pillow: Heap buffer overflow in _tiffWriteProc when saving TIFF to BytesIO (GHSA-332p-7hrc-92wf, critical, fixed in 13.0.0)
See 9 more

32 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: python>=3.12
  • System packages: Chrome
  • Needs the network
  • Keys or accounts: OpenRouter API key for the default text helper
  1. clone repo

    rm -rf gliner2-ultrafast && git clone https://github.com/sahibzada-allahyar/gliner2-ultrafast.git gliner2-ultrafast
  2. uv sync frozen install

    cd gliner2-ultrafast && uv sync --frozen
Where the README and reality differ
  • README: gliner CLI with --help
    What worked: uv run gliner starts the inspector server on 127.0.0.1:8766 (must run in background); it has no --help output

Check that it works

cd gliner2-ultrafast && uv run browser-harness --help

The output should contain “browser-harness --doctor”.

First thing to try

cd gliner2-ultrafast && timeout 30 uv run browser-harness --doctor

Run uv run browser-harness --doctor from the project folder to check that your setup is ready.

What it does

  • Automate a browser using local inference
    Not tested
  • Extract requirements and score page controls
    Not shown working
  • Run plain-language goals in the browser
    Not tested
  • Inspect and export automation traces
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Good for

  • Find a one-way flight ticket from New York to San Francisco on a date
  • Get walking directions between two places on Maps

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.1.13

Differences the test machine hit

  • README: uv run browser-harness --doctor
    In the test: doctor exits 1 and reports FAIL chrome running / daemon alive / active connections when no Chrome is running

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.