Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Semantic search alone doesn't cut it. Neither does brute-force grep. Agents need both. Today we're shipping the Retrieval Harness in LlamaParse Index: semantic search, server-side grep, and file-level navigation working together in a single agent reasoning loop. 🦙🌤️ Grep a file, list what's in an index, read past a... show more

LlamaIndex 🦙

117,203 subscribers

29,181 views • 3 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

We've created a comprehensive Retrieval Harness for modern agentic retrieval in 2026. The harness provides a persistent data pipeline that can connect to a data source, index and update a large knowledge base, and expose a broad set of tools akin to filesystem operations (semantic/keyword search, regex grep, file search, read). You can plug this into any of your agents to let them autonomously crawl an arbitrary knowledge base to solve a task with any complexity. Check out our reference implementation: LlamaParse:

We've created a comprehensive Retrieval Harness for modern agentic retrieval in 2026. The harness provides a persistent data pipeline that can connect to a data source, index and update a large knowledge base, and expose a broad set of tools akin to filesystem operations (semantic/keyword search, regex grep, file search, read). You can plug this into any of your agents to let them autonomously crawl an arbitrary knowledge base to solve a task with any complexity. Check out our reference implementation: LlamaParse:

Jerry Liu

57,248 views • 3 months ago

Give Claude Code a semantic filesystem 🗃️🛠️ Giving Claude Code access to the right CLI tools over your filesystem turns it into a general agent capable of automating far more knowledge work beyond code - it can do dynamic financial/legal/medical/technical/backoffice analysis over any subset of documents. With our latest release of semtools 💫, you can now manually or *agentically* create a persistent workspace over any subset of files. This gives Claude Code the ability to get blazing-fast, local semantic search over any data, while still allowing it to chain with commands like grep/cat/etc. so that it can load in dynamic context instead of naive top-k vector search. The coding agent can dynamically index data and use those indexes, instead of having to rebuild it every time. So you get the benefits of fast search along with agentic reasoning over CLI tools mentioned above. Come check it out!

Give Claude Code a semantic filesystem 🗃️🛠️ Giving Claude Code access to the right CLI tools over your filesystem turns it into a general agent capable of automating far more knowledge work beyond code - it can do dynamic financial/legal/medical/technical/backoffice analysis over any subset of documents. With our latest release of semtools 💫, you can now manually or agentically create a persistent workspace over any subset of files. This gives Claude Code the ability to get blazing-fast, local semantic search over any data, while still allowing it to chain with commands like grep/cat/etc. so that it can load in dynamic context instead of naive top-k vector search. The coding agent can dynamically index data and use those indexes, instead of having to rebuild it every time. So you get the benefits of fast search along with agentic reasoning over CLI tools mentioned above. Come check it out!

Jerry Liu

77,373 views • 1 year ago

Filesystems vs Vector search is the new MCP vs CLI. Claude uses agentic search. And Dens Sumesh at mintlify like filesystems too. but Retrieval is still used by Notion, Cursor, and others. We hit the cafes of SF to see what people want. - The debate is hot. Filesystems won by 1 point - filesystems feel very simple and intuitive. - RAG requires embedding, vector search and other stuff filesystems won. Introducing SMFS - Supermemory Filesystem we brought the best of these worlds into one single product - it's a filesystem, but agent can also do semantic search using grep. live today. Try it! Works with any sandbox, you mount and sync with cloud, it has a sync engine built in, all filetypes supported - even images and videos can be grepped. So, what do you choose - Filesystems, or vector search? we have both!

Filesystems vs Vector search is the new MCP vs CLI. Claude uses agentic search. And Dens Sumesh at mintlify like filesystems too. but Retrieval is still used by Notion, Cursor, and others. We hit the cafes of SF to see what people want. - The debate is hot. Filesystems won by 1 point - filesystems feel very simple and intuitive. - RAG requires embedding, vector search and other stuff filesystems won. Introducing SMFS - Supermemory Filesystem we brought the best of these worlds into one single product - it's a filesystem, but agent can also do semantic search using grep. live today. Try it! Works with any sandbox, you mount and sync with cloud, it has a sync engine built in, all filetypes supported - even images and videos can be grepped. So, what do you choose - Filesystems, or vector search? we have both!

