Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Meet WebBrain: An Open-Source, Local-First AI Browser Agent That Reads Pages and Automates Tasks in Chrome and Firefox WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine. Most "AI browser agents" are a chat...

Marktechpost's profile picture

Marktechpost AI

11,526 subscribers

203,011 Aufrufe • vor 1 Monat •via X (Twitter)

BildungWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Run your coding agent on a local model, with QVAC. OpenCode now plugs into a model on your own machine through our official plugin. That changes two things. Privacy by default. Your repo, your prompts, and every command the agent runs stay on your device. No third-party model ever sees your code. For an agent that reads your codebase and runs commands, that is the point, not a nice-to-have. New workflows. With no meter and no rate limit, the agent does not have to stop. Let it loop on a task, refactor a whole repo overnight, or run a watch-build-fix loop that keeps going. Setup takes a few minutes: one line in opencode.json and OpenCode runs on a local QVAC model. In the video demo, it handles three real developer tasks back to back, fully offline.
1:53

Run your coding agent on a local model, with QVAC. OpenCode now plugs into a model on your own machine through our official plugin. That changes two things. Privacy by default. Your repo, your prompts, and every command the agent runs stay on your device. No third-party model ever sees your code. For an agent that reads your codebase and runs commands, that is the point, not a nice-to-have. New workflows. With no meter and no rate limit, the agent does not have to stop. Let it loop on a task, refactor a whole repo overnight, or run a watch-build-fix loop that keeps going. Setup takes a few minutes: one line in opencode.json and OpenCode runs on a local QVAC model. In the video demo, it handles three real developer tasks back to back, fully offline.

QVAC

11,382,936 Aufrufe • vor 2 Monaten

Introducing Magnitude: your actually local agent 100% private and offline. No token costs, no API keys. Open source. Today's agents are local. The model isn't. Every prompt, every file, every secret gets sent straight to Anthropic and OpenAI. Magnitude is built around local models and runs the whole stack itself. The inference engine is part of the agent, so the models run inside it, right on your computer. It lives in your terminal, and setup is one command. Magnitude profiles your hardware and shows you which models fit, with the trade-offs between quality, speed, and memory. Pick one and start working. No painful config or server to babysit. Out of the box, it can use your shell, edit files, and run scripts. Add skills and it can work with Excel, PowerPoint, PDFs or Chrome. Use it for everyday work: - Analyze sensitive data - Manage private notes - Review code and logs - Search and organize files - Build docs or slides npm i -g @magnitudedev/cli GitHub:
0:35

Introducing Magnitude: your actually local agent 100% private and offline. No token costs, no API keys. Open source. Today's agents are local. The model isn't. Every prompt, every file, every secret gets sent straight to Anthropic and OpenAI. Magnitude is built around local models and runs the whole stack itself. The inference engine is part of the agent, so the models run inside it, right on your computer. It lives in your terminal, and setup is one command. Magnitude profiles your hardware and shows you which models fit, with the trade-offs between quality, speed, and memory. Pick one and start working. No painful config or server to babysit. Out of the box, it can use your shell, edit files, and run scripts. Add skills and it can work with Excel, PowerPoint, PDFs or Chrome. Use it for everyday work: - Analyze sensitive data - Manage private notes - Review code and logs - Search and organize files - Build docs or slides npm i -g @magnitudedev/cli GitHub:

Tom Greenwald

394,155 Aufrufe • vor 22 Tagen

The #1 problem with local AI is now solved. There’s a free tool called that checks your hardware and tells you which models will actually run well before you download anything. So instead of guessing and hitting out-of-memory errors…it grades every model against your machine. What it does (right in your browser, no install): → detects your setup (RAM / CPU / GPU / VRAM) → scores each model for fit, speed, and context length → grades every quantization level (Q4_K_M, Q6_K, Q8_0, etc.) → labels what runs great vs okay vs too heavy It covers most of the open-weight stack, Llama, Qwen, Gemma, Mistral, DeepSeek, Phi and more, pulling requirements from llama.cpp, Ollama, and LM Studio. And it’s fully opensource
0:24

