Launched this week
Lyto
"One AI agent across your browser, tools, and messages "
259 followers
"One AI agent across your browser, tools, and messages "
259 followers
Lyto AI is a Chrome extension that gives you full control over your browser. Open and close tabs, scroll, click, fill forms, and interact with every DOM element. Integrates with Google Docs, Gmail, and Google Sheets. Research, automate tasks, and organize your workflow — all inside Chrome.
Free Options
Launch Team / Built With
Lyto
Appreciate the straight answer. The part I'd watch closely is the Gmail/Sheets step — since page content is processed server-side, will the whole inbox/sheet DOM get shipped, or can you scope it to just the rows/region the action actually touches so the server only sees what the task needs? Even an opt-in 'this site stays fully local' allowlist would make me comfortable pointing it at a work account.
@arystan_tanekov The cross-app coordination piece is tough — how'd you decide which integrations to ship first? Did you let user requests drive it or had a specific sequencing strategy?
The persistent workflow memory across tabs and tools is the part that stands out - that context loss is exactly what breaks when you bounce between ChatGPT and your actual tabs. Where does that memory actually live: locally in the extension, or synced to your backend (matters a lot once it is reading Gmail and Sheets)? And when it acts on a page, is the DOM automation running locally in my browser while only the reasoning is hosted, or does the page content get shipped server-side on each step?
Lyto
@noctis06 Great questions, happy to be transparent on this.
Memory lives locally in the extension storage on your account, it never leaves your device.
For DOM automation, page content does get processed through our server so the reasoning can act on it. We know that raises valid questions especially as we add Gmail and Sheets, and handling that responsibly is something we are actively building around. Happy to go deeper on the specifics if you want.
Appreciate the straight answer on the split. The piece I would want before pointing it at Gmail/Sheets: when page content goes to your server for reasoning, is it processed ephemerally and dropped, or retained or logged for any window? And is there a way to scope what gets sent, like a column or field allowlist, so a whole sheet is not streamed when the task only needs two columns?
The Google Docs + Gmail + Sheets integrations are what make this practical - those are the three apps most people actually live in, so hitting them first was the right call. Full DOM interaction is powerful but also where browser agents usually hit walls. Two things I'm curious about: how does it handle sites heavy on shadow DOM or cross-origin iframes? That's typically where this approach breaks down. And is agent context session-persistent, or does it lose memory of what it just did when you close and reopen Chrome?
Lyto
@galdayan Really good edge cases to raise. On shadow DOM and cross-origin iframes, if the page is blocking the DOM reader you can always manually select any element yourself and Lyto works from there. Not fully invisible but it doesn't just break.
On memory, context is session-persistent and stays in your history even after you close and reopen Chrome. It doesn't reset on you.
The browser-as-agent-surface bet is the right one. I have spent a lot of time driving real pages with DOM clicks, so the part I keep landing on is the write side. Reading tabs is low stakes, but once it fills and submits forms in Gmail or Sheets, one misread intent sends the email or overwrites a cell. Is there a confirmation gate on mutative actions, or a preview before it commits? That boundary is what decides whether I would let it touch my inbox.
Lyto
@dipankar_sarkar This is exactly the right question and honestly the boundary we think about the most. Yes, mutative actions like sending an email or editing a sheet go through a confirmation step before Lyto commits. You see a preview of what it's about to do and approve it. We are not going to let it touch your inbox without you seeing it first.
one agent across browser, tools, and messages is ambitious, that's a lot of surface area to keep consistent. what's been the trickiest part so far, getting it to actually act vs just summarizing/suggesting stuff.
Lyto
@martin_mo Honestly the hardest part is exactly what you said, getting it to actually act rather than just suggest. Anyone can build something that tells you what to do. The gap is closing the loop so it does it. That's where most of our engineering time has gone and still goes.
That’s a fantastic idea!
Did the inspiration come from a tedious task you personally had to deal with?
Or was it based on requests from users?
Lyto
@nanimono_masa Both honestly! I kept losing context every time I switched between tabs and had to re-explain everything to ChatGPT from scratch. That was the personal frustration. Then when we talked to other people we realised it was not just me, it was everyone bouncing between tools all day. That combo is what pushed us to build it.
@arystan_tanekov I see—it certainly is a tedious task.
Thank you for the answer.
Hey, how does Lyto handle the case where the source data or target workflow is inconsistent instead of clean?
Lyto
@romejerome Great question. When the data or workflow is messy, Lyto flags the inconsistency and asks for clarification before proceeding rather than guessing and getting it wrong. The goal is to never silently do the wrong thing. Happy to go deeper on a specific case if you have one in mind!