Aside retweeted
if you want your browser to do things or you need your agent to do browser things, look no further than @AsideAI
there isn't a single tool I recommend more than this thing and I tinker with so many things in the applied AI space
The Arc-clones that are Chromium are:
• aside.com/
• yetanotherbrowser.com/
• ardia.dev/
• crestbrowser.com/
I'm typing in this in "Yab" (the 2nd one, "Yet Another Browser").
Aside retweeted
initial impressions of aside browser are really solid, glad to see someone trying the 'ai browser' done well, a CLI and MCP for your browser are so obviously good features
i do wish they'd let me kill all their agent features though, i have my own agent
Aside retweeted
rolled out @AsideAI Browser v1.0.1022.1
turns out putting Liquid Glass everywhere makes a browser heavy. shocking.
so optimized the hell out of it.
also: multiple profiles, native PiP, better rendering.
300+ bromium commits for one update.
we might need therapy.
+ my duo is coming
Introducing Context Awareness. Your browser is now your second brain.
⋅ Remember everything on your screen
⋅ No need to explain your context every time
⋅ Saved privately on your device
⋅ Connect Aside as memory for your personal assistant
aside.com
Aside retweeted
Codex? nah cua? nah
real time btw, using opus 5.5 on high reasoning without fast mode. (this is aside's new computer use that releases soon :D)
Aside retweeted
i'd take the under on "a year" nitter.cf/garrytan/status/211197…
Prediction: you’re all going to be using @AsideAI with your agents in a year or so
Prediction: you’re all going to be using @AsideAI with your agents in a year or so
notice..
> Delta is blocking AI agents from booking flights
> JPMorgan Chase and Charles Schwab block agents from accessing accounts
> Yelp requires paid data licensing for agents
> Amazon has blocked Grok bot and other shopping agents.
the internet is starting to block AI agents that were supposed to do everything for us
thought our docs for boat.dev were dogshit
so I sent astra on @asideai analyze all my past support tickets, user convos and notes on usecases with subagents
this + claude code helped mapping out all the possible user journeys (200+ or them)
then in cloud VMs in chrome claude via pi & cua driver walked each user journey on existing docs and noted friction, 200 journeys in parallel
and then we compiled it all into new docs version and repeated that process a couple times overnight
hope it's good docs now
