Dhravya Shah

153,119 views • 5 months ago

🤯 YOUR AGENT NOW READS THE ENTIRE INTERNET WITHOUT A SINGLE API KEY someone open-sourced this repo. it replaces $300/mo in paid APIs Agent Reach. #1 Repository of the Day on GitHub trending. 63,165 stars install it - and your agent reads: - any web page → clean markdown - YouTube → captions and search, plus 1800+ video sites - GitHub → repos, issues, search - X → timeline, search, full posts - Reddit → threads and comments - LinkedIn, Instagram, Facebook - RSS and semantic search across the whole web no keys. no subscriptions. important: your cookies stay on your machine. they never leave your agent has been guessing about the internet this whole time. save this before your next research task ↓

🤯 YOUR AGENT NOW READS THE ENTIRE INTERNET WITHOUT A SINGLE API KEY someone open-sourced this repo. it replaces $300/mo in paid APIs Agent Reach. #1 Repository of the Day on GitHub trending. 63,165 stars install it - and your agent reads: - any web page → clean markdown - YouTube → captions and search, plus 1800+ video sites - GitHub → repos, issues, search - X → timeline, search, full posts - Reddit → threads and comments - LinkedIn, Instagram, Facebook - RSS and semantic search across the whole web no keys. no subscriptions. important: your cookies stay on your machine. they never leave your agent has been guessing about the internet this whole time. save this before your next research task ↓

Granite

230,560 views • 2 months ago

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

162,339 views • 7 months ago

🚀 Introducing the World's First Full Agentic Download Agent & AI Drive! 💬 One prompt does it all: search, download, organize files instantly 🗂️ Support download any file: PDFs, images, videos, music, Office documents and more 💡 Integrated Super Agents in AI Drive: process your saved files with AI Try it now: #AItool #Genspark #GENSPEED

🚀 Introducing the World's First Full Agentic Download Agent & AI Drive! 💬 One prompt does it all: search, download, organize files instantly 🗂️ Support download any file: PDFs, images, videos, music, Office documents and more 💡 Integrated Super Agents in AI Drive: process your saved files with AI Try it now: #AItool #Genspark #GENSPEED

Genspark

211,905 views • 1 year ago

Andrew Ng + Google showed the foundation behind modern "RAG", "Graph RAG" and semantic retrieval: • 12:00 - turning text into embeddings that capture meaning • 24:00 - visualizing semantic relationships between vectors • 35:00 - using embeddings for classification, clustering and outlier detection • 50:00 - controlling LLM generation with temperature, top-k and top-p • 1:04:00 - semantic search with ScaNN • 1:15:00 - combining retrieval + an LLM into a RAG-style Q&A system - 84-minute deep dive, and one of the clearest explanations of what happens underneath retrieval systems The progression is simple: Text → Embeddings → Similarity → Semantic Search → Retrieval → LLM Answer Most people jump straight into RAG frameworks without understanding this layer Andrew Ng starts one level lower and shows why retrieval works in the first place Watch it today, then read the full "RAG → Context Graphs" roadmap below

Andrew Ng + Google showed the foundation behind modern "RAG", "Graph RAG" and semantic retrieval: • 12:00 - turning text into embeddings that capture meaning • 24:00 - visualizing semantic relationships between vectors • 35:00 - using embeddings for classification, clustering and outlier detection • 50:00 - controlling LLM generation with temperature, top-k and top-p • 1:04:00 - semantic search with ScaNN • 1:15:00 - combining retrieval + an LLM into a RAG-style Q&A system - 84-minute deep dive, and one of the clearest explanations of what happens underneath retrieval systems The progression is simple: Text → Embeddings → Similarity → Semantic Search → Retrieval → LLM Answer Most people jump straight into RAG frameworks without understanding this layer Andrew Ng starts one level lower and shows why retrieval works in the first place Watch it today, then read the full "RAG → Context Graphs" roadmap below

Morlex

34,790 views • 2 months ago

