Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

over the weekend i built and shipped Sentra for our docs. we use Mintlify for documentation. the built-in assistant kept running into context issues. wrong answers, missing context, no citations. so we extended Sentra's capability to the docs site directly. now when you're reading Dodo Payments docs, you can... ask Sentra questions right there. it pulls context from our entire documentation via RAG (the same contextmcp (completely opensource) + Pinecone vector search with reranking), generates grounded answers, and cites the exact doc pages. built as a single Cloudflare Worker serving both the widget and the chat endpoint. React widget bundled into one self-contained IIFE, mounted in Shadow DOM so it doesn't conflict with Mintlify's styles. OpenAI models routed through Cloudflare AI Gateway. Vercel's AI SDK for streaming and shadcn for beautiful chat components. live now atshow more

Ayush Agarwal

10,608 subscribers

18,408 görüntüleme • 2 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

13 Yorum

Revoca AI profil fotoğrafı

Revoca AI2 ay önce

The context and citation problem you hit is very real. Most of the built-in doc assistants are not great at answering with exact page citations. We’re building this space: connect your docs, github, etc and it handles customer onboarding and support with to-the-point, grounded answers. Our view is that you don't want companies pulled off their core craft to solve this, let us handle it. Give Revoca a try. We do a lot more than just surfacing the docs. I’d love to show you what we have.

Tanay Kumar profil fotoğrafı

Tanay Kumar2 ay önce

@mintlify oof this is SO GOOD. Sire, the engineers g culture you’ve cultivated at Dodo is 🤌

Uday profil fotoğrafı

Uday2 ay önce

@mintlify The citation layer is the real unlock for docs assistants. A wrong answer without a source feels worse than no assistant. I’d also make “I don’t know from the docs” a first-class path, with links to the closest source pages. That keeps trust intact when context is thin.

Animesh profil fotoğrafı

Animesh2 ay önce

@mintlify I've been thinking of building this for myself any plans of making this open-source or as self-hostable Ask AI widget

Ayush Agarwal profil fotoğrafı

Ayush Agarwal2 ay önce

@mintlify open sourced it here -

Animesh profil fotoğrafı

Animesh2 ay önce

@mintlify Wow, thanks a lot Ayush! 🙌

Mateusz profil fotoğrafı

Mateusz2 ay önce

@mintlify What LLM model you use under the hood?

Ayush Agarwal profil fotoğrafı

Ayush Agarwal2 ay önce

@mintlify For this gpt-5.4-mini

Somi profil fotoğrafı

Somi2 ay önce

@mintlify what's the reindex story when docs change, every deploy or on a schedule? that's the part that rots quietly, stale citations still read as grounded so you don't notice

Ayush Agarwal profil fotoğrafı

Ayush Agarwal2 ay önce

@mintlify It reindex everyday to maintain freshness

Wijayanto profil fotoğrafı

Wijayanto2 ay önce

@mintlify Actually i more like MCP because can conntect with my agent an AI

Ayush Agarwal profil fotoğrafı

Ayush Agarwal2 ay önce

@mintlify This is also an extension to our mcp

Uday profil fotoğrafı

Uday2 ay önce

@mintlify Nice direction. For docs assistants, citations are only the visible part. The deeper thing is trust recovery: show which page/version answered, what context was ignored, and where the answer is unsure. That makes wrong answers debuggable instead of just embarrassing.

Benzer Videolar

