12 karma · joined July 27, 2023
What if the event flow has a time component?
My naive guess is make the time ticker a tool claude can control time.
Which would bifurcate the control surface into two classes: user accessible (keypress) and user inaccessible (fixtures, time).
"tick" would not work for small intervals.
Instead you would need "progress_x_time".
The concept of non-linear problems lingers in my mind.
Claude in Chrome blocks 58 domains. Banks, Tinder, Reddit, Robinhood, Bloomberg. Also only works in Chrome and Edge. open-claude-in-chrome has none of that.
Same 18 tools, same performance. Claude doesn't know the difference because it was trained on these exact schemas.
Stuff I found running both extensions side-by-side:
- The official forces deviceScaleFactor: 1 via CDP. Without this, Retina displays make every click miss. Spent an afternoon staring at window.devicePixelRatio to figure that one out.
- It doesn't return screenshots on clicks or typing. Only on screenshot and scroll. I was returning one on every action and burning through the 20MB API limit in 15 calls.
Case study on how I built it: https://www.noemica.io/blog/reverse-engineered-claude-in-chr...
Ok bro.
Location: US
Remote: Yes
Willing to relocate: Yes
Technologies: Full-stack SWE
Résumé/CV: Upon request
Email: 1sebastian1sosa1@gmail.com
All info here https://www.kuoly.com/ctg/880e935b-14c5-44b1-9c69-b5f9602309...