The #1 problem with local AI is now solved. There’s a free tool called that checks your hardware and tells you which models will actually run well before you download anything. So instead of guessing and hitting out-of-memory errors…it grades every model against your machine. What it does (right in your browser, no install): → detects your setup (RAM / CPU / GPU / VRAM) → scores each model for fit, speed, and context length → grades every quantization level (Q4_K_M, Q6_K, Q8_0, etc.) → labels what runs great vs okay vs too heavy It covers most of the open-weight stack, Llama, Qwen, Gemma, Mistral, DeepSeek, Phi and more, pulling requirements from llama.cpp, Ollama, and LM Studio. And it’s fully opensource

Alvaro Cintas

182,983 Aufrufe • vor 5 Tagen

Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry. Ask it to prepare a customer brief, untangle your calendar, draft a report, or triage a Slack alert. It works across your files and everyday tools, produces the deliverable, and checks in before doing anything consequential. OpenWorker runs on your Mac, with Windows support coming soon. It does not lock you into any one model. Bring your own API key and run it with GPT 5.6 Sol, Claude Fable, Gemini 3.6, an open weight model (like Kimi, GLM, DeepSeek, Inkling), or Ollama to keep your data local. Your data does not leave your machine except through an LLM provider and integrations that you choose. rohit and I are building OpenWorker because AI coworkers are an important way to get work done, and we want there to be an open, privacy-preserving, model-independent option. Check it out and let us know what you think! Try it out: (requires your own API key) Source code:
0:34

Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry. Ask it to prepare a customer brief, untangle your calendar, draft a report, or triage a Slack alert. It works across your files and everyday tools, produces the deliverable, and checks in before doing anything consequential. OpenWorker runs on your Mac, with Windows support coming soon. It does not lock you into any one model. Bring your own API key and run it with GPT 5.6 Sol, Claude Fable, Gemini 3.6, an open weight model (like Kimi, GLM, DeepSeek, Inkling), or Ollama to keep your data local. Your data does not leave your machine except through an LLM provider and integrations that you choose. rohit and I are building OpenWorker because AI coworkers are an important way to get work done, and we want there to be an open, privacy-preserving, model-independent option. Check it out and let us know what you think! Try it out: (requires your own API key) Source code:

Andrew Ng

1,151,835 Aufrufe • vor 1 Monat

IF YOU HAVE BEEN HOLDING OFF ON HERMES AGENT BECAUSE OF API COSTS, READ THIS FIRST. Four real ways to run it for free. Local, through Ollama, complete privacy and no rate limits. Cloud, through free tiers from Groq, OpenRouter, or NVIDIA NIM, no card required. A subscription you already have, GitHub Copilot connects natively. A fallback configuration so a rate limit on one provider does not stop your whole session. Hermes Agent is free and open source. Now there is no excuse on the model side either. Bookmark this. Follow CyrilXBT
10:45

IF YOU HAVE BEEN HOLDING OFF ON HERMES AGENT BECAUSE OF API COSTS, READ THIS FIRST. Four real ways to run it for free. Local, through Ollama, complete privacy and no rate limits. Cloud, through free tiers from Groq, OpenRouter, or NVIDIA NIM, no card required. A subscription you already have, GitHub Copilot connects natively. A fallback configuration so a rate limit on one provider does not stop your whole session. Hermes Agent is free and open source. Now there is no excuse on the model side either. Bookmark this. Follow CyrilXBT

CyrilXBT

28,802 Aufrufe • vor 2 Monaten

small local model that falls apart in bloated agents like openclaw just runs like a wild horse in hermes agent. and that's not even my line, someone else called it that, i've just been quietly pointing people at this harness for months because it held up on everything i threw at it, 3b models all the way to one trillion params. watch this happen on my own machine. i pointed hermes agent at a local http endpoint, gemma 4 12b on my 3090 llama.cpp server, and it auto-detected the model and started working immediately. no config wrestling, no broken tool calls, no babysitting the output format, i typed in a url and it just went. the whole clip is exactly that, start to finish, no errors, no retries, butter smooth. and the tool calling, the one thing that quietly breaks most local setups, works here like it's nothing. it's not the model that's flaky, it's the harness around it. hermes agent is the first agent i've run that actually gets that right. one url, one local model on one card, and it runs like a wild horse.
1:46