We've been obsessing a lot about creating the best possible AI support experience Dub.co. And I think we've found the magic formula. The stack: ✦ Mintlify → docs + help articles ✦ Upstash vector → vector search ✦ AI SDK + Claude sonnet → LLM/retrieval ✦ Plain → support infra Here's how it works: We consolidated our docs + help articles on Mintlify (best-in-class docs platform) so all our support content is now in one place. On every push to main, we sync changes to our Upstash Vector DB. We also built a custom chat interface that retrieves content from Upstash Vector and generates responses via AI SDK + Claude sonnet. The best part: The AI agent uses 𝚝𝚘𝚘𝚕() from AI SDK to retrieve the user's workspace / partner data to provide accurate responses. Finally, if the user needs to speak to a human, we generate a 𝚃𝚒𝚌𝚔𝚎𝚝𝚄𝚙𝚕𝚘𝚊𝚍 UI that lets users upload screenshots + add more context, before creating a ticket on Plain. Cherry on top: The chat interface is embeddable, so we're able to embed it both in our Mintlify docs + support portal 👇 Since we launched this, it's been a gamechanger for scaling support – reducing support workload and creating a much better experience for our users. Highly recommend giving this a try!

We've been obsessing a lot about creating the best possible AI support experience Dub.co. And I think we've found the magic formula. The stack: ✦ Mintlify → docs + help articles ✦ Upstash vector → vector search ✦ AI SDK + Claude sonnet → LLM/retrieval ✦ Plain → support infra Here's how it works: We consolidated our docs + help articles on Mintlify (best-in-class docs platform) so all our support content is now in one place. On every push to main, we sync changes to our Upstash Vector DB. We also built a custom chat interface that retrieves content from Upstash Vector and generates responses via AI SDK + Claude sonnet. The best part: The AI agent uses 𝚝𝚘𝚘𝚕() from AI SDK to retrieve the user's workspace / partner data to provide accurate responses. Finally, if the user needs to speak to a human, we generate a 𝚃𝚒𝚌𝚔𝚎𝚝𝚄𝚙𝚕𝚘𝚊𝚍 UI that lets users upload screenshots + add more context, before creating a ticket on Plain. Cherry on top: The chat interface is embeddable, so we're able to embed it both in our Mintlify docs + support portal 👇 Since we launched this, it's been a gamechanger for scaling support – reducing support workload and creating a much better experience for our users. Highly recommend giving this a try!

Steven Tey

23,029 görüntüleme • 6 ay önce

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 görüntüleme • 6 ay önce

introducing: Auto Knowledge Gap Finding for Your Docs Your docs probably don't know what shipped, and no one remembers to keep them up to date. Every release creates the same cleanup job: search the docs, decide what is missing or stale, find the evidence, and write the update. Most teams discover the gap when a customer asks a question the docs should have answered. So we built Knowledge Gaps in Compare GitHub releases, RSS feeds, or changelog entries against your customer and internal documentation. See missing, stale, hard-to-find, and needs-triage findings with the release evidence and every documentation page BuildBetter checked. Approve the real work, copy a ready-to-use prompt into your agent, or attach the finding to a project. Happy building!

introducing: Auto Knowledge Gap Finding for Your Docs Your docs probably don't know what shipped, and no one remembers to keep them up to date. Every release creates the same cleanup job: search the docs, decide what is missing or stale, find the evidence, and write the update. Most teams discover the gap when a customer asks a question the docs should have answered. So we built Knowledge Gaps in Compare GitHub releases, RSS feeds, or changelog entries against your customer and internal documentation. See missing, stale, hard-to-find, and needs-triage findings with the release evidence and every documentation page BuildBetter checked. Approve the real work, copy a ready-to-use prompt into your agent, or attach the finding to a project. Happy building!

Spencer Shulem

5,438,637 görüntüleme • 1 ay önce

AI coding just arrived in Jupyter notebooks - and bhupesh ganger (Jupyter co-founder) and I will show you how to use it. Coding by hand is becoming obsolete. The latest Jupyter AI - built by the Jupyter team and showcased at JupyterCon this week - brings AI assistance directly into notebooks. Most AI coding assistants struggle with Jupyter notebooks. Jupyter AI was designed specifically for them. This is the first course to teach it. In this course, Brian and I teach you to: - Generate and debug code directly in notebook cells through an integrated chat interface - Provide the right context (like API docs) to help AI write accurate code - Use Jupyter AI's unique notebook features: drag cells to chat, generate cells from chat, attach context for the LLM We've integrated Jupyter AI directly into the DeepLearningAI platform, so you can start using it immediately. Since Jupyter AI is open source, you can also install and run it locally afterward. Whether you're experienced with notebooks or learning them for the first time, this course will prepare you for AI-assisted notebook development. Start using Jupyter AI (free):