We're building self-improving agents to automate tedious, repetitive operational work GREP.AI (YC F26). At IG, a UK online brokerage, Grep agents review compliance alerts, helping over 80% of traders onboard without manual intervention. IG is now a FTSE 100 company. Operational work often means following a specific procedure, gathering information from different sources, checking it against what's needed, and deciding what to do next. The steps are repetitive, but no job is the same, making the work tedious to do by hand and hard to automate with workflows alone. Meanwhile, using frontier agents to reason through every task is often too expensive to scale. gives you an agent workforce that: -> Takes minutes to create and are domain experts with the right skills and tools from day one. -> Learn from every run, moving repeatable steps into code and workflows and saving frontier intelligence for exceptions and unfamiliar cases. -> Get smarter and cheaper as they scale using our AgentRun harness. -> Runs on our managed agent platform with secure sandboxes, audit logs, evals, cost controls, team sharing, and access controls included. Grep AI agents are available on demand and can run on schedules or in batch. Access them via the console, MCP, API, or SDKs that integrate into your existing workflows. Our customers, including IG, Airwallex, Worldpay, FV Bank, and Citizens Bank, have saved more than 250,000 hours of operational work with Grep Al agents across onboarding, doc verification, compliance, underwriting, operations, HR, GT ops, market research, and business intelligence. If operational bottlenecks are slowing your business down, create an agent workforce with Grep to automate them in minutes. P.S. We're in the Y Combinator Fall 2026 batch!

We're building self-improving agents to automate tedious, repetitive operational work GREP.AI (YC F26). At IG, a UK online brokerage, Grep agents review compliance alerts, helping over 80% of traders onboard without manual intervention. IG is now a FTSE 100 company. Operational work often means following a specific procedure, gathering information from different sources, checking it against what's needed, and deciding what to do next. The steps are repetitive, but no job is the same, making the work tedious to do by hand and hard to automate with workflows alone. Meanwhile, using frontier agents to reason through every task is often too expensive to scale. gives you an agent workforce that: -> Takes minutes to create and are domain experts with the right skills and tools from day one. -> Learn from every run, moving repeatable steps into code and workflows and saving frontier intelligence for exceptions and unfamiliar cases. -> Get smarter and cheaper as they scale using our AgentRun harness. -> Runs on our managed agent platform with secure sandboxes, audit logs, evals, cost controls, team sharing, and access controls included. Grep AI agents are available on demand and can run on schedules or in batch. Access them via the console, MCP, API, or SDKs that integrate into your existing workflows. Our customers, including IG, Airwallex, Worldpay, FV Bank, and Citizens Bank, have saved more than 250,000 hours of operational work with Grep Al agents across onboarding, doc verification, compliance, underwriting, operations, HR, GT ops, market research, and business intelligence. If operational bottlenecks are slowing your business down, create an agent workforce with Grep to automate them in minutes. P.S. We're in the Y Combinator Fall 2026 batch!

AJ Asver

75,420 views • 9 days ago

Introducing the Knowledge Agent Template Vercel dropped the Chat SDK so we built a full template on top of it that you can deploy in one click. Here's what's inside: • Add your sources: GitHub repos, YouTube, etc. directly from the UI • File-based agent using grep/find/cat • Powered by Vercel Workflow + Sandbox • Multi-platform: web chat, GitHub bot, Discord bot, and more • Comes with skills to edit your project, add sources, create agents Deploy, add a source, ask questions. Your knowledge base is live and always in sync. This is just scratching the surface. There's way more packed in this template, and I'll be breaking down the features all week. Links in the below 👇

Introducing the Knowledge Agent Template Vercel dropped the Chat SDK so we built a full template on top of it that you can deploy in one click. Here's what's inside: • Add your sources: GitHub repos, YouTube, etc. directly from the UI • File-based agent using grep/find/cat • Powered by Vercel Workflow + Sandbox • Multi-platform: web chat, GitHub bot, Discord bot, and more • Comes with skills to edit your project, add sources, create agents Deploy, add a source, ask questions. Your knowledge base is live and always in sync. This is just scratching the surface. There's way more packed in this template, and I'll be breaking down the features all week. Links in the below 👇

Hugo

54,794 views • 7 months ago

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

rody

18,089 views • 14 days ago