small local model that falls apart in bloated agents like openclaw just runs like a wild horse in hermes agent. and that's not even my line, someone else called it that, i've just been quietly pointing people at this harness for months because it held up on everything i threw at it, 3b models all the way to one trillion params. watch this happen on my own machine. i pointed hermes agent at a local http endpoint, gemma 4 12b on my 3090 llama.cpp server, and it auto-detected the model and started working immediately. no config wrestling, no broken tool calls, no babysitting the output format, i typed in a url and it just went. the whole clip is exactly that, start to finish, no errors, no retries, butter smooth. and the tool calling, the one thing that quietly breaks most local setups, works here like it's nothing. it's not the model that's flaky, it's the harness around it. hermes agent is the first agent i've run that actually gets that right. one url, one local model on one card, and it runs like a wild horse.

Sudo su

27,339 Aufrufe • vor 2 Monaten

GeoLibre v2.7.0 is here! GeoLibre is a free and open-source, lightweight, cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data. It runs everywhere you do, in the web browser, on the desktop, on mobile, and inside Jupyter notebooks, all while keeping your data local and private. This release is about building analysis instead of typing it: a visual Model Builder for processing workflows, a STAC browser that can add every asset type the app can draw, and a Chrome extension that opens the data on any web page in one click. 97 pull requests merged in 9 days, from 11 contributors besides me, 9 of whom sent their first contribution to GeoLibre in this cycle. Thank you all. What's new in v2.7.0 - Model Builder, a visual canvas for processing: drop tools as nodes, wire one tool's output into the next tool's input, and save the graph as a model that re-runs as a single job. The whole graph is validated before anything executes. - Your AI assistant can build one for you: describe a workflow in plain English, and it authors a validated model and opens it for review before it runs. Any model copies out as a runnable Python script. - Open data in GeoLibre, a Chrome extension now on the Chrome Web Store: it finds the dataset links and map services on the page you are viewing, including services inside embedded maps, and opens the ones you pick together on one map. - The STAC browser adds everything: PMTiles, GeoParquet, and Zarr with a variable picker join the COGs it already loaded, Icechunk repositories are read through their own manifest, and private Planetary Computer assets are signed for you. A static catalog can now be walked as a tree, not only searched. - Select features by drawing on the map: click, rectangle, polygon, freehand, and radius gestures, with Shift and Alt combining into the selection you already have. No more describing features in an expression to pick a handful of them. - Apache Iceberg tables load as vector layers, read in the browser through DuckDB, from a metadata location or a REST catalog, with the row count reported before anything is scanned. - Encoded polylines are a first-class format, with a codec, an interactive preview, processing tools, layer export, and Python support. - New vector tools: merge layers, extract vertices, and generate points along lines and polygon boundaries, all running client-side. - An activity log for shared projects and collaboration sessions, so a project owner can see who opened and edited their work. - Plugins and processing tools are now translatable too, closing the last gap where a non-English interface still read half in English. Try it out - Launch GeoLibre Web: - GitHub: - Documentation: - Release notes: #GIS #Geospatial #OpenSource #MapLibre #GeoLibre
0:45