AI coding just arrived in Jupyter notebooks - and bhupesh ganger (Jupyter co-founder) and I will show you how to use it. Coding by hand is becoming obsolete. The latest Jupyter AI - built by the Jupyter team and showcased at JupyterCon this week - brings AI assistance directly into notebooks. Most AI coding assistants struggle with Jupyter notebooks. Jupyter AI was designed specifically for them. This is the first course to teach it. In this course, Brian and I teach you to: - Generate and debug code directly in notebook cells through an integrated chat interface - Provide the right context (like API docs) to help AI write accurate code - Use Jupyter AI's unique notebook features: drag cells to chat, generate cells from chat, attach context for the LLM We've integrated Jupyter AI directly into the DeepLearningAI platform, so you can start using it immediately. Since Jupyter AI is open source, you can also install and run it locally afterward. Whether you're experienced with notebooks or learning them for the first time, this course will prepare you for AI-assisted notebook development. Start using Jupyter AI (free):

Andrew Ng

118,853 görüntüleme • 10 ay önce

Today we’re introducing Superhuman Docs, the evolution of Coda (Superhuman Docs) into the best place for teams and AI to work together. I co-founded Coda to reimagine the modern document and enable anyone to make a doc as powerful as an app. Superhuman Docs builds on that mission, and is reimagined for how teams work with AI now. With Superhuman Docs, AI is no longer a solo experience. Docs AI works with you the way a teammate would, with full context of everything your team has built: your data, your briefs, your roadmaps, your connected tools. You can ask it to summarize a sprint, draft a decision record from your meeting notes, or pull a competitor analysis into a new page, and that work stays right where your teammates can pick it up. I’m incredibly proud of the team for bringing Docs to life! There’s so much more we’re launching, including a way to create custom interfaces on top of your data just by describing it. We’re also introducing Superhuman Databases for teams to manage up to 1 million rows, launching Docs MCP to open it up to the AI tools you already use, and debuting a brand new Mac app. We’ve been building toward this moment for a long time, and Docs starts rolling out today. If you’re an existing Coda user, everything you rely on in your docs will remain the same, and if you’re new, now is a great time to jump in.

Shishir

24,342 görüntüleme • 2 ay önce

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

Sarah Chieng

26,679 görüntüleme • 5 ay önce

I've been using Ring-2.6-1T on OpenRouter for my documentation pipeline this week. My usual flow: I dump a raw codebase or a long spec doc into the model and ask it to generate structured docs, flag inconsistencies, and draft a changelog. With other models, I was splitting this into 3 separate prompts because of context limits. Each split costs tokens. Each split loses some coherence between sections. With Ring-2.6-1T, I sent the whole thing in 1 prompt. 38,000 tokens. got back structured docs, a flagged inconsistencies list, and a changelog draft in a single response. Coherence was intact across all 3 outputs. No context bleed between sections. Still running it through more workflows, but the single-prompt full-doc processing alone has already cut my per-task token spend significantly. And then the cost showed $0.00, and I sat there for a second 👉 #BuildInPublic #OpenSource

I've been using Ring-2.6-1T on OpenRouter for my documentation pipeline this week. My usual flow: I dump a raw codebase or a long spec doc into the model and ask it to generate structured docs, flag inconsistencies, and draft a changelog. With other models, I was splitting this into 3 separate prompts because of context limits. Each split costs tokens. Each split loses some coherence between sections. With Ring-2.6-1T, I sent the whole thing in 1 prompt. 38,000 tokens. got back structured docs, a flagged inconsistencies list, and a changelog draft in a single response. Coherence was intact across all 3 outputs. No context bleed between sections. Still running it through more workflows, but the single-prompt full-doc processing alone has already cut my per-task token spend significantly. And then the cost showed $0.00, and I sat there for a second 👉 #BuildInPublic #OpenSource