New AI Agentic course! Learn to use LangGraph to build single and multi-agent LLM applications in AI Agents in LangGraph. This short course, taught by LangChain founder Harrison Chase Harrison Chase and Tavily founder @weiss_rotem, shows how to integrate agentic search to enhance an agent's knowledge with query-focused answers in predictable formats. Also learn to implement agentic memory to save state for reasoning and debugging, and see how human-in-the-loop input can guide agents at key junctures. You'll build an agent from scratch, then reconstruct it with LangGraph to thoroughly understand the framework. Finally, you'll build a sophisticated essay-writing agent that incorporates all the learnings from the course. Sign up here!

New AI Agentic course! Learn to use LangGraph to build single and multi-agent LLM applications in AI Agents in LangGraph. This short course, taught by LangChain founder Harrison Chase Harrison Chase and Tavily founder @weiss_rotem, shows how to integrate agentic search to enhance an agent's knowledge with query-focused answers in predictable formats. Also learn to implement agentic memory to save state for reasoning and debugging, and see how human-in-the-loop input can guide agents at key junctures. You'll build an agent from scratch, then reconstruct it with LangGraph to thoroughly understand the framework. Finally, you'll build a sophisticated essay-writing agent that incorporates all the learnings from the course. Sign up here!

Andrew Ng

152,816 views • 2 years ago

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

Jerry Liu

23,119 views • 1 month ago

Startups have raised $1B+ to crack Enterprise AI search. Now someone open-sourced it for FREE. The video below shows a self-hosted Slack assistant that answers your questions by searching across all your company's tools in a single query. It's built on top of Airweave, an open-source context retrieval layer that makes all your tools searchable for Agents using semantic, keyword, and agentic search. Here's how the app works: - The app watches for questions in Slack. - It searches every connected tool at once using Airweave (Notion, GitHub, Jira, Linear, etc.) to find relevant context. - The Airweave engine ranks the results by relevance and returns references to the original docs. - An LLM generates the final response and sends it back to Slack with citations. The entire stack is self-hostable via Docker. Find the project in the replies!

Startups have raised $1B+ to crack Enterprise AI search. Now someone open-sourced it for FREE. The video below shows a self-hosted Slack assistant that answers your questions by searching across all your company's tools in a single query. It's built on top of Airweave, an open-source context retrieval layer that makes all your tools searchable for Agents using semantic, keyword, and agentic search. Here's how the app works: - The app watches for questions in Slack. - It searches every connected tool at once using Airweave (Notion, GitHub, Jira, Linear, etc.) to find relevant context. - The Airweave engine ranks the results by relevance and returns references to the original docs. - An LLM generates the final response and sends it back to Slack with citations. The entire stack is self-hostable via Docker. Find the project in the replies!

Avi Chawla

11,982 views • 6 months ago

Beyond Reading — AI with Eyes 👁️👁️ AI agents can already read the web. Now, we’re giving them eyes. This week, we demoed Semantic Video Search — powered by the UpRock Network. Not transcript search. Not keyword matching. Real multimodal intelligence across video, audio, frames, timestamps, and context. The demo: We asked UpRock to search across 100+ hours of livestream history. In seconds, it found: → the exact moment → the visual context → the timestamp → the story behind Jesse’s heart-shaped glasses 🕶️ This is what AI search is becoming. Drop in a YouTube video, TikTok, X video, earnings call, competitor demo, or 3-hour conference talk. Don’t just get a summary. Get structured intelligence your AI agent can actually reason over. What makes UpRock different is what’s underneath: 3M+ real devices. 190+ countries. Real phones. Real locations. Ground-truth access. No datacenter proxy games. No synthetic traffic. No stale scrape layer. Just the internet as real users see it. Semantic Video Search is coming soon for UpRock business customers. Building AI agents, research workflows, media intelligence tools, or multimodal search products? Get in touch → ⚡

Beyond Reading — AI with Eyes 👁️👁️ AI agents can already read the web. Now, we’re giving them eyes. This week, we demoed Semantic Video Search — powered by the UpRock Network. Not transcript search. Not keyword matching. Real multimodal intelligence across video, audio, frames, timestamps, and context. The demo: We asked UpRock to search across 100+ hours of livestream history. In seconds, it found: → the exact moment → the visual context → the timestamp → the story behind Jesse’s heart-shaped glasses 🕶️ This is what AI search is becoming. Drop in a YouTube video, TikTok, X video, earnings call, competitor demo, or 3-hour conference talk. Don’t just get a summary. Get structured intelligence your AI agent can actually reason over. What makes UpRock different is what’s underneath: 3M+ real devices. 190+ countries. Real phones. Real locations. Ground-truth access. No datacenter proxy games. No synthetic traffic. No stale scrape layer. Just the internet as real users see it. Semantic Video Search is coming soon for UpRock business customers. Building AI agents, research workflows, media intelligence tools, or multimodal search products? Get in touch → ⚡