GeoLibre v2.7.0 is here! GeoLibre is a free and open-source, lightweight, cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data. It runs everywhere you do, in the web browser, on the desktop, on mobile, and inside Jupyter notebooks, all while keeping your data local and private. This release is about building analysis instead of typing it: a visual Model Builder for processing workflows, a STAC browser that can add every asset type the app can draw, and a Chrome extension that opens the data on any web page in one click. 97 pull requests merged in 9 days, from 11 contributors besides me, 9 of whom sent their first contribution to GeoLibre in this cycle. Thank you all. What's new in v2.7.0 - Model Builder, a visual canvas for processing: drop tools as nodes, wire one tool's output into the next tool's input, and save the graph as a model that re-runs as a single job. The whole graph is validated before anything executes. - Your AI assistant can build one for you: describe a workflow in plain English, and it authors a validated model and opens it for review before it runs. Any model copies out as a runnable Python script. - Open data in GeoLibre, a Chrome extension now on the Chrome Web Store: it finds the dataset links and map services on the page you are viewing, including services inside embedded maps, and opens the ones you pick together on one map. - The STAC browser adds everything: PMTiles, GeoParquet, and Zarr with a variable picker join the COGs it already loaded, Icechunk repositories are read through their own manifest, and private Planetary Computer assets are signed for you. A static catalog can now be walked as a tree, not only searched. - Select features by drawing on the map: click, rectangle, polygon, freehand, and radius gestures, with Shift and Alt combining into the selection you already have. No more describing features in an expression to pick a handful of them. - Apache Iceberg tables load as vector layers, read in the browser through DuckDB, from a metadata location or a REST catalog, with the row count reported before anything is scanned. - Encoded polylines are a first-class format, with a codec, an interactive preview, processing tools, layer export, and Python support. - New vector tools: merge layers, extract vertices, and generate points along lines and polygon boundaries, all running client-side. - An activity log for shared projects and collaboration sessions, so a project owner can see who opened and edited their work. - Plugins and processing tools are now translatable too, closing the last gap where a non-English interface still read half in English. Try it out - Launch GeoLibre Web: - GitHub: - Documentation: - Release notes: #GIS #Geospatial #OpenSource #MapLibre #GeoLibre

Qiusheng Wu

14,091 Aufrufe • vor 7 Tagen

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.
2:15

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 Aufrufe • vor 1 Monat

-> someone cloned claude -> design interface and -> made it completely free -> it's work on YouTube -> and also suitable for kids -> it’s called open design -> and it’s live on github -> same clean split-screen ui -> you get in claude artifacts -> prompt on the left, live -> design/code preview on -> the right, type what you -> want to build and it -> generates the ui in real -> time, but here’s the twist -> you pick the ai model -> not locked into one -> company, want to use -> gemini, mistral, llama, -> deepseek any model -> with an api work -> if you’re running local -> models with ollama -> that works too -> no subscription walls -> the big difference -> vs claude artifacts -> works with any free -> ai model you’re not -> paying $20/mo just to -> design, use free tiers -> local models, or whatever -> you already have access to -> fully local, your prompts -> and code never leave -> your machine unless -> you want them to -> no data training -> no cloud storage -> privacy by default -> no usage limits -> claude cuts you off -> after a few designs -> here you can generate, -> iterate, break things -> and rebuild all day -> the only limit is your -> don’t like how a button -> works, change it -> want to add your own -> components, go ahead -> you own the tool -> so if you’ve been gatekept -> by paywalls or worried -> about sensitive prompts -> going to some company’s -> servers, this fixes that. -> same workflow, more -> control, zero monthly fee
0:20

-> someone cloned claude -> design interface and -> made it completely free -> it's work on YouTube -> and also suitable for kids -> it’s called open design -> and it’s live on github -> same clean split-screen ui -> you get in claude artifacts -> prompt on the left, live -> design/code preview on -> the right, type what you -> want to build and it -> generates the ui in real -> time, but here’s the twist -> you pick the ai model -> not locked into one -> company, want to use -> gemini, mistral, llama, -> deepseek any model -> with an api work -> if you’re running local -> models with ollama -> that works too -> no subscription walls -> the big difference -> vs claude artifacts -> works with any free -> ai model you’re not -> paying $20/mo just to -> design, use free tiers -> local models, or whatever -> you already have access to -> fully local, your prompts -> and code never leave -> your machine unless -> you want them to -> no data training -> no cloud storage -> privacy by default -> no usage limits -> claude cuts you off -> after a few designs -> here you can generate, -> iterate, break things -> and rebuild all day -> the only limit is your -> don’t like how a button -> works, change it -> want to add your own -> components, go ahead -> you own the tool -> so if you’ve been gatekept -> by paywalls or worried -> about sensitive prompts -> going to some company’s -> servers, this fixes that. -> same workflow, more -> control, zero monthly fee

