Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Turn any PDF, image, DOCX, or PPTX into clean Markdown! Production workloads contain millions of pages, mixed formats, inconsistent layouts, low-quality scans, and documents written in dozens of languages. Datalab Marker v2 (open-source with 40k stars) handles that workload at scale through one open-source document parsing pipeline. It recovers:...

_avichawla's profile picture

Avi Chawla

79,011 subscribers

13,147 görüntüleme • 6 gün önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Building RAG is easy. Parsing real, unstructured data is the hard part. Most tools fail when documents get complicated. RAGFlow by InfiniFlow makes the entire process visual and flawless 🔥 It is an (open-source!) engine built specifically to find the exact needle in a data haystack, even across literally unlimited tokens. The platform comes packed with: → "Quality in, quality out" parsing for highly complex formats → Multiple recall paired with fused re-ranking → A built-in Python and JavaScript code executor for agents → An orchestrable ingestion pipeline Here's why it stands out: 1️⃣ Structural Understanding Instead of just scraping text, it handles tables across pages, scanned copies, slides, and Excel sheets natively using deep document understanding. 2️⃣ Grounded Citations Every answer is verifiable. The UI highlights the exact chunks used, allowing you to trace any response directly back to the source material. 3️⃣ Enterprise Synchronization Keep your context constantly updated with native data sync from Google Drive, Notion, Discord, and Confluence. Stop letting bad document parsing ruin your RAG systems. Best part? It's 100% Free and open-source. Link to the repo in 🧵↓
0:18

Building RAG is easy. Parsing real, unstructured data is the hard part. Most tools fail when documents get complicated. RAGFlow by InfiniFlow makes the entire process visual and flawless 🔥 It is an (open-source!) engine built specifically to find the exact needle in a data haystack, even across literally unlimited tokens. The platform comes packed with: → "Quality in, quality out" parsing for highly complex formats → Multiple recall paired with fused re-ranking → A built-in Python and JavaScript code executor for agents → An orchestrable ingestion pipeline Here's why it stands out: 1️⃣ Structural Understanding Instead of just scraping text, it handles tables across pages, scanned copies, slides, and Excel sheets natively using deep document understanding. 2️⃣ Grounded Citations Every answer is verifiable. The UI highlights the exact chunks used, allowing you to trace any response directly back to the source material. 3️⃣ Enterprise Synchronization Keep your context constantly updated with native data sync from Google Drive, Notion, Discord, and Confluence. Stop letting bad document parsing ruin your RAG systems. Best part? It's 100% Free and open-source. Link to the repo in 🧵↓

Charly Wargnier

19,220 görüntüleme • 6 ay önce

Fine-tune DeepSeek-OCR on your own language! (100% local) DeepSeek-OCR is a 3B-parameter vision model that achieves 97% precision while using 10× fewer vision tokens than text-based LLMs. It handles tables, papers, and handwriting without killing your GPU or budget. Why it matters: Most vision models treat documents as massive sequences of tokens, making long-context processing expensive and slow. DeepSeek-OCR uses context optical compression to convert 2D layouts into vision tokens, enabling efficient processing of complex documents. The best part? You can easily fine-tune it for your specific use case on a single GPU. I used Unsloth to run this experiment on Persian text and saw an 88.26% improvement in character error rate. ↳ Base model: 149% character error rate (CER) ↳ Fine-tuned model: 60% CER (57% more accurate) ↳ Training time: 60 steps on a single GPU Persian was just the test case. You can swap in your own dataset for any language, document type, or specific domain you're working with. I've shared the complete guide in the next tweet - all the code, notebooks, and environment setup ready to run with a single click. Everything is 100% open-source!
0:14

Fine-tune DeepSeek-OCR on your own language! (100% local) DeepSeek-OCR is a 3B-parameter vision model that achieves 97% precision while using 10× fewer vision tokens than text-based LLMs. It handles tables, papers, and handwriting without killing your GPU or budget. Why it matters: Most vision models treat documents as massive sequences of tokens, making long-context processing expensive and slow. DeepSeek-OCR uses context optical compression to convert 2D layouts into vision tokens, enabling efficient processing of complex documents. The best part? You can easily fine-tune it for your specific use case on a single GPU. I used Unsloth to run this experiment on Persian text and saw an 88.26% improvement in character error rate. ↳ Base model: 149% character error rate (CER) ↳ Fine-tuned model: 60% CER (57% more accurate) ↳ Training time: 60 steps on a single GPU Persian was just the test case. You can swap in your own dataset for any language, document type, or specific domain you're working with. I've shared the complete guide in the next tweet - all the code, notebooks, and environment setup ready to run with a single click. Everything is 100% open-source!

Akshay 🚀

126,273 görüntüleme • 11 ay önce

Stop manually making flowcharts. Try this GitHub skill with Claude Code. I found an open-source tool that turns a plain description of a software system into a clean, interactive diagram. It's called Archify, and it has more than 66,000 stars on GitHub. You add it as a skill to an AI coding agent like Claude Code, Codex, Cursor, or OpenCode. Then you describe the system in the chat in one line. Archify turns that line into a single HTML file you can open, click through, and send to anyone. If you point your agent at an existing codebase, it reads the code and Archify maps how the pieces connect. I liked five things about it. 1. It makes five kinds of diagrams, including system maps and step-by-step workflows. 2. You can click any piece and trace what connects to it. 3. It checks the layout before it hands the diagram over, so arrows don't pile up and labels don't overlap. 4. It has dark and light themes and exports to PNG, SVG, or a short video. 5. You keep editing in plain chat, with requests like "add Redis" or "highlight the rollback path." You don't need a codebase to use it. A description in the chat is enough.
0:12

