ohthatsnas

This is neat. Any examples of games running on Ikemen-GO now? Either way, will definitely try my hand at getting a mini-game up this weekend

Hey! So we don't explicitly support perimeterX, but some of our users have been able to consistently bypass perimeterX using custom proxies (and some of our own as well).

We'll probably take a deeper look at this in the next few weeks and expand on what we work with vs what we don't.

Haven't tried to build one myself, but that would be a cool project.

If it's a login page that gets redirected to when you try to access a page on your browser, then theoretically you should be able to do that with the open source repo and custom AI logic.

Having to constantly fill out those login pages (especially for networks that expire) is such a pain so would love to use this myself lol

Haha, would love to write one. Will get started on a draft once I get the time. :)

Good point! The space is so early, and it's 100% on us to help people get started building web agents. We're actually re-working this repo (+ a tutorial with it): https://github.com/steel-dev/claude-browser - which implements a web agent by reworking the claude computer use repo + page screenshots for vision.

We also have more AI-specific examples, tutorials, and an MCP server coming out really soon (like really soon).

You can keep an eye out on our releases on discord/twitter where we'll be posting a bunch of these example repos.

You can use any model on top of us! We only provide browser infrastructure, so multiple warm browsers that you can connect to and drive using puppeteer, playwright, selenium, etc.

So you would just need to add some wrapper code and call those actions using a model of your choice.

We're working on more examples and guides that show how you can do this, so keep an eye out on our releases or hop in the discord and you should see some specific examples very soon!

A browser extension would have to run on individual/personal browser; we're focused on providing infrastructure to run hundreds of browsers that you can connect to with code -- whether for automation or information retrieval.

Curious, what made you think browser extension first? :)

Instances are not shared. :) Everyone gets a dedicated session with dedicated resources. One session for every machine.

Yeah, good question! The reason we went open-source is really about transparency and flexibility. We want people to trust what they’re using and have the option to self-host if that’s what makes the most sense for them. Open-sourcing the browser API also lets us build a better product with input and contributions from the community—it’s a win-win.

As for the infra, it’s not totally free—our managed service is there for anyone who doesn’t want the hassle of hosting and scaling everything themselves (although it does have a generous free plan). Going open-source just gives people the choice: run it yourself if you want full control, or use our managed option for convenience and scale. It’s all about making browser automation more accessible without forcing people into one path.

Hey, Nas here.

The concept of agents running wild with only schemas of how to interact with their environment + one another is something I’ve thought about a lot. With current models, I guess this would just be function calling or forced JSON outputs, but I think it would make for some very interesting results.

With Steel, we’re really just providing a way to do something similar to the “rendering engine” in this scenario but with the web. So agents can interface with their environments (websites) very easily and at scale (which comes with its own difficulties wrt deloying/managing)