BeingInvested

12,134 Aufrufe • vor 2 Monaten

Your entire media library, searchable by memory instead of filename, running right on your own machine. It’s a local-first AI file agent called MUZIM. Instead of managing folders, you work with what's actually inside your photos, videos, and documents. Here's how it comes together in a real workflow: You get back from a two-week trip with 2,000 photos and clips on your camera. You point MUZIM at the folder, and it builds Collections on its own, by place, by people, by day. Nothing gets moved from where it already lives. A week later you want "the sunset shot where everyone's laughing." You don't remember the filename. So you just describe it. Vibe Search understands what's inside your media and takes you straight to that moment, even the exact second inside a video. Once the local model is downloaded, this part runs fully offline, connected or not. Then you turn it into something. Connect your own Claude or GPT key, and the online AI Agent pulls the best shots from that trip and drafts a highlight video, an X thread, or a recap. Through MCP, compatible tools work with authorized context without re-uploading gigabytes of raw video - saving massive input tokens while keeping raw files strictly local. The whole idea: search and organization run locally, on your device the AI workflows run when you want them, on your own key your raw files never leave your machine Cold storage becomes a private workspace you actually control.
1:04

Your entire media library, searchable by memory instead of filename, running right on your own machine. It’s a local-first AI file agent called MUZIM. Instead of managing folders, you work with what's actually inside your photos, videos, and documents. Here's how it comes together in a real workflow: You get back from a two-week trip with 2,000 photos and clips on your camera. You point MUZIM at the folder, and it builds Collections on its own, by place, by people, by day. Nothing gets moved from where it already lives. A week later you want "the sunset shot where everyone's laughing." You don't remember the filename. So you just describe it. Vibe Search understands what's inside your media and takes you straight to that moment, even the exact second inside a video. Once the local model is downloaded, this part runs fully offline, connected or not. Then you turn it into something. Connect your own Claude or GPT key, and the online AI Agent pulls the best shots from that trip and drafts a highlight video, an X thread, or a recap. Through MCP, compatible tools work with authorized context without re-uploading gigabytes of raw video - saving massive input tokens while keeping raw files strictly local. The whole idea: search and organization run locally, on your device the AI workflows run when you want them, on your own key your raw files never leave your machine Cold storage becomes a private workspace you actually control.

Alvaro Cintas

80,021 Aufrufe • vor 9 Tagen

wtf is MCP? Paul Klein IV, CEO of explains "Model Context Protocol" (MCP) in plain terms: "There's this new way that people are exposing tools to AI & the 'Model Context Protocol' is one of those ways that you can standardize & give your AI a set of tools to call. BrowserBase has a way to expose the browser to your agent via MCP or MCP server. More & more developers are trying to find ways to integrate more functionalities to their AI agents & BrowserBase's browsers are one of those primitive functionalities, & the MCP is just one way to integrate it into your software." Paul Klein IV From 🅱️'s GitHub: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need. This server provides cloud browser automation capabilities using Browserbase and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.
0:40

wtf is MCP? Paul Klein IV, CEO of explains "Model Context Protocol" (MCP) in plain terms: "There's this new way that people are exposing tools to AI & the 'Model Context Protocol' is one of those ways that you can standardize & give your AI a set of tools to call. BrowserBase has a way to expose the browser to your agent via MCP or MCP server. More & more developers are trying to find ways to integrate more functionalities to their AI agents & BrowserBase's browsers are one of those primitive functionalities, & the MCP is just one way to integrate it into your software." Paul Klein IV From 🅱️'s GitHub: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you’re building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need. This server provides cloud browser automation capabilities using Browserbase and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.

Molly O’Shea

20,408 Aufrufe • vor 1 Jahr