Stop manually making flowcharts. Try this GitHub skill with Claude Code. I found an open-source tool that turns a plain description of a software system into a clean, interactive diagram. It's called Archify, and it has more than 66,000 stars on GitHub. You add it as a skill to an AI coding agent like Claude Code, Codex, Cursor, or OpenCode. Then you describe the system in the chat in one line. Archify turns that line into a single HTML file you can open, click through, and send to anyone. If you point your agent at an existing codebase, it reads the code and Archify maps how the pieces connect. I liked five things about it. 1. It makes five kinds of diagrams, including system maps and step-by-step workflows. 2. You can click any piece and trace what connects to it. 3. It checks the layout before it hands the diagram over, so arrows don't pile up and labels don't overlap. 4. It has dark and light themes and exports to PNG, SVG, or a short video. 5. You keep editing in plain chat, with requests like "add Redis" or "highlight the rollback path." You don't need a codebase to use it. A description in the chat is enough.

Alex Veremeyenko

61,928 görüntüleme • 25 gün önce

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.
0:14

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

Akshay 🚀

52,426 görüntüleme • 7 ay önce

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this
0:16

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

Ridark

7,028,225 görüntüleme • 3 ay önce

✨ I open sourced my first Chrome extension 🚀 SuperLevels I vibe coded it to replace all my Chrome extensions that are increasingly being bought up by spyware and malware companies who sell your data or worse hack your accounts and steal your stuff/money/data, which I'd call one of the top security risks right now For example: Chrome extensions can read your cookies or localStorage data, including session tokens, then login to your web or email accounts and hack you, they can inject code into any site to pull data form any site you browse, then break into your crypto accounts, drain your wallets, and selling your browsing history to ad companies, but that'd actually be the most favorable thing to happen of all these! Chrome extensions are just very very very unsafe So I coded my own, that I can trust because I made it, and I can read the source code: my extension is called 🚀SuperLevels and has all the features that the Chrome extensions I used to use have but all built into one safe one The cool thing is it's 100% open source and free, and you can audit the code first with AI yourself before installing it, and then if you do install it, customize it to your liking again with AI It has these features that improve my daily workflow while browsing the web: 🚮 Tab Cleaner Automatically closes inactive tabs after a configurable timeout (default: 5 minutes). Set excluded hosts to keep important tabs alive. View and re-open recently closed tabs. 🍪 Cookie Editor Full cookie manager for the current site. View, edit, add, and delete cookies. Export cookies as JSON. Expand any cookie to see and modify all fields including domain, path, SameSite, secure, and httpOnly flags. 🔀 Redirect Tracer See every redirect hop your browser took to reach the current page. Shows status codes (301, 302, 307, etc.) with a visual chain. Copy the full redirect chain to clipboard. 🌙 Dark Mode Instant dark mode for any website using CSS filter inversion. Adjustable brightness. Toggle per-site or globally. Images and videos are automatically re-inverted so they look normal. 𝕏 X Dim Mode Custom dim theme for X/Twitter with 7 color palettes: Dim, Slate, Jade, Plum, Dusk, Ember, or a custom hue. Live preview in the popup. ⚡ JS Toggle Disable JavaScript per-site with one click. Useful for debugging, reading articles without popups, or testing progressive enhancement. Page reloads automatically. 🚫 GDPR Cookie Consent Dismisser Auto-hides and auto-clicks cookie consent banners. Supports OneTrust, CookieBot, Didomi, Quantcast, GDPR plugins, and dozens more frameworks. Toggle off if a site breaks. 🎨 Live CSS Editor Write custom CSS for any website, applied in real-time as you type. Saved per-domain. Supports tab key for indentation. 📺 YouTube Unhook Removes YouTube distractions: no homepage feed, no sidebar suggestions, no end screen overlays, no Shorts. Search still works — just no algorithmic recommendations. 🎵 Music Recognizer Shazam-like music identification for any tab. Captures 10 seconds of audio and identifies the song via ACRCloud (free signup, bring your own API key). Results link to YouTube. History of recognized songs. 🖼 Picture-in-Picture Pop the largest video on the current tab into a floating PiP window with one click. 🗺 Google Maps Links Re-adds clickable Maps links and map preview cards to Google Search results. 🖼 View Image Adds a "View Image" button back to Google Images, linking directly to the full-size original image. {} JSON Formatter Auto-detects pure JSON response pages and formats them with syntax highlighting, collapsible sections, and a dark theme. Copy or view raw with one click. Never triggers on regular HTML pages.
0:17

