Aye
Your teachable AI intern for everyday browser work
184 followers
Your teachable AI intern for everyday browser work
184 followers
Aye is a Chromium-based AI browser for macOS and Windows that gives web work a teachable AI intern. It reads visible pages, plans steps, and works through normal browser actions: clicking, typing, scrolling, switching tabs, and checking results. Summarize pages, research across tabs, draft replies, and automate repeatable workflows. Turn recurring tasks into reusable skills, separate accounts with profiles, and stay in control with reviewable progress and approval for sensitive steps.
Turning a recurring task into a reusable skill is the part that stands out to me. When a skill runs again with different inputs — new names, dates, another sheet — does it generalize, or is it tied to the exact values from when you taught it? Congrats on the launch!
@andrei_rebrov1 Thanks, Andrei! Aye is designed to understand the workflow rather than simply replay the exact values from the original teaching session.
So the names, dates, files, or spreadsheet content can change between runs, and Aye should adapt to the new context. If it doesn’t handle a particular variation correctly, you can adjust or re-teach the skill to improve it.
@siyan_chen1 That's exactly what I was hoping for — generalizing the workflow instead of replaying fixed values is what makes a "skill" genuinely reusable, and having re-teach as a fallback for the odd variation is a smart touch. Thanks for the clear reply — congrats again on the launch!
@andrei_rebrov1 Glad that helped! That’s what made the idea of reusable skills click for me too. Thanks for the thoughtful question and the kind words, Andrei!
Congrats on the launch! I’m curious about how Aye handles websites that frequently change their layouts. If I teach it a workflow today and the buttons or page structure change later, can it adapt based on context, or would I need to retrain the skill?
@jing_chang3Thanks for asking.Aye’s skills work more like a regular AI agent than a fixed macro. It has some ability to understand the page, judge the context, and find the appropriate next step, so a skill should still work through many normal layout changes.
Of course, major website changes can occasionally affect a workflow. If that happens, you can adjust or re-teach the relevant steps instead of rebuilding the entire skill from scratch.
The profiles feature is great for keeping things separate, but I'd love to see some kind of shared library or way to export a skill I built on one profile and use it on another. Right now if I make a really useful workflow on my personal profile, I basically have to rebuild it from scratch on my work profile. A simple import/export button for skills would save a lot of time and honestly would probably get me using Aye way more across both accounts.
@fahri1585951 Good news, you shouldn’t need to rebuild it. Aye’s Profile windows keep tabs, cookies, sign-ins, and site data separate, but your skills are shared across profiles. So you can open a work profile and use the same skill you created in your personal one.
If it’s not showing up for any reason, you can reach the maker at https://okaapps.com/support.
honestly the profiles idea is solid but you should let people share skills across profiles with like a simple export/import, or even a small community gallery. would make those reusable automations way more useful instead of rebuilding the same one in every profile
@tunahan7j2k Thanks for the suggestion! Skills in Aye are already shared across profiles, so you don’t need to export and import a skill just to use it in another profile.
Separate export and import options could still be useful for sharing skills with other users or moving them between different devices, though.
Interesting concept.
I'm curious—what surprised you most about how people actually use Aye compared with what you originally expected?
the approval step for sensitive actions is genuinely thoughtful, you know most browser agents just bulldoze through stuff without checking. feels like the team actually thought about trust before shipping.
@duyguerayaa60h yep, that stood out to me too, and it’s one reason I was excited to share Aye. Letting it handle routine steps while keeping sensitive actions under the user’s approval feels like the right balance.
@Xiao Chen fair enough, honest answer beats a made-up one. Good to hear it's reading the page and checking results rather than blind replay, that's the piece that worried me most. Will follow up with the support page if I end up trying it on anything credential-heavy.
@omri_ben_shoham1 Totally understandable—credential-heavy workflows deserve extra caution. We’ll make sure the support documentation clearly explains what Aye can access, how sensitive data is handled, and where users remain in control. Thanks for raising such a thoughtful concern!