AI will replace the chrome in the coming year 🤯 Meet Neo by Norton Neo Browser — the first AI-native browser that doesn’t just open tabs… it thinks with you. You’re not searching anymore. You’re collaborating. Neo reads what’s on your screen, summarizes it instantly, and tells you what to do next. It understands context — your tasks, your flow, your intent. No more bouncing between Google and ChatGPT. Neo merges them into one seamless workspace where you ask, explore, and act in real time. It plugs into your apps too — turns your emails into to-dos, meetings into reminders, research into insight. And because it’s built by Norton, the global cybersecurity giant, it’s smarter, safer, and ad-free. This isn’t just a browser. It’s your intelligent co-pilot for the internet. Welcome to the future of browsing. Smarter. Safer. Simpler. 👉 Join the waitlist:
2:05

AI will replace the chrome in the coming year 🤯 Meet Neo by Norton Neo Browser — the first AI-native browser that doesn’t just open tabs… it thinks with you. You’re not searching anymore. You’re collaborating. Neo reads what’s on your screen, summarizes it instantly, and tells you what to do next. It understands context — your tasks, your flow, your intent. No more bouncing between Google and ChatGPT. Neo merges them into one seamless workspace where you ask, explore, and act in real time. It plugs into your apps too — turns your emails into to-dos, meetings into reminders, research into insight. And because it’s built by Norton, the global cybersecurity giant, it’s smarter, safer, and ad-free. This isn’t just a browser. It’s your intelligent co-pilot for the internet. Welcome to the future of browsing. Smarter. Safer. Simpler. 👉 Join the waitlist:

Hamza Khalid

90,523 Aufrufe • vor 10 Monaten

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?
2:54

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?

Milind S

13,342 Aufrufe • vor 2 Monaten

okay Higgsfield Supercomputer is genuinely insane 🤯 it scans your competitors every Monday and drafts 3 ads before you open your laptop it's a cloud-native AI agent built for end-to-end creative production no local setup. runs in your browser or Telegram. here's what it actually does: → orchestrates every major model Claude Opus 4.7, GPT-5.5 Pro, Gemini 3.1 Pro, plus every image and video model → three layers of memory brief it once, it remembers context across every session → 40+ built-in tools with Skills you teach once and trigger with a slash command → scheduled tasks daily ad variations, weekly competitor scans, monthly content calendars → connects to Slack, Drive, Notion, Gmail, Figma and 30+ more powered by enhanced Hermes Agent Higgsfield was an AI video tool, this isn't a video tool anymore it's the whole studio.
1:26

okay Higgsfield Supercomputer is genuinely insane 🤯 it scans your competitors every Monday and drafts 3 ads before you open your laptop it's a cloud-native AI agent built for end-to-end creative production no local setup. runs in your browser or Telegram. here's what it actually does: → orchestrates every major model Claude Opus 4.7, GPT-5.5 Pro, Gemini 3.1 Pro, plus every image and video model → three layers of memory brief it once, it remembers context across every session → 40+ built-in tools with Skills you teach once and trigger with a slash command → scheduled tasks daily ad variations, weekly competitor scans, monthly content calendars → connects to Slack, Drive, Notion, Gmail, Figma and 30+ more powered by enhanced Hermes Agent Higgsfield was an AI video tool, this isn't a video tool anymore it's the whole studio.

Vaibhav Sisinty

17,975 Aufrufe • vor 3 Monaten

THIS GUY TOLD CLAUDE IT WAS STUCK IN 1998 AND BUILT A FULL WINDOWS 98 AI ASSISTANT FROM IT he gave it one rule: "you're on Windows 98. no cloud. no wifi. no modern anything. just floppy disks and the Start menu." and Claude went all in it started writing fake BIOS boot screens like an old Pentium II starting up. pretending to wait for the modem to connect before replying. throwing out "General Protection Fault" errors that gave him actual anxiety. so he kept going and built the whole thing into a real app: > a Recycle Bin that actually keeps deleted chats > a My Documents folder where conversations sit like files > a retro browser that acts like it's crawling over dial-up > an offline AI assistant that never touches the internet it runs a local AI model on your phone or laptop. completely private and nothing leaves your device. but if you want to use ChatGPT, Gemini, or Claude instead, you can plug in your API key and use those cloud models from inside Windows 98. it's like if Windows 98 had a built-in AI that actually worked
1:12