✨ I open sourced my first Chrome extension 🚀 SuperLevels I vibe coded it to replace all my Chrome extensions that are increasingly being bought up by spyware and malware companies who sell your data or worse hack your accounts and steal your stuff/money/data, which I'd call one of the top security risks right now For example: Chrome extensions can read your cookies or localStorage data, including session tokens, then login to your web or email accounts and hack you, they can inject code into any site to pull data form any site you browse, then break into your crypto accounts, drain your wallets, and selling your browsing history to ad companies, but that'd actually be the most favorable thing to happen of all these! Chrome extensions are just very very very unsafe So I coded my own, that I can trust because I made it, and I can read the source code: my extension is called 🚀SuperLevels and has all the features that the Chrome extensions I used to use have but all built into one safe one The cool thing is it's 100% open source and free, and you can audit the code first with AI yourself before installing it, and then if you do install it, customize it to your liking again with AI It has these features that improve my daily workflow while browsing the web: 🚮 Tab Cleaner Automatically closes inactive tabs after a configurable timeout (default: 5 minutes). Set excluded hosts to keep important tabs alive. View and re-open recently closed tabs. 🍪 Cookie Editor Full cookie manager for the current site. View, edit, add, and delete cookies. Export cookies as JSON. Expand any cookie to see and modify all fields including domain, path, SameSite, secure, and httpOnly flags. 🔀 Redirect Tracer See every redirect hop your browser took to reach the current page. Shows status codes (301, 302, 307, etc.) with a visual chain. Copy the full redirect chain to clipboard. 🌙 Dark Mode Instant dark mode for any website using CSS filter inversion. Adjustable brightness. Toggle per-site or globally. Images and videos are automatically re-inverted so they look normal. 𝕏 X Dim Mode Custom dim theme for X/Twitter with 7 color palettes: Dim, Slate, Jade, Plum, Dusk, Ember, or a custom hue. Live preview in the popup. ⚡ JS Toggle Disable JavaScript per-site with one click. Useful for debugging, reading articles without popups, or testing progressive enhancement. Page reloads automatically. 🚫 GDPR Cookie Consent Dismisser Auto-hides and auto-clicks cookie consent banners. Supports OneTrust, CookieBot, Didomi, Quantcast, GDPR plugins, and dozens more frameworks. Toggle off if a site breaks. 🎨 Live CSS Editor Write custom CSS for any website, applied in real-time as you type. Saved per-domain. Supports tab key for indentation. 📺 YouTube Unhook Removes YouTube distractions: no homepage feed, no sidebar suggestions, no end screen overlays, no Shorts. Search still works — just no algorithmic recommendations. 🎵 Music Recognizer Shazam-like music identification for any tab. Captures 10 seconds of audio and identifies the song via ACRCloud (free signup, bring your own API key). Results link to YouTube. History of recognized songs. 🖼 Picture-in-Picture Pop the largest video on the current tab into a floating PiP window with one click. 🗺 Google Maps Links Re-adds clickable Maps links and map preview cards to Google Search results. 🖼 View Image Adds a "View Image" button back to Google Images, linking directly to the full-size original image. {} JSON Formatter Auto-detects pure JSON response pages and formats them with syntax highlighting, collapsible sections, and a dark theme. Copy or view raw with one click. Never triggers on regular HTML pages.

@levelsio

260,841 görüntüleme • 5 ay önce

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.
0:10

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.

Rohan Paul

178,460 görüntüleme • 1 yıl önce

There’s been two papers released in the past couple months, one by Google and one by NVIDIA, that argue that ordering the documents retrieved by RAG systems can enhance performance. However, they both give two different strategies on HOW these documents should be ordered 🤔 Both papers agree on two main points: 1️⃣ There’s a fundamental issue in RAG - as more documents are retrieved, more irrelevant context (e.g., hard negatives) are introduced, which leads to confusion for the LLM and eventually degrades the quality of the generated output. This is called an inverted-U performance curve. 2️⃣ Ordering the retrieved documents is a key lever for optimizing RAG performance. Google Cloud researchers proposed ordering results based on relevance scores: The authors in this paper argue for relevance-based reordering, or ordering the retrieved chunks based on their similarity scores, so the most relevant documents are at the beginning and the end of the inputs to counter the “lost in the middle” effect. NVIDIA researchers proposed ordering results based on the original sequence of document chunks: The authors of this paper argue for Order-Preserving Reordering, or Order-Preserve RAG (OP-RAG), to maintain the logically coherent content flow of the document. So they preserved the original order of retrieved document chunks in the source text, instead of ranking them by relevance scores. So which one is right? It probably depends on the specific use case and dataset - relevance-based reordering could perform better in tasks where you need fast access to the most critical information (e.g., fact retrieval, QA systems), while order-preserving RAG might be better where you need to understand the sequential structure of information (e.g., narrative or legal documents). There are still so many uncertainties in AI - we don’t actually know what we’re doing, and it takes awhile to figure out the best strategies for most things! Excited to see more research about this.
0:20

There’s been two papers released in the past couple months, one by Google and one by NVIDIA, that argue that ordering the documents retrieved by RAG systems can enhance performance. However, they both give two different strategies on HOW these documents should be ordered 🤔 Both papers agree on two main points: 1️⃣ There’s a fundamental issue in RAG - as more documents are retrieved, more irrelevant context (e.g., hard negatives) are introduced, which leads to confusion for the LLM and eventually degrades the quality of the generated output. This is called an inverted-U performance curve. 2️⃣ Ordering the retrieved documents is a key lever for optimizing RAG performance. Google Cloud researchers proposed ordering results based on relevance scores: The authors in this paper argue for relevance-based reordering, or ordering the retrieved chunks based on their similarity scores, so the most relevant documents are at the beginning and the end of the inputs to counter the “lost in the middle” effect. NVIDIA researchers proposed ordering results based on the original sequence of document chunks: The authors of this paper argue for Order-Preserving Reordering, or Order-Preserve RAG (OP-RAG), to maintain the logically coherent content flow of the document. So they preserved the original order of retrieved document chunks in the source text, instead of ranking them by relevance scores. So which one is right? It probably depends on the specific use case and dataset - relevance-based reordering could perform better in tasks where you need fast access to the most critical information (e.g., fact retrieval, QA systems), while order-preserving RAG might be better where you need to understand the sequential structure of information (e.g., narrative or legal documents). There are still so many uncertainties in AI - we don’t actually know what we’re doing, and it takes awhile to figure out the best strategies for most things! Excited to see more research about this.