Parul Gautam

48,658 görüntüleme • 4 ay önce

If you don't know what a RAG system is, you're already behind. Plenty of people are still typing questions into ChatGPT and pasting answers back out. That's the beginner level. You're renting a smart stranger who forgets you the second you close the tab and makes things up, because it has never seen your actual work. A RAG system is a completely different level of using AI. You build an AI plugged into your own world. Your files, company's docs, notes. It's not pulling from the internet, it only knows what you fed it. Ask it anything and it digs through your data, finds the answer, and shows you which document it came from. That's the gap. One person is asking a chatbot for generic answers. The other has built a private expert that knows their business cold and answers with receipts. And that gap is worth real money: > At work, the person who can wire a company's knowledge into an AI that actually answers correctly is rare and paid like it. > As a business, companies pay serious money for a system that reads their internal docs and answers staff and customers accurately. You build it once, you sell it. > For yourself, you get a second brain that actually remembers. Same skill behind all three, and it's still rare enough to be worth learning. Full breakdown in the article below.

If you don't know what a RAG system is, you're already behind. Plenty of people are still typing questions into ChatGPT and pasting answers back out. That's the beginner level. You're renting a smart stranger who forgets you the second you close the tab and makes things up, because it has never seen your actual work. A RAG system is a completely different level of using AI. You build an AI plugged into your own world. Your files, company's docs, notes. It's not pulling from the internet, it only knows what you fed it. Ask it anything and it digs through your data, finds the answer, and shows you which document it came from. That's the gap. One person is asking a chatbot for generic answers. The other has built a private expert that knows their business cold and answers with receipts. And that gap is worth real money: > At work, the person who can wire a company's knowledge into an AI that actually answers correctly is rare and paid like it. > As a business, companies pay serious money for a system that reads their internal docs and answers staff and customers accurately. You build it once, you sell it. > For yourself, you get a second brain that actually remembers. Same skill behind all three, and it's still rare enough to be worth learning. Full breakdown in the article below.

Yarchi

32,840 görüntüleme • 2 ay önce

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain

Muskan Jain

44,007 görüntüleme • 1 ay önce

I’ve been waiting for something like this. Using multiple AI agents sounds great until you have to keep giving each one the same context. Jarvix Jarvix is built to solve that： It carries your selected context across the AI tools you already use and brings everything together in one place. #JarvixOS You can use Jarvix Home to see your context and connections, Jarvix Search to find past information without remembering exact file names, and Self Reflection to spot patterns in the way you work. There’s also Jarvix Radio for personalized content discovery and Next Move to surface a useful direction based on your context. And the part I find most interesting: Agent Team Mode. Give Jarvix one goal, choose the agents you want to use, and it divides the work while keeping everyone on the same project context. You can watch the progress, review the result, and approve what happens next. No need to keep briefing every agent from scratch. One goal. Shared context. Multiple agents. You stay in control. That’s a much cleaner way to work with AI.

I’ve been waiting for something like this. Using multiple AI agents sounds great until you have to keep giving each one the same context. Jarvix Jarvix is built to solve that： It carries your selected context across the AI tools you already use and brings everything together in one place. #JarvixOS You can use Jarvix Home to see your context and connections, Jarvix Search to find past information without remembering exact file names, and Self Reflection to spot patterns in the way you work. There’s also Jarvix Radio for personalized content discovery and Next Move to surface a useful direction based on your context. And the part I find most interesting: Agent Team Mode. Give Jarvix one goal, choose the agents you want to use, and it divides the work while keeping everyone on the same project context. You can watch the progress, review the result, and approve what happens next. No need to keep briefing every agent from scratch. One goal. Shared context. Multiple agents. You stay in control. That’s a much cleaner way to work with AI.