UpRock

128,161 views • 4 months ago

HERMES AGENT JUST LAUNCHED A NATIVE DESKTOP APP. macOS. WINDOWS. LINUX. DOWNLOAD, OPEN, START. Hermes Desktop is now in public preview. first demoed at Jensen's GTC keynote. native app with: → side-by-side preview pane → built-in file browser → integrated voice and TTS → image generation built in → multi-model reasoning → same data directory as CLI → switch between Desktop and CLI anytime what your agent can do from the app: → persistent memory across sessions → natural-language cron jobs → isolated subagents with zero-context-cost → browser automation and web search → 27+ messaging platforms from one gateway → 5 sandbox backends with container hardening (local, Docker, SSH, Singularity, Modal) open source. MIT license. v0.15.2. download link in the comments. full Hermes setup guide in the article 👇

HERMES AGENT JUST LAUNCHED A NATIVE DESKTOP APP. macOS. WINDOWS. LINUX. DOWNLOAD, OPEN, START. Hermes Desktop is now in public preview. first demoed at Jensen's GTC keynote. native app with: → side-by-side preview pane → built-in file browser → integrated voice and TTS → image generation built in → multi-model reasoning → same data directory as CLI → switch between Desktop and CLI anytime what your agent can do from the app: → persistent memory across sessions → natural-language cron jobs → isolated subagents with zero-context-cost → browser automation and web search → 27+ messaging platforms from one gateway → 5 sandbox backends with container hardening (local, Docker, SSH, Singularity, Modal) open source. MIT license. v0.15.2. download link in the comments. full Hermes setup guide in the article 👇

YanXbt

25,078 views • 4 months ago

I cant believe this guy just made a permanent solution to context bloat and open sourced it all! when we tested this tool (Context+) for solving an issue on the OpenCode repository, the agent using this tool used ~6.5k fewer tokens, found the code and fixed it in half the time! the results were surprising: 6 to 10k tokens saved per prompt, completed task in ~2 minutes while the agent running without the tool took ~4 mins for the same and got stuck in loops bro built an entire beast by using all the modern tools that we could think of: undo trees, semantic search by meaning (by haskellforall), advanced refactoring, blast radius, advanced file context trees, restore points... i can keep going on semantic code search and context trees are the future of agentic coding and this tool proves it the feature i loved the most is semantic search and how it gets things done 2x faster with least possible tokens it makes an agent that actually knows what it’s doing and not just guessing, it makes meaning from your code similar to RAG. if you aren't optimizing your context, you are just burning money the developer says this tool is still under development, it can have unexpected behavior and the docs need updates but the video shows the reality of how fast it can be github: get here:

I cant believe this guy just made a permanent solution to context bloat and open sourced it all! when we tested this tool (Context+) for solving an issue on the OpenCode repository, the agent using this tool used ~6.5k fewer tokens, found the code and fixed it in half the time! the results were surprising: 6 to 10k tokens saved per prompt, completed task in ~2 minutes while the agent running without the tool took ~4 mins for the same and got stuck in loops bro built an entire beast by using all the modern tools that we could think of: undo trees, semantic search by meaning (by haskellforall), advanced refactoring, blast radius, advanced file context trees, restore points... i can keep going on semantic code search and context trees are the future of agentic coding and this tool proves it the feature i loved the most is semantic search and how it gets things done 2x faster with least possible tokens it makes an agent that actually knows what it’s doing and not just guessing, it makes meaning from your code similar to RAG. if you aren't optimizing your context, you are just burning money the developer says this tool is still under development, it can have unexpected behavior and the docs need updates but the video shows the reality of how fast it can be github: get here:

forloop

226,544 views • 7 months ago

