umerkay gives Mike a web-research arm

Four new endpoints let the assistant pull live content off the open web - scrape a page, ask a question and get a sourced answer, or map and crawl a whole site.

integrationsearch

umerkay wires Mike up to Olostep, a third-party service that fetches and cleans web pages into tidy text. The result is a research toolkit the assistant can call on: hand it a URL and get readable text back, pose a question and get an answer with its sources listed, or point it at a site to discover and pull every page. Every route sits behind login and checks the address before it reaches out.

It's an early build. The scrape and question-answer paths work today, but the crawl feature only hands back a job ticket - there's no way yet to fetch the finished results, so that piece isn't usable end to end. There's also no rate limiting, caching, or logging on these outbound paid calls, which matters once real matter work runs through them.

So what Worth a look for anyone who wants Mike to reason over live web sources rather than just uploaded documents - but treat it as a foundation, not a finished feature.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from umerkay/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
007f8123 feat(research): add Olostep web research endpoints umerkay 2026-05-01 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-140.md from inside the repo you want the changes in.

⬇ Download capture-thread-140.md