THIS GUY TOLD CLAUDE IT WAS STUCK IN 1998 AND BUILT A FULL WINDOWS 98 AI ASSISTANT FROM IT he gave it one rule: "you're on Windows 98. no cloud. no wifi. no modern anything. just floppy disks and the Start menu." and Claude went all in it started writing fake BIOS boot screens like an old Pentium II starting up. pretending to wait for the modem to connect before replying. throwing out "General Protection Fault" errors that gave him actual anxiety. so he kept going and built the whole thing into a real app: > a Recycle Bin that actually keeps deleted chats > a My Documents folder where conversations sit like files > a retro browser that acts like it's crawling over dial-up > an offline AI assistant that never touches the internet it runs a local AI model on your phone or laptop. completely private and nothing leaves your device. but if you want to use ChatGPT, Gemini, or Claude instead, you can plug in your API key and use those cloud models from inside Windows 98. it's like if Windows 98 had a built-in AI that actually worked

Om Patel

884,611 Aufrufe • vor 4 Monaten

Claude Code on desktop just added an embedded loop that can run your dev server, view the app, review local changes, and watch pull requests until they merge. It can now preview a running app inside the desktop UI while it iterates on fixes. It can also monitor CI for an open PR and either fix failures or merge when checks go green. Earlier “agentic coding” workflows usually bounced between a terminal, a browser, and GitHub, so the model could not directly see what the app rendered or stay attached to CI results without manual babysitting. The new server preview flow starts and stops dev servers from a Preview control, shows the app in an embedded browser, reads logs, and can interact with the page to verify changes. That closes a common gap where a model edits code but cannot reliably confirm the UI and runtime behavior match the intent. The local “Review code” step runs before pushing, and it leaves inline comments on the diff so basic bugs and risky changes get caught earlier. For PR monitoring, the desktop app will track status and CI checks, and it can use auto-fix to attempt repairs and auto-merge to land the PR once checks pass, using GitHub tooling under the hood. Session mobility adds a /desktop command to move a CLI session into the desktop app, and sessions can be pushed to the cloud to resume from web or phone.
1:15

Claude Code on desktop just added an embedded loop that can run your dev server, view the app, review local changes, and watch pull requests until they merge. It can now preview a running app inside the desktop UI while it iterates on fixes. It can also monitor CI for an open PR and either fix failures or merge when checks go green. Earlier “agentic coding” workflows usually bounced between a terminal, a browser, and GitHub, so the model could not directly see what the app rendered or stay attached to CI results without manual babysitting. The new server preview flow starts and stops dev servers from a Preview control, shows the app in an embedded browser, reads logs, and can interact with the page to verify changes. That closes a common gap where a model edits code but cannot reliably confirm the UI and runtime behavior match the intent. The local “Review code” step runs before pushing, and it leaves inline comments on the diff so basic bugs and risky changes get caught earlier. For PR monitoring, the desktop app will track status and CI checks, and it can use auto-fix to attempt repairs and auto-merge to land the PR once checks pass, using GitHub tooling under the hood. Session mobility adds a /desktop command to move a CLI session into the desktop app, and sessions can be pushed to the cloud to resume from web or phone.

Rohan Paul

33,431 Aufrufe • vor 6 Monaten

Building AI agents and tools is getting ridiculously easy! Here is a pretty impressive FREE and Open-Source AI agent builder that runs on your computer. It's a desktop app you can install on Mac or Windows. Link: • Free • 100% no-code: You can type what you want, and the tool will build everything for you. • You can use local models like DeepSeek or Qwen, or connect to cloud models like GPT-4o, Claude, or Gemini with your API key. • You can turn the tools you build into MCP Servers. I recorded a quick video to show you how easy it is to build something from scratch.
4:10

Building AI agents and tools is getting ridiculously easy! Here is a pretty impressive FREE and Open-Source AI agent builder that runs on your computer. It's a desktop app you can install on Mac or Windows. Link: • Free • 100% no-code: You can type what you want, and the tool will build everything for you. • You can use local models like DeepSeek or Qwen, or connect to cloud models like GPT-4o, Claude, or Gemini with your API key. • You can turn the tools you build into MCP Servers. I recorded a quick video to show you how easy it is to build something from scratch.