Victoria Slocum

15,333 görüntüleme • 1 yıl önce

Big win for open-source LLMs! DeepSeek V4 Pro holds the top open-weights score on SWE-bench Verified, in the GPT-5.5 range. GLM 5.2 leads the open-weight intelligence index and sits near the closed frontier on long-horizon coding. But this leaderboard number is a weak proxy for real performance. It comes from one task set, run through one harness, served at one precision. The same weights can even score differently across providers, since many hosts quantize activations to fp8 and drift the model off its reference weights. Real performance is determined based on whether a model can read a repo, make coordinated edits across files, run the tests, and recover when one breaks. By that measure, the top open models hold up, but only inside the right harness. The teams that actually put DeepSeek V4 into production pipelines as a frontier substitute got there through the harness they built around the model, not by picking a stronger model. If you want to see this in practice, Cline (64k+ stars) has actually built that harness around open models, tuned so they run at production quality. And it's tuned so that these LLMs can run at production quality, with plan and act modes, checkpoints, and terminal feedback. ClinePass is the new access layer on top of it. It runs a curated set of those models inside Cline, narrowed to the ones tested for coding-agent use, with 2 to 5x the standard rate limits and no separate provider accounts, keys, or billing to track. The video below shows the setup, and I worked with the team to put this together. It runs alongside custom keys and local models as well, not in place of them.
0:14

Big win for open-source LLMs! DeepSeek V4 Pro holds the top open-weights score on SWE-bench Verified, in the GPT-5.5 range. GLM 5.2 leads the open-weight intelligence index and sits near the closed frontier on long-horizon coding. But this leaderboard number is a weak proxy for real performance. It comes from one task set, run through one harness, served at one precision. The same weights can even score differently across providers, since many hosts quantize activations to fp8 and drift the model off its reference weights. Real performance is determined based on whether a model can read a repo, make coordinated edits across files, run the tests, and recover when one breaks. By that measure, the top open models hold up, but only inside the right harness. The teams that actually put DeepSeek V4 into production pipelines as a frontier substitute got there through the harness they built around the model, not by picking a stronger model. If you want to see this in practice, Cline (64k+ stars) has actually built that harness around open models, tuned so they run at production quality. And it's tuned so that these LLMs can run at production quality, with plan and act modes, checkpoints, and terminal feedback. ClinePass is the new access layer on top of it. It runs a curated set of those models inside Cline, narrowed to the ones tested for coding-agent use, with 2 to 5x the standard rate limits and no separate provider accounts, keys, or billing to track. The video below shows the setup, and I worked with the team to put this together. It runs alongside custom keys and local models as well, not in place of them.

Avi Chawla

44,124 görüntüleme • 3 ay önce

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.
0:16

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

elvis

11,303 görüntüleme • 1 ay önce