MICROSOFT JUST OPEN SOURCED THE ENTIRE AGENT RUNTIME, SO YOU NEVER HAVE TO BUILD ONE AGAIN a raw model only writes text. to make it a real agent it needs a loop, tools, memory, planning, approvals, and a way to know when it is done. Microsoft's Agent Harness is that whole layer, and it ships with everything on by default. you bring the model and the tools, it wires up the rest: > an automatic tool calling loop with iteration limits > history saved after every call, so a crash resumes instead of starting over > context compaction that summarizes when the window fills > a persistent todo list plus plan and execute modes > file memory that survives across turns > tool approval with standing rules and auto approval > OpenTelemetry tracing and web search built in > Agent Skills that load domain expertise on demand the mental model is simple: the model is the brain, the harness is the body around it. and it works with whatever you already run: > Azure OpenAI, OpenAI, Anthropic, and GitHub Copilot, and it hosts on Microsoft Foundry you spin one up in a single line: agent = create_harness_agent(client, name, instructions) open source, Python, .NET, and Go, stable since mid 2026. bookmark this. Microsoft already built the hard part of every AI agent, you just plug in the model.

MICROSOFT JUST OPEN SOURCED THE ENTIRE AGENT RUNTIME, SO YOU NEVER HAVE TO BUILD ONE AGAIN a raw model only writes text. to make it a real agent it needs a loop, tools, memory, planning, approvals, and a way to know when it is done. Microsoft's Agent Harness is that whole layer, and it ships with everything on by default. you bring the model and the tools, it wires up the rest: > an automatic tool calling loop with iteration limits > history saved after every call, so a crash resumes instead of starting over > context compaction that summarizes when the window fills > a persistent todo list plus plan and execute modes > file memory that survives across turns > tool approval with standing rules and auto approval > OpenTelemetry tracing and web search built in > Agent Skills that load domain expertise on demand the mental model is simple: the model is the brain, the harness is the body around it. and it works with whatever you already run: > Azure OpenAI, OpenAI, Anthropic, and GitHub Copilot, and it hosts on Microsoft Foundry you spin one up in a single line: agent = create_harness_agent(client, name, instructions) open source, Python, .NET, and Go, stable since mid 2026. bookmark this. Microsoft already built the hard part of every AI agent, you just plug in the model.

NO1ennn

69,163 views • 1 month ago

🚨 Tiger Data - Creators of TimescaleDB (Yes! the team behind TimescaleDB) is quietly revolutionizing how we build agents. The Old Way: Glueing together Postgres + Vector DBs + Search tools = complexity. The New Way: Tiger Data’s Agentic Postgres handles it all natively 🔥 What’s now possible 🧵 ↓ ✦ Hybrid retrieval → combine keyword filtering and vector similarity in a single query ✦ Forkable databases → retrieval and safe experimentation without external systems ✦ Native Postgres semantics → everything stays queryable, inspectable, and debuggable in SQL Why this matters: → Fewer moving parts in RAG pipelines → No extra infrastructure to stitch together → Agents can iterate and learn safely → Production data stays isolated and protected This is an awesome shift! Stop bolting workflows onto your database. Let your database be the workflow 🔥

🚨 Tiger Data - Creators of TimescaleDB (Yes! the team behind TimescaleDB) is quietly revolutionizing how we build agents. The Old Way: Glueing together Postgres + Vector DBs + Search tools = complexity. The New Way: Tiger Data’s Agentic Postgres handles it all natively 🔥 What’s now possible 🧵 ↓ ✦ Hybrid retrieval → combine keyword filtering and vector similarity in a single query ✦ Forkable databases → retrieval and safe experimentation without external systems ✦ Native Postgres semantics → everything stays queryable, inspectable, and debuggable in SQL Why this matters: → Fewer moving parts in RAG pipelines → No extra infrastructure to stitch together → Agents can iterate and learn safely → Production data stays isolated and protected This is an awesome shift! Stop bolting workflows onto your database. Let your database be the workflow 🔥

Charly Wargnier ♨️

20,190 views • 8 months ago

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

NO1ennn

13,359 views • 2 months ago