Aaliya

23,225 görüntüleme • 1 ay önce

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.

Mike Fishbein

10,171 görüntüleme • 3 ay önce

I normally don't like plugging on an AI chat into my projects, because it's seems too easy and basic I think you should instead rebuild entire projects from the ground up to be AI first, not just add some AI button But in this case is already AI from the ground up (it collects data and rates hotels with AI), so here it makes sense I think So you can now can talk to the hotel assistant and ask it to find hotels with a 🏋️‍♀️weightlifting gym, ✨newly built, 🔝highly rated or ones that have 🥯 cinnamon rolls for breakfast 😋 And it controls the site, moves the map, opens hotels for you! Hope you like it 😊😊😊 P.S. it doesn't make money, it's just my contribution for now to fight the enshittification and get you a good hotel for a good price!

I normally don't like plugging on an AI chat into my projects, because it's seems too easy and basic I think you should instead rebuild entire projects from the ground up to be AI first, not just add some AI button But in this case is already AI from the ground up (it collects data and rates hotels with AI), so here it makes sense I think So you can now can talk to the hotel assistant and ask it to find hotels with a 🏋️‍♀️weightlifting gym, ✨newly built, 🔝highly rated or ones that have 🥯 cinnamon rolls for breakfast 😋 And it controls the site, moves the map, opens hotels for you! Hope you like it 😊😊😊 P.S. it doesn't make money, it's just my contribution for now to fight the enshittification and get you a good hotel for a good price!

@levelsio

316,215 görüntüleme • 3 ay önce

Google Opal is vastly underrated but can replace n8n or Make in many situations You can create powerful AI workflows for free and with a single prompt: - Ask the user for any input - Run multiple deep research simultaneously - Add any context you want (YT video, text, docs...) - Use tools like web, Maps, code execution - Synthesize with Gemini 2.5 Pro - Generate results in any format I created this agent to prepare meetings in literally 10 minutes. Tip: make sure to use the microphone feature to give as much context as possible to Opal... So it can generate the workflow almost in one-shot!

Google Opal is vastly underrated but can replace n8n or Make in many situations You can create powerful AI workflows for free and with a single prompt: - Ask the user for any input - Run multiple deep research simultaneously - Add any context you want (YT video, text, docs...) - Use tools like web, Maps, code execution - Synthesize with Gemini 2.5 Pro - Generate results in any format I created this agent to prepare meetings in literally 10 minutes. Tip: make sure to use the microphone feature to give as much context as possible to Opal... So it can generate the workflow almost in one-shot!

Paul Couvert

68,011 görüntüleme • 10 ay önce

Today we're launching Macro 1.0 — a new office suite for the intelligence age. Macro is a unified workspace for your entire company, your team and your agents. 1. Fully open source. Built in Rust + SolidJS. Self-host if you want. 2. Designed as a single system: email, messaging, docs, tasks, agents, calls, and CRM all @-linked together in one tab. 3. Unified team-level memory for agents built over emails, team chat, tasks, PR's and CRM. Access the memory from Macro or AI or external agents via MCP. We built Macro for ourselves because we wanted a single system for our whole company. We didn't want to get slowed down by rate limits and 2FA'ing into 17 different tabs. Let's take a look at each block 🧵👇

Today we're launching Macro 1.0 — a new office suite for the intelligence age. Macro is a unified workspace for your entire company, your team and your agents. 1. Fully open source. Built in Rust + SolidJS. Self-host if you want. 2. Designed as a single system: email, messaging, docs, tasks, agents, calls, and CRM all @-linked together in one tab. 3. Unified team-level memory for agents built over emails, team chat, tasks, PR's and CRM. Access the memory from Macro or AI or external agents via MCP. We built Macro for ourselves because we wanted a single system for our whole company. We didn't want to get slowed down by rate limits and 2FA'ing into 17 different tabs. Let's take a look at each block 🧵👇