Turn any open LLM into a Jev-style model: Researchers just open-sourced AnyJev, a Python library that extracts typed choices, yes/no judgments, scores, and probabilities from causal LLMs. Beyond its raw baseline, AnyJev offers three levels depending on how much labeled data and calibration you need: - L0 requires no labels. It rotates the answer options to reduce position bias, but its probabilities remain uncalibrated. - L1 uses 100-500 labeled examples per question to calibrate those probabilities through temperature scaling. It improves confidence estimates without changing the answer ranking. - L2 uses 100-300 labels to fit a closed-form head on an intermediate hidden state. It leaves model weights untouched and can stop inference before the full forward pass completes. The main constraint is model access. AnyJev requires access to logits or hidden states, so it is built for open models. L2 heads are also specific to a model and question. It is compatible with several open causal LLMs. Repo: (don't forget to star it ⭐ ) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.
0:11

Turn any open LLM into a Jev-style model: Researchers just open-sourced AnyJev, a Python library that extracts typed choices, yes/no judgments, scores, and probabilities from causal LLMs. Beyond its raw baseline, AnyJev offers three levels depending on how much labeled data and calibration you need: - L0 requires no labels. It rotates the answer options to reduce position bias, but its probabilities remain uncalibrated. - L1 uses 100-500 labeled examples per question to calibrate those probabilities through temperature scaling. It improves confidence estimates without changing the answer ranking. - L2 uses 100-300 labels to fit a closed-form head on an intermediate hidden state. It leaves model weights untouched and can stop inference before the full forward pass completes. The main constraint is model access. AnyJev requires access to logits or hidden states, so it is built for open models. L2 heads are also specific to a model and question. It is compatible with several open causal LLMs. Repo: (don't forget to star it ⭐ ) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.

Avi Chawla

55,843 görüntüleme • 19 gün önce

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑
0:11

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑

Vercel Developers

965,171 görüntüleme • 1 ay önce

Build AI agents on a time-aware knowledge graph! Utopia is an open-source knowledge system that turns documents, databases, and connected sources into a temporal graph your agents can reason over. Most RAG systems are optimized for one question: what is relevant right now? That works until the underlying knowledge changes. A customer contract gets updated. A project owner changes. A policy is revised. A previous fact may no longer be true, but simply overwriting it means the system loses the history behind that change. Utopia handles this with a bitemporal knowledge graph. Each fact can track both when it was true in the real world and when the system learned about it. When something changes, the old fact is preserved instead of silently disappearing. That means an agent can reason about questions like: • What is true now? • What was true three months ago? • When did this information change? • What evidence was the conclusion based on? The graph is also ontology-aware, so documents are represented as entities, facts, and relationships instead of only chunks and embeddings. That gives the system more structure for reasoning across relationships, resolving entities, detecting conflicting facts, and deriving new information through explicit rules. Key capabilities: • Bitemporal knowledge graph for tracking how facts change over time • Provenance on facts so agents can trace where information came from • Conflict detection instead of silently overwriting contradictory information • Ontology-based reasoning across entities, relationships, and derived facts • Hybrid retrieval across full-text search, vector search, and graph traversal • MCP and agentic RAG support for exposing the knowledge layer directly to agents The interesting part is that this turns the knowledge base into more than a retrieval system. Instead of only finding relevant information, an agent can reason over what changed, what is still valid, how facts are connected, and where each conclusion came from. 100% open source. I've shared the GitHub repo in the comments!
0:16

Build AI agents on a time-aware knowledge graph! Utopia is an open-source knowledge system that turns documents, databases, and connected sources into a temporal graph your agents can reason over. Most RAG systems are optimized for one question: what is relevant right now? That works until the underlying knowledge changes. A customer contract gets updated. A project owner changes. A policy is revised. A previous fact may no longer be true, but simply overwriting it means the system loses the history behind that change. Utopia handles this with a bitemporal knowledge graph. Each fact can track both when it was true in the real world and when the system learned about it. When something changes, the old fact is preserved instead of silently disappearing. That means an agent can reason about questions like: • What is true now? • What was true three months ago? • When did this information change? • What evidence was the conclusion based on? The graph is also ontology-aware, so documents are represented as entities, facts, and relationships instead of only chunks and embeddings. That gives the system more structure for reasoning across relationships, resolving entities, detecting conflicting facts, and deriving new information through explicit rules. Key capabilities: • Bitemporal knowledge graph for tracking how facts change over time • Provenance on facts so agents can trace where information came from • Conflict detection instead of silently overwriting contradictory information • Ontology-based reasoning across entities, relationships, and derived facts • Hybrid retrieval across full-text search, vector search, and graph traversal • MCP and agentic RAG support for exposing the knowledge layer directly to agents The interesting part is that this turns the knowledge base into more than a retrieval system. Instead of only finding relevant information, an agent can reason over what changed, what is still valid, how facts are connected, and where each conclusion came from. 100% open source. I've shared the GitHub repo in the comments!

Sumanth

16,653 görüntüleme • 1 ay önce

Big moment for Postgres! Search has always been Postgres' weak spot, and everyone just accepted it. If you needed a real relevance-ranked keyword search, the default answer was to spin up Elasticsearch or add Algolia and deal with the data sync headaches forever. The problem isn't that Postgres can't do text search. It can. But the built-in `ts_rank` function uses a basic term frequency algorithm that doesn't come close to what modern search engines deliver. So teams end up: - Running a separate Elasticsearch cluster just for search - Building sync pipelines that inevitably drift out of consistency - Paying for managed search services that charge per query - Accepting mediocre search relevance because "good enough" ships faster But this is actually a solvable problem. You can realistically bring industry-standard search ranking directly into Postgres, which eliminates the need for external infra entirely. This exact solution is now available with the newly open-sourced pg_textsearch by Tiger Data - Creators of TimescaleDB, a Postgres extension that brings true BM25 relevance ranking into the database. BM25 is the algorithm behind Elasticsearch, Lucene, and most modern search engines. Now it runs natively in Postgres. Here's what pg_textsearch enables: - True BM25 ranking with configurable parameters (the same algorithm powering production search systems) - Simple SQL syntax: `ORDER BY content 'search terms'` - Works with Postgres text search configurations for multiple languages - Pairs naturally with pgvector for hybrid keyword + semantic search That last point matters a lot for RAG apps. The video below shows this in action, and I worked with the team to put this together. You can now do hybrid retrieval (combining keyword matching with vector similarity) in a single database, without stitching together multiple systems. The syntax is clean enough that you can add relevance-ranked search to existing queries in minutes. pg_textsearch is fully open-source under the PostgreSQL license. You can find a link to their GitHub repo in the next tweet.
0:10

Big moment for Postgres! Search has always been Postgres' weak spot, and everyone just accepted it. If you needed a real relevance-ranked keyword search, the default answer was to spin up Elasticsearch or add Algolia and deal with the data sync headaches forever. The problem isn't that Postgres can't do text search. It can. But the built-in `ts_rank` function uses a basic term frequency algorithm that doesn't come close to what modern search engines deliver. So teams end up: - Running a separate Elasticsearch cluster just for search - Building sync pipelines that inevitably drift out of consistency - Paying for managed search services that charge per query - Accepting mediocre search relevance because "good enough" ships faster But this is actually a solvable problem. You can realistically bring industry-standard search ranking directly into Postgres, which eliminates the need for external infra entirely. This exact solution is now available with the newly open-sourced pg_textsearch by Tiger Data - Creators of TimescaleDB, a Postgres extension that brings true BM25 relevance ranking into the database. BM25 is the algorithm behind Elasticsearch, Lucene, and most modern search engines. Now it runs natively in Postgres. Here's what pg_textsearch enables: - True BM25 ranking with configurable parameters (the same algorithm powering production search systems) - Simple SQL syntax: `ORDER BY content 'search terms'` - Works with Postgres text search configurations for multiple languages - Pairs naturally with pgvector for hybrid keyword + semantic search That last point matters a lot for RAG apps. The video below shows this in action, and I worked with the team to put this together. You can now do hybrid retrieval (combining keyword matching with vector similarity) in a single database, without stitching together multiple systems. The syntax is clean enough that you can add relevance-ranked search to existing queries in minutes. pg_textsearch is fully open-source under the PostgreSQL license. You can find a link to their GitHub repo in the next tweet.

Akshay 🚀

215,785 görüntüleme • 8 ay önce

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.
0:11

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 görüntüleme • 7 ay önce

Goldman pays $27,000 per seat for a Bloomberg Terminal. I found 10 open source tools on GitHub that replicate almost all of it for free. Retail investors have never had this much firepower. Bookmark & Repost this one: 1. OpenBB Stocks, options, crypto, forex, and macro data in one research platform. Build your own dashboards, reports, and AI analysts on top of it. The OG of open source finance. 50K+ stars. 2. FinceptTerminal A full financial terminal: global market data, advanced charts, economic indicators, portfolio analysis, and AI research tools. Windows, Mac, and Linux. 3. Neuberg 516 drag-and-drop panels covering equities, bonds, commodities, currencies, credit, and macro. Even connects to Alpaca, Hyperliquid, and Polymarket so you can trade from the terminal itself. 4. Qlib (by Microsoft) An open source AI platform for quant investing. Train ML models, discover signals, backtest strategies, and build portfolios with the same workflow a quant desk uses. 5. FinRobot An AI equity research team on your laptop. Its agents read financial statements, build DCF valuations, debate bull vs bear cases, and generate full investment reports. 6. EdgarTools Turns the SEC database into something humans can actually use. Pull 10-Ks, 10-Qs, insider trades, executive pay, and hedge fund holdings going back to 1994. 7. LEAN (by QuantConnect) An institutional-grade engine for trading algorithms. Write strategies in Python or C#, backtest on decades of data, then connect to real brokers and go live. 8. FinanceToolkit 200+ financial ratios, valuation models, risk metrics, and economic indicators. Works on stocks, ETFs, options, currencies, commodities, and crypto from Python. 9. Ghostfolio A private wealth dashboard for stocks, ETFs, and crypto across all your accounts. Performance, allocation, diversification. Your data never leaves your machine. 10. OpenTerminalUI A self-hosted trading terminal: pro charts, screeners, options chains with live Greeks, portfolio optimization, backtesting, and an AI research agent. Runs entirely on your own hardware. Bloomberg spent 40 years building a $27,000/year moat. Open source is draining it one repo at a time. The software is free. Some live data feeds need your own API keys, but the barrier is now effort, not money. If you want the exact workflows we use to stack these tools with AI, join the AIBullss Discord:
0:13

Goldman pays $27,000 per seat for a Bloomberg Terminal. I found 10 open source tools on GitHub that replicate almost all of it for free. Retail investors have never had this much firepower. Bookmark & Repost this one: 1. OpenBB Stocks, options, crypto, forex, and macro data in one research platform. Build your own dashboards, reports, and AI analysts on top of it. The OG of open source finance. 50K+ stars. 2. FinceptTerminal A full financial terminal: global market data, advanced charts, economic indicators, portfolio analysis, and AI research tools. Windows, Mac, and Linux. 3. Neuberg 516 drag-and-drop panels covering equities, bonds, commodities, currencies, credit, and macro. Even connects to Alpaca, Hyperliquid, and Polymarket so you can trade from the terminal itself. 4. Qlib (by Microsoft) An open source AI platform for quant investing. Train ML models, discover signals, backtest strategies, and build portfolios with the same workflow a quant desk uses. 5. FinRobot An AI equity research team on your laptop. Its agents read financial statements, build DCF valuations, debate bull vs bear cases, and generate full investment reports. 6. EdgarTools Turns the SEC database into something humans can actually use. Pull 10-Ks, 10-Qs, insider trades, executive pay, and hedge fund holdings going back to 1994. 7. LEAN (by QuantConnect) An institutional-grade engine for trading algorithms. Write strategies in Python or C#, backtest on decades of data, then connect to real brokers and go live. 8. FinanceToolkit 200+ financial ratios, valuation models, risk metrics, and economic indicators. Works on stocks, ETFs, options, currencies, commodities, and crypto from Python. 9. Ghostfolio A private wealth dashboard for stocks, ETFs, and crypto across all your accounts. Performance, allocation, diversification. Your data never leaves your machine. 10. OpenTerminalUI A self-hosted trading terminal: pro charts, screeners, options chains with live Greeks, portfolio optimization, backtesting, and an AI research agent. Runs entirely on your own hardware. Bloomberg spent 40 years building a $27,000/year moat. Open source is draining it one repo at a time. The software is free. Some live data feeds need your own API keys, but the barrier is now effort, not money. If you want the exact workflows we use to stack these tools with AI, join the AIBullss Discord:

AlphaCartel

22,101 görüntüleme • 2 ay önce

I just vibe-coded a Shopify Reviews Scraper that swipes all your competitors' customer reviews instantly. 🤯 Paste any competitor's product URL → pull every review in under 30 seconds → export to CSV. Built 100% in Codex. Perfect for brands and agencies who want to mine competitor voice-of-customer data at scale and turn it into winning ad creative. Here's how it works: → Drop a Shopify product URL into the tool → Set your review limit (50, 100, 500+) → Hit scrape — it launches a browser, finds the review widget, pulls every review → Export clean rows: rating, body, author, date → Feed the CSV to Claude and ask "what do customers love and hate about this product" → Turn the output into ad angles, hooks, and headlines No more paying $99/mo for clunky review scraping SaaS that locks you behind credits. What you get: - Any Shopify store's reviews in 30 seconds - Clean structured data (rating, body, author, date) - CSV or JSON export — drops straight into Sheets or an LLM - Unlimited scrapes, no per-review fees - A voice-of-customer firehose you can turn into ad creative on demand This is essentially a competitor review intelligence engine in a box. I'm giving away the full GitHub repo so you can clone it and run it yourself for free. Want the repo? > Like this post > Comment "SCRAPE" And I'll send it over (must be following so I can DM)
0:14

I just vibe-coded a Shopify Reviews Scraper that swipes all your competitors' customer reviews instantly. 🤯 Paste any competitor's product URL → pull every review in under 30 seconds → export to CSV. Built 100% in Codex. Perfect for brands and agencies who want to mine competitor voice-of-customer data at scale and turn it into winning ad creative. Here's how it works: → Drop a Shopify product URL into the tool → Set your review limit (50, 100, 500+) → Hit scrape — it launches a browser, finds the review widget, pulls every review → Export clean rows: rating, body, author, date → Feed the CSV to Claude and ask "what do customers love and hate about this product" → Turn the output into ad angles, hooks, and headlines No more paying $99/mo for clunky review scraping SaaS that locks you behind credits. What you get: - Any Shopify store's reviews in 30 seconds - Clean structured data (rating, body, author, date) - CSV or JSON export — drops straight into Sheets or an LLM - Unlimited scrapes, no per-review fees - A voice-of-customer firehose you can turn into ad creative on demand This is essentially a competitor review intelligence engine in a box. I'm giving away the full GitHub repo so you can clone it and run it yourself for free. Want the repo? > Like this post > Comment "SCRAPE" And I'll send it over (must be following so I can DM)

Mike Futia

29,996 görüntüleme • 5 ay önce

INVESTOR DECKS ARE OFFICIALLY A ONE-PROMPT PROBLEM NOW goes from scattered brand notes and market research straight to an investor ready deck - eliminating manual slide layout, manual chart building, and manual re formatting between tools Here is the exact stack: Claude Design Canvas - reads a brand concept doc and a research outline, builds each slide type with real visual reasoning, not text dropped into a template Live Research Layer - for skills that support it, runs an actual web search per prompt, structures a narrative arc from current data instead of guessing at market size Design-System Ingestion - feed it a clean codebase or existing brand files, Claude infers your grid, type scale, and color system automatically instead of starting from a blank canvas Multi format Export - PPTX, PDF, HTML, or straight into Google Slides, so the deck opens correctly wherever the investor actually opens it Core advantage: set up a Project once with your colors, fonts, and style guide - every deck generated after that follows your brand automatically, no re-uploading brand assets slide by slide honest limit worth knowing: HTML to PPTX export is lossy text can flatten to images, fonts substitute, master slides drop If the deck's final home is PowerPoint, budget one manual pass to catch what didn't survive the conversion Pass a brand doc and a research outline Claude structures the narrative arc, builds every slide, and exports to whatever format the round actually needs zero blank canvas, zero manual chart rebuilding full below
0:15

INVESTOR DECKS ARE OFFICIALLY A ONE-PROMPT PROBLEM NOW goes from scattered brand notes and market research straight to an investor ready deck - eliminating manual slide layout, manual chart building, and manual re formatting between tools Here is the exact stack: Claude Design Canvas - reads a brand concept doc and a research outline, builds each slide type with real visual reasoning, not text dropped into a template Live Research Layer - for skills that support it, runs an actual web search per prompt, structures a narrative arc from current data instead of guessing at market size Design-System Ingestion - feed it a clean codebase or existing brand files, Claude infers your grid, type scale, and color system automatically instead of starting from a blank canvas Multi format Export - PPTX, PDF, HTML, or straight into Google Slides, so the deck opens correctly wherever the investor actually opens it Core advantage: set up a Project once with your colors, fonts, and style guide - every deck generated after that follows your brand automatically, no re-uploading brand assets slide by slide honest limit worth knowing: HTML to PPTX export is lossy text can flatten to images, fonts substitute, master slides drop If the deck's final home is PowerPoint, budget one manual pass to catch what didn't survive the conversion Pass a brand doc and a research outline Claude structures the narrative arc, builds every slide, and exports to whatever format the round actually needs zero blank canvas, zero manual chart rebuilding full below

YARD

32,780 görüntüleme • 1 ay önce

NanoBanana 2 just made your static ad agency obsolete. And I just open sourced the entire tool. Drop your product page URL. It pulls your logos, product images, fonts, colors, and brand voice automatically. Builds a full brand guide for you. Then generates ad creatives at scale using nearly 4,000 high-performing ad templates across 8 niches. It dynamically matches the best templates to your brand and brief. Here's what makes it different: → Instant resizing Get any ad in 1x1, 4x5, 9x16 with one click. No regeneration. No broken text. → Highlight-to-edit See an issue? Highlight the area and tell it what to fix. → Multiple brand profiles Run different brands or segments from one tool. → Auto persona building from real customer reviews → Multiple QC loops on briefs and final assets Catches AI-isms before you do. → Upload your own templates or use ours Runs locally. Just needs your Claude and Google API keys. This is the lite version of what we use internally. You get the full finished tool AND the open source code to make it your own. Creatives still design the system, this handles iteration and scale. Want a copy to download? 1. Like this post 2. Comment "AI" Will DM you the tool along with a tutorial shortly after.
0:13

NanoBanana 2 just made your static ad agency obsolete. And I just open sourced the entire tool. Drop your product page URL. It pulls your logos, product images, fonts, colors, and brand voice automatically. Builds a full brand guide for you. Then generates ad creatives at scale using nearly 4,000 high-performing ad templates across 8 niches. It dynamically matches the best templates to your brand and brief. Here's what makes it different: → Instant resizing Get any ad in 1x1, 4x5, 9x16 with one click. No regeneration. No broken text. → Highlight-to-edit See an issue? Highlight the area and tell it what to fix. → Multiple brand profiles Run different brands or segments from one tool. → Auto persona building from real customer reviews → Multiple QC loops on briefs and final assets Catches AI-isms before you do. → Upload your own templates or use ours Runs locally. Just needs your Claude and Google API keys. This is the lite version of what we use internally. You get the full finished tool AND the open source code to make it your own. Creatives still design the system, this handles iteration and scale. Want a copy to download? 1. Like this post 2. Comment "AI" Will DM you the tool along with a tutorial shortly after.

Peter Quadrel

293,472 görüntüleme • 7 ay önce

Introducing the BIOS API: Turn Your Agent Into a Research Scientist Built to: 🦞 Add biomedical workflows to your OpenClaw🦞 agent 🧠 Create research or health agents w/ on-demand scientific intelligence 🧪 Pay per query via x402 on Base Any agent or app can now tap into the BIOS AI Scientist, plugging BIOS into the broader agent economy. What is BIOS? BIOS is an AI Scientist designed to handle complex biomedical research by orchestrating specialized scientific subagents. Ranked #1 on the leading bioinformatics benchmark, BIOS is already being used by 1,000+ researchers and labs to build new drugs and medicines. An Agentic Economy for Science AI agents have proven they can form multi-billion dollar ecosystems. BIOS applies the same primitives to drug discovery pipelines and health. Instead of coding bots and personal AI assistants, think research agent swarms running on a modern scientific stack. Imagine an OpenClaw agent built for longevity: It scans new literature daily, generates novel compound hypotheses through BIOS, designs validation workflows, and routes the best candidates to wet-lab funding - all programmatically. Connect it with an agent for microbiome health, enabling agent “backrooms” that autonomously surface cross-disciplinary insights. Micropayments for Scientific Work via x402 Each query triggers payment routing to BIOS and whichever subagents contribute to a response. The best agents earn. Usage settles instantly across contributing sources. The goal is pay-per-task science: paying for a CRISPR assay result, licensing a genomic dataset, or triggering a clinical data query - all settled in seconds via USDC. No purchase orders. No grant bureaucracy. No middlemen. x402 is the payment rail that makes agent-to-lab commerce possible - letting capital and cognition route themselves to the highest-signal science. What Will You Build? Drug discovery copilots? Longevity scouts? Automated literature monitors? Scientific due diligence agents? We’ll soon share the first implementations of the BIOS API. Stay tuned and see below for instructions on generating an API key for your agent or use-case.
0:13

Introducing the BIOS API: Turn Your Agent Into a Research Scientist Built to: 🦞 Add biomedical workflows to your OpenClaw🦞 agent 🧠 Create research or health agents w/ on-demand scientific intelligence 🧪 Pay per query via x402 on Base Any agent or app can now tap into the BIOS AI Scientist, plugging BIOS into the broader agent economy. What is BIOS? BIOS is an AI Scientist designed to handle complex biomedical research by orchestrating specialized scientific subagents. Ranked #1 on the leading bioinformatics benchmark, BIOS is already being used by 1,000+ researchers and labs to build new drugs and medicines. An Agentic Economy for Science AI agents have proven they can form multi-billion dollar ecosystems. BIOS applies the same primitives to drug discovery pipelines and health. Instead of coding bots and personal AI assistants, think research agent swarms running on a modern scientific stack. Imagine an OpenClaw agent built for longevity: It scans new literature daily, generates novel compound hypotheses through BIOS, designs validation workflows, and routes the best candidates to wet-lab funding - all programmatically. Connect it with an agent for microbiome health, enabling agent “backrooms” that autonomously surface cross-disciplinary insights. Micropayments for Scientific Work via x402 Each query triggers payment routing to BIOS and whichever subagents contribute to a response. The best agents earn. Usage settles instantly across contributing sources. The goal is pay-per-task science: paying for a CRISPR assay result, licensing a genomic dataset, or triggering a clinical data query - all settled in seconds via USDC. No purchase orders. No grant bureaucracy. No middlemen. x402 is the payment rail that makes agent-to-lab commerce possible - letting capital and cognition route themselves to the highest-signal science. What Will You Build? Drug discovery copilots? Longevity scouts? Automated literature monitors? Scientific due diligence agents? We’ll soon share the first implementations of the BIOS API. Stay tuned and see below for instructions on generating an API key for your agent or use-case.

Bio Protocol

25,957 görüntüleme • 7 ay önce