RLM is the most import foundation of my Pi Harness (other than Pi of course). It's seeded with late interaction retrieval results (thanks to @lightonai for pylate). The Agent initiates it with query then.. 𝐒𝐞𝐭𝐮𝐩 A python REPL is created and seeded with: 1. Late interaction search to pre-filter. Instead of doing top 3/5/10, it's top hundreds of documents. This is set into a `context` variable. 2. Python functions are loaded in to do more searches if `context` variable isn't enough. And to make llm calls with cheaper models in parallel batches. 𝐈𝐭𝐞𝐫𝐚𝐭𝐢𝐨𝐧 𝐋𝐨𝐨𝐩 From there, an LLM iterates in the REPL based on the query. It's just like exploring in a jupyter notebook. The LLM writes prose (like a markdown cell) and code to be run in the REPL each turn. This allows the LLM to sort, filter, and synthesize information. It can fan out and ask smaller models to summarize, combine, contrast, or do anything else to documents to help it understand the data. After several turns the LLM reponds with the final answer. Either because it found the answer, or hit the budget limit. Context as a Python variable, LLM as the programmer, REPL as the runtime. 𝐖𝐡𝐲 𝐃𝐨𝐞𝐬 𝐓𝐡𝐢𝐬 𝐖𝐨𝐫𝐤 1. Richer Shell. Agents (and subagents) work by intermixing code and prose/thinking. But they use static scripts or bash that run and exit and start over each tool call. That's not ideal for exploration and synthesis of data. For that, state is useful to continue building and exploring the data as you learn more. There's a reason jupyter notebooks have been popular with data scientists. 2. Keeps main agent context clean. The better context you have the better the agent will perform (duh!). This means three thing: better human input, less missing search results, and less incorrect search results. Letting the agent iterate allows it to synthesize just what is needed and nothing else. All bad paths or peeks at something that turns out to be irrelevant stays out of main agent context. 3. Stack the good ideas! People often compare late interaction search vs RLM. Or static vs dynamic languages. Or agentic search vs semantic search. But...You can just use them all together for what they're each good at. Use them all for the area they're really great for. Read the full post which has more detail about how and why.

RLM is the most import foundation of my Pi Harness (other than Pi of course). It's seeded with late interaction retrieval results (thanks to @lightonai for pylate). The Agent initiates it with query then.. 𝐒𝐞𝐭𝐮𝐩 A python REPL is created and seeded with: 1. Late interaction search to pre-filter. Instead of doing top 3/5/10, it's top hundreds of documents. This is set into a `context` variable. 2. Python functions are loaded in to do more searches if `context` variable isn't enough. And to make llm calls with cheaper models in parallel batches. 𝐈𝐭𝐞𝐫𝐚𝐭𝐢𝐨𝐧 𝐋𝐨𝐨𝐩 From there, an LLM iterates in the REPL based on the query. It's just like exploring in a jupyter notebook. The LLM writes prose (like a markdown cell) and code to be run in the REPL each turn. This allows the LLM to sort, filter, and synthesize information. It can fan out and ask smaller models to summarize, combine, contrast, or do anything else to documents to help it understand the data. After several turns the LLM reponds with the final answer. Either because it found the answer, or hit the budget limit. Context as a Python variable, LLM as the programmer, REPL as the runtime. 𝐖𝐡𝐲 𝐃𝐨𝐞𝐬 𝐓𝐡𝐢𝐬 𝐖𝐨𝐫𝐤 1. Richer Shell. Agents (and subagents) work by intermixing code and prose/thinking. But they use static scripts or bash that run and exit and start over each tool call. That's not ideal for exploration and synthesis of data. For that, state is useful to continue building and exploring the data as you learn more. There's a reason jupyter notebooks have been popular with data scientists. 2. Keeps main agent context clean. The better context you have the better the agent will perform (duh!). This means three thing: better human input, less missing search results, and less incorrect search results. Letting the agent iterate allows it to synthesize just what is needed and nothing else. All bad paths or peeks at something that turns out to be irrelevant stays out of main agent context. 3. Stack the good ideas! People often compare late interaction search vs RLM. Or static vs dynamic languages. Or agentic search vs semantic search. But...You can just use them all together for what they're each good at. Use them all for the area they're really great for. Read the full post which has more detail about how and why.

Isaac Flath

42,874 views • 5 months ago