Gyrus — agents working alongside your browsing

Raihan Rafeek, Kaaustaaub Shankar and I had built enough AI things by then that the easiest kind of AI help was starting to bug me. You ask a question, get an answer and move on. If a tool keeps taking away the work that helps you understand a subject, you can end up with a good answer and no idea how you got there.

Gyrus was our try at going the other way. Your browser already knows a lot about what you're trying to do. It has the query you started with, the tabs you opened, the source that led you to the next one, and the page you kept coming back to. Then you open some other AI app and explain the whole task again from scratch.

So we put the agents inside the browser. Your browsing gave them context. Different agent crews could gather material, organise it, quiz you, or do other work based on what you were doing. You could talk to them through an in-browser CLI without moving the task somewhere else.

Here's the browser in demo mode. There's no backend behind it, so the sources the crew finds are stand-in pages, but the search, the sorting and the memory graph work the way they did.

The Devpost describes it as using AI to support thinking instead of replacing it. The browser was how we tried to do that.

Gyrus started out as Clay. We renamed it for the hackathon in case Weights & Biases minded the name. Some of that research later carried on into Friction, with a different group and a very different interface.