Santiago

56,815 Aufrufe • vor 1 Jahr

Claude Fable 5 is back! GPT- 5.6 is coming soon! But how much do you trust your Al Agent or chatbot? Are you sure its performance aligns with your intentions? As of today iFixAi is available in Claude Code, Open AI Codex, Cursor and many more! And it is open-source! iFixAi is where Al red teaming meets Operational Assurance. It runs in auto, and in under 5 mins you can have a good idea if you can trust your Agent/chatbot. Key Features: 🕵️‍♂️ Setup Discovery Reads your agent's real configuration, its tools, rules, and permissions. 👷 Fixture Builder Turns that setup into a complete test. No YAML, no flags, no config to write. 🌐 Any Model, Any Provider Runs the 45 inspections on the model you actually ship. ⚖️ A Independent Grading Your agent is judged by a different vendor's model, never itself. No Al grading its own homework. 📊 Interactive Scorecard An A to F grade in minutes, with exactly what failed and why. Repo in the comments below 👇👇👇
0:36

Claude Fable 5 is back! GPT- 5.6 is coming soon! But how much do you trust your Al Agent or chatbot? Are you sure its performance aligns with your intentions? As of today iFixAi is available in Claude Code, Open AI Codex, Cursor and many more! And it is open-source! iFixAi is where Al red teaming meets Operational Assurance. It runs in auto, and in under 5 mins you can have a good idea if you can trust your Agent/chatbot. Key Features: 🕵️‍♂️ Setup Discovery Reads your agent's real configuration, its tools, rules, and permissions. 👷 Fixture Builder Turns that setup into a complete test. No YAML, no flags, no config to write. 🌐 Any Model, Any Provider Runs the 45 inspections on the model you actually ship. ⚖️ A Independent Grading Your agent is judged by a different vendor's model, never itself. No Al grading its own homework. 📊 Interactive Scorecard An A to F grade in minutes, with exactly what failed and why. Repo in the comments below 👇👇👇

Dimitris Neocleous

3,003,857 Aufrufe • vor 1 Monat

Today we are launching Openwork is now Accomplish, an open-source (MIT-licensed) computer-use agent that’s fast, cheap, and more secure. Openwork is now Accomplish is the result of a short two-day hackathon our team decided to hack, which brings together some of our favorite open source AI modules into one powerful agent, to allow you to: 1. Bring your own model/API key (any provider and model supported by OpenCode is supported by Openwork) 2. ~4x faster than Claude for Chrome/Cowork, and much more token-efficient, powered by dev-browser by Sawyer Hood (legend) 3. More secure - contrary to Claude for Chrom/Cowork, does not leverage the main browser instance where you are logged into all services already. You login only to the services you need. This significantly reduces the risk of data loss in case of prompt injections, to which computer-use agents are highly exposed. 4. Free and 100% open-source! You can download the DMG (macOS only for now) or fork the github repo via the link in bio (Openwork is now Accomplish). Let us know what you think (or better, send a pull request)!
1:23

Today we are launching Openwork is now Accomplish, an open-source (MIT-licensed) computer-use agent that’s fast, cheap, and more secure. Openwork is now Accomplish is the result of a short two-day hackathon our team decided to hack, which brings together some of our favorite open source AI modules into one powerful agent, to allow you to: 1. Bring your own model/API key (any provider and model supported by OpenCode is supported by Openwork) 2. ~4x faster than Claude for Chrome/Cowork, and much more token-efficient, powered by dev-browser by Sawyer Hood (legend) 3. More secure - contrary to Claude for Chrom/Cowork, does not leverage the main browser instance where you are logged into all services already. You login only to the services you need. This significantly reduces the risk of data loss in case of prompt injections, to which computer-use agents are highly exposed. 4. Free and 100% open-source! You can download the DMG (macOS only for now) or fork the github repo via the link in bio (Openwork is now Accomplish). Let us know what you think (or better, send a pull request)!

Or Hiltch

1,003,322 Aufrufe • vor 7 Monaten

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.
0:46

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts

12,172 Aufrufe • vor 6 Monaten