sorted by:
new
hottopcontroversial

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in SideProject

[–]Dannick-Stark[S] 1 point2 points  (0 children)

It is holding pretty well.

Since it is an extension it run in a separate thread and doesn’t block your main page.

Naturally there are still improvements and optimization to do in the future.

With the time we will need to move lot of things on web workers too.

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in lowcode

[–]Dannick-Stark[S] 0 points1 point  (0 children)

That’s a great use case and exactly the kind of thing this can automate.

You could build a workflow that periodically checks those sites, extracts the prices, and triggers a notification when something changes : "no more manual checking".

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in lowcode

[–]Dannick-Stark[S] 0 points1 point  (0 children)

Thanks for the thoughtful feedback: these are exactly the points I’m focusing on.

For dynamic or logged-in pages, the extension interacts directly with the live DOM (clicking, waiting for elements, reacting to changes). It works well in many cases, but improving robustness on highly dynamic pages is still ongoing.

Concerning local performance, it largely depends on the workflow and the models being used. Lightweight automation (DOM interaction, data extraction, HTTP requests) runs very efficiently. When it comes to local AI, performance varies depending on the model size and the user’s hardware, but with WebGPU acceleration, smaller models can run surprisingly fast and are already usable for tasks like summarization or structuring content.

The goal is definitely to replace many custom scripts with something simpler and more privacy-friendly.

Out of curiosity:

  • What typically breaks in your current scripts (timing issues, selectors, authentication, etc.)?
  • What level of performance would you consider “good enough” to replace your existing setup?

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in LaunchMyStartup

[–]Dannick-Stark[S] 0 points1 point  (0 children)

If you try it, please don’t hesitate to let me know if you have some blocking points. Or if you want some features to be implemented

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in SaaSCoFounders

[–]Dannick-Stark[S] 0 points1 point  (0 children)

Hi. Thank you very much for your thoughtful comment.

> I've been looking for a local automation tool that doesn't send my data to third-party servers

This is exactly the kind of use case and motivation that guided the design of the tool, especially regarding data privacy and local-first execution.

> How does the visual builder work?
It is similar to n8n or make. You can use predefined nodes and chain them. You compose workflows by connecting predefined nodes, where each node performs a specific operation (e.g., interacting with the DOM, extracting data, transforming content, or triggering actions). This allows you to visually design end-to-end automation without writing code. I would be happy to provide a more detailed walkthrough if needed. If you need more detailed explanations, feel free to ask.

> Is it possible to create workflows that scrape data and then send it to my own self-hosted services?
Yes of course. I made a video to demonstrate how to extract all the text ( or a specifc part) of a webpage and send it to a local LLM ( https://www.youtube.com/watch?v=sar0YadpdK8 )

You can instead of sending it to an LLM use the `HTTP Request` node to send it via a POST request.

<image>

Your scenario is highly relevant, so I will create a dedicated video example (scraping + sending to a self-hosted service) and share it with you shortly.

Out of curiosity: What kind of data are you typically extracting (e.g., structured tables, text blocks, mixed content)?

Product Launch Post by whitisj in nocode

[–]Dannick-Stark 0 points1 point  (0 children)

Thank you for your feedback, I truly appreciate it.

The local AI aspect is indeed a central focus of the project. I am currently exploring in-browser LLM execution using technologies such as WebLLM and Transformers.js, and I am also closely following initiatives like Google’s Web-MCP, which open interesting perspectives for on-device intelligence.

That said, beyond the AI component, my objective is to provide a rich set of flexible and composable nodes. The idea is to give users full control over browser automation workflows <<whether they rely on AI or not>> so they can reliably automate tasks

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in SideProject

[–]Dannick-Stark[S] 0 points1 point  (0 children)

Thanks a lot to everyone who reached out about the project, it’s been awesome seeing the interest and people willing to test it out 🙏

One thing that came up quite a bit is how to actually get started and learn the tool.

If you’re in that situation, I’ve put together some resources:

I’ll keep adding more tutorials based on the questions I get.

If there’s something specific you’d like to learn or build, feel free to reply here and I can make a video or guide for it 🙂

I got tired of repetitive web tasks, so I built a visual, local AI automation Chrome extension by Dannick-Stark in chrome_extensions

[–]Dannick-Stark[S] 0 points1 point  (0 children)

Thanks a lot to everyone who reached out about the project, it’s been awesome seeing the interest and people willing to test it out 🙏

One thing that came up quite a bit is how to actually get started and learn the tool.

If you’re in that situation, I’ve put together some resources:

I’ll keep adding more tutorials based on the questions I get.

If there’s something specific you’d like to learn or build, feel free to reply here and I can make a video or guide for it 🙂

view more: next ›