Macro

165,654 görüntüleme • 1 ay önce

I built a knowledge/chat agent that actually sees inside your Shopify app. It knows every screen, every button, every text block, and every link — and can deep-link users directly into the right page of your live app. It’s called Zero Docs. ▻ Drop the agent directly into your live app ▻ Use our Chrome extension to capture your authenticated app screens ▻ It answers with real layout intelligence + deep links ▻ Reduce your support requests by 80% ▻ One click and it writes your docs too Deploy it in 10 minutes. Free to try. Plans start at $10/mo. First 50 Shopify apps get 4 free months of Bootstrap or Starter plans — just DM me or use code SHOPIFY4 at checkout. I'd love feedback from other Shopify devs — especially if you’ve tried other AI "chat" agents before.

I built a knowledge/chat agent that actually sees inside your Shopify app. It knows every screen, every button, every text block, and every link — and can deep-link users directly into the right page of your live app. It’s called Zero Docs. ▻ Drop the agent directly into your live app ▻ Use our Chrome extension to capture your authenticated app screens ▻ It answers with real layout intelligence + deep links ▻ Reduce your support requests by 80% ▻ One click and it writes your docs too Deploy it in 10 minutes. Free to try. Plans start at $10/mo. First 50 Shopify apps get 4 free months of Bootstrap or Starter plans — just DM me or use code SHOPIFY4 at checkout. I'd love feedback from other Shopify devs — especially if you’ve tried other AI "chat" agents before.

William Belk

1,078,547 görüntüleme • 4 ay önce

We’re entering the 10x speed of research publication workflow with AI. SciSpace (SciSpace), the first AI Agent built exclusively for the scientific community, is releasing so many inredibly useful features. 🎯 This is the AI Agent that can use 150+ tools, 59 databases, and 280M+ papers A few weeks back they launched BioMed Agent - It can design entire molecular biology workflows and even create publication-ready illustrations in a single prompt. This is its new domain-specialized AI co-scientist that sits on top of the existing SciSpace Agent and automates full biomedical workflows, from raw data and papers to analysis, decisions, and the final production-grade illustrations. You just need to give it 1 prompt. And today the added the following - Library Search, so it can search and analyze the PDFs already sitting in My Library, letting people ask questions across their own paper pile while keeping it private. - Now connects directly to Zotero, so the Agent can pull and work with the papers you already saved there without manual uploads. - For bigger prompts, it auto-triggers a Report Writing Sub-Agent that turns the chat into a structured research-style report, which is way cleaner for literature reviews and long summaries. - And when you get something worth keeping, Save to Notebook lets you store the output as .md notes with citations in My notebooks, so the work becomes reusable research notes instead of disappearing into chat. Behind the scenes, it indexes the PDF text, pulls a few relevant chunks for the question, then writes an answer grounded on those chunks.

We’re entering the 10x speed of research publication workflow with AI. SciSpace (SciSpace), the first AI Agent built exclusively for the scientific community, is releasing so many inredibly useful features. 🎯 This is the AI Agent that can use 150+ tools, 59 databases, and 280M+ papers A few weeks back they launched BioMed Agent - It can design entire molecular biology workflows and even create publication-ready illustrations in a single prompt. This is its new domain-specialized AI co-scientist that sits on top of the existing SciSpace Agent and automates full biomedical workflows, from raw data and papers to analysis, decisions, and the final production-grade illustrations. You just need to give it 1 prompt. And today the added the following - Library Search, so it can search and analyze the PDFs already sitting in My Library, letting people ask questions across their own paper pile while keeping it private. - Now connects directly to Zotero, so the Agent can pull and work with the papers you already saved there without manual uploads. - For bigger prompts, it auto-triggers a Report Writing Sub-Agent that turns the chat into a structured research-style report, which is way cleaner for literature reviews and long summaries. - And when you get something worth keeping, Save to Notebook lets you store the output as .md notes with citations in My notebooks, so the work becomes reusable research notes instead of disappearing into chat. Behind the scenes, it indexes the PDF text, pulls a few relevant chunks for the question, then writes an answer grounded on those chunks.

Rohan Paul

11,574 görüntüleme • 8 ay önce

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,491 görüntüleme • 6 ay önce

MCP is an absolute game-changer. (Together with DeepSeek, MCP is probably the hottest thing in AI over the last 6 months.) I use Cursor to write code 90% of the time. I built an MCP server to connect the Cursor agent to GroundX, an open-source RAG system, and I'm not going back. This is officially insane! Here is what I did, step by step: First, a little bit of context. I maintain an end-to-end Machine Learning System with several pipelines to process data, train, evaluate, register, deploy, and monitor a model. I've written a lot of documentation explaining how the system works and how to modify and maintain it. There's also the documentation of the few libraries I used to build the system. I'm a massive fan of GroundX, an open-source enterprise-grade RAG system you can run on your servers or deploy to any cloud provider. I've been working with them for a long time. GroundX offers two services. First, the "ingest" service uses a custom, pretrained vision model to ingest and understand your data. I used this to process all the documentation I have for my code. Markdown files, source code, HTML files, and even PDF documents. Everything I've written related to my project went into GroundX. Their second service is "search," which combines text and vector search with a fine-tuned re-ranker model to retrieve information from the data. I needed to connect Cursor with this service, and that's where MCP came in. I built an MCP server with two tools: 1. The first tool would go to GroundX and retrieve the available topics. Splitting the data into topics (or "buckets," as GroundX calls them) allows me to use the same setup to serve documentation from different topics. 2. The second tool would search GroundX under a specific topic for the context related to the supplied query. The magic happens after connecting the MCP server with Cursor. Now, I can ask any questions related to my project, and Cursor's AI agent retrieves the list of available topics from the RAG system and then searches it to provide relevant context to the model. I went from getting mediocre, sometimes wrong answers to 100% truthful, complete answers. Here is the crazy part:

MCP is an absolute game-changer. (Together with DeepSeek, MCP is probably the hottest thing in AI over the last 6 months.) I use Cursor to write code 90% of the time. I built an MCP server to connect the Cursor agent to GroundX, an open-source RAG system, and I'm not going back. This is officially insane! Here is what I did, step by step: First, a little bit of context. I maintain an end-to-end Machine Learning System with several pipelines to process data, train, evaluate, register, deploy, and monitor a model. I've written a lot of documentation explaining how the system works and how to modify and maintain it. There's also the documentation of the few libraries I used to build the system. I'm a massive fan of GroundX, an open-source enterprise-grade RAG system you can run on your servers or deploy to any cloud provider. I've been working with them for a long time. GroundX offers two services. First, the "ingest" service uses a custom, pretrained vision model to ingest and understand your data. I used this to process all the documentation I have for my code. Markdown files, source code, HTML files, and even PDF documents. Everything I've written related to my project went into GroundX. Their second service is "search," which combines text and vector search with a fine-tuned re-ranker model to retrieve information from the data. I needed to connect Cursor with this service, and that's where MCP came in. I built an MCP server with two tools: 1. The first tool would go to GroundX and retrieve the available topics. Splitting the data into topics (or "buckets," as GroundX calls them) allows me to use the same setup to serve documentation from different topics. 2. The second tool would search GroundX under a specific topic for the context related to the supplied query. The magic happens after connecting the MCP server with Cursor. Now, I can ask any questions related to my project, and Cursor's AI agent retrieves the list of available topics from the RAG system and then searches it to provide relevant context to the model. I went from getting mediocre, sometimes wrong answers to 100% truthful, complete answers. Here is the crazy part:

Santiago

255,756 görüntüleme • 1 yıl önce