Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Introducing InsForge 2.0: The Backend for Agentic Development Our OSS backend provides databases, auth, storage, model gateway, and edge functions accessible through a context-optimized layer that agents can better understand and operate end-to-end. GitHub: Key Benchmarks (vs. Supabase MCP): - 14% higher accuracy - 1.3x faster per task -...

insforge's profile picture

InsForge

2,317 subscribers

1,592,049 görüntüleme • 4 ay önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

Introducing InsForge Backend Branching. We made agentic coding production-safe. Your agent creates isolated backend branches when working. Every backend service, policy, and config is copied into a secure, isolated environment. Review PR-style diffs. Merge only when ready.
1:33

Introducing InsForge Backend Branching. We made agentic coding production-safe. Your agent creates isolated backend branches when working. Every backend service, policy, and config is copied into a secure, isolated environment. Review PR-style diffs. Merge only when ready.

InsForge

62,139 görüntüleme • 1 ay önce

Introducing Diagnose and Debug. Give your agent first-party backend context: health metrics, logs, errors, database checks, and more. Your coding agent catches backend issues now, then fixes them by working with your dedicated InsForge debugging agent. Agent <> Agent.
1:50

Introducing Diagnose and Debug. Give your agent first-party backend context: health metrics, logs, errors, database checks, and more. Your coding agent catches backend issues now, then fixes them by working with your dedicated InsForge debugging agent. Agent <> Agent.

InsForge

52,193 görüntüleme • 1 ay önce

We’re building the agent-native alternative to AWS, but it's actually good. - 33,000+ projects created (10% WoW growth) - 2x weekly active projects (2000 → 4000+) - 11,000+ GitHub stars (5x in the last 3 months) - faster than React, Supabase, and Linux Introducing InsForge ↓
1:42

We’re building the agent-native alternative to AWS, but it's actually good. - 33,000+ projects created (10% WoW growth) - 2x weekly active projects (2000 → 4000+) - 11,000+ GitHub stars (5x in the last 3 months) - faster than React, Supabase, and Linux Introducing InsForge ↓

InsForge

597,553 görüntüleme • 1 ay önce

Introducing InsForge Compute. Deploy long-running backend services as Docker containers via your coding agent. It writes the Dockerfile, builds the image, injects env vars, runs the container, and returns a live URL. All in under 60 seconds.
1:21

Introducing InsForge Compute. Deploy long-running backend services as Docker containers via your coding agent. It writes the Dockerfile, builds the image, injects env vars, runs the container, and returns a live URL. All in under 60 seconds.

InsForge

1,510,962 görüntüleme • 1 ay önce

Today we’re launching 4 open-source Next.js app templates: 1. Basic starter 2. Chatbot 3. CRM 4. Ecommerce We made building real full-stack apps even easier on InsForge. Try one in your next project: npx @insforge/cli create Thread below with all 4 repos ↓
1:00

Today we’re launching 4 open-source Next.js app templates: 1. Basic starter 2. Chatbot 3. CRM 4. Ecommerce We made building real full-stack apps even easier on InsForge. Try one in your next project: npx @insforge/cli create Thread below with all 4 repos ↓

InsForge

671,992 görüntüleme • 3 ay önce

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.
0:29

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.

Avi Chawla

112,879 görüntüleme • 1 ay önce

Introducing InsForge Payments. Your coding agent can now set up Stripe payments for your app using InsForge. Describe your pricing and watch it create products and prices in Stripe, add checkout, and set up billing portal sessions. Test first. Go live when ready.
1:16

Introducing InsForge Payments. Your coding agent can now set up Stripe payments for your app using InsForge. Describe your pricing and watch it create products and prices in Stripe, add checkout, and set up billing portal sessions. Test first. Go live when ready.

InsForge

674,484 görüntüleme • 1 ay önce

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

118,124 görüntüleme • 1 ay önce

Introducing 🦀 CRAB: Cross-environment Agent Benchmark for Multimodal Language Model Agents 🦀 CRAB provides an end-to-end and easy-to-use framework to build multimodal agents, operate environments, and create benchmarks to evaluate them, featuring three key components: - 🔀 Cross-environment support - agents can operate tasks in 📱 Android and 💻 Ubuntu. - 🕸️ Graph evaluator - provides a fine-grain evaluation metric for agents. - 🤖 Task generation - composes subtasks to automatically generate tasks. By connecting all devices to agents, 🦀CRAB unlocks greater capabilities for human-like tasks than ever before. Use 🦀 CRAB to benchmark your multimodal agents! - 👨‍💻 Check out the repository: - 📝 Read the paper: - 🌐 Find out more via the project page: - 🐫 Join our community:
1:05

Introducing 🦀 CRAB: Cross-environment Agent Benchmark for Multimodal Language Model Agents 🦀 CRAB provides an end-to-end and easy-to-use framework to build multimodal agents, operate environments, and create benchmarks to evaluate them, featuring three key components: - 🔀 Cross-environment support - agents can operate tasks in 📱 Android and 💻 Ubuntu. - 🕸️ Graph evaluator - provides a fine-grain evaluation metric for agents. - 🤖 Task generation - composes subtasks to automatically generate tasks. By connecting all devices to agents, 🦀CRAB unlocks greater capabilities for human-like tasks than ever before. Use 🦀 CRAB to benchmark your multimodal agents! - 👨‍💻 Check out the repository: - 📝 Read the paper: - 🌐 Find out more via the project page: - 🐫 Join our community:

CAMEL-AI.org

72,661 görüntüleme • 1 yıl önce

Today we're launching Airbyte Agents. It’s a platform meant to solve what we call the discovery gap. Agents in demos are successful because they know the fields and sources they have to call to solve their task. Agents in production fail because they don’t have that knowledge assembled beforehand. Airbyte Agents, powered by the Context Store, fixes that with one unified layer of pre-materialized context across all of your business systems. Real results. 80% fewer tokens. 40% fewer tool calls. Get more out of your AI tool’s plan limit. Three ways to build: MCP, SDK, or no-code Automations 💡 We're early, and we want to build with our users. Try Airbyte Agents today.
2:51

Today we're launching Airbyte Agents. It’s a platform meant to solve what we call the discovery gap. Agents in demos are successful because they know the fields and sources they have to call to solve their task. Agents in production fail because they don’t have that knowledge assembled beforehand. Airbyte Agents, powered by the Context Store, fixes that with one unified layer of pre-materialized context across all of your business systems. Real results. 80% fewer tokens. 40% fewer tool calls. Get more out of your AI tool’s plan limit. Three ways to build: MCP, SDK, or no-code Automations 💡 We're early, and we want to build with our users. Try Airbyte Agents today.

Airbyte

6,761,845 görüntüleme • 2 ay önce

Long, long, ago, coding agents could do nothing but write code Forger was powerless, just like all the others. Claude Code. Codex. Cursor. Until one day... InsForge Launch Week 2 starts Monday, June 1st
0:24

Long, long, ago, coding agents could do nothing but write code Forger was powerless, just like all the others. Claude Code. Codex. Cursor. Until one day... InsForge Launch Week 2 starts Monday, June 1st

InsForge

35,208 görüntüleme • 1 ay önce

Today, we're introducing not one but TWO new models, striking the balance between efficiency and quality to enable you to build production AI agents. — Gemini 3.6 Flash: Addresses efficiency feedback we received from Gemini 3.5 Flash with upgrades in coding, knowledge work, and multimodal tasks faster, more accurately, and with substantially fewer tokens per task — Gemini 3.5 Flash-Lite: Our fastest, most cost-effective 3.5-class model yet built for agentic workflows, hitting ~350 output tokens/sec with improved coding and overall quality Start building with these today via the Gemini API in Google AI Studio or try them out in the Google Gemini
0:42

Today, we're introducing not one but TWO new models, striking the balance between efficiency and quality to enable you to build production AI agents. — Gemini 3.6 Flash: Addresses efficiency feedback we received from Gemini 3.5 Flash with upgrades in coding, knowledge work, and multimodal tasks faster, more accurately, and with substantially fewer tokens per task — Gemini 3.5 Flash-Lite: Our fastest, most cost-effective 3.5-class model yet built for agentic workflows, hitting ~350 output tokens/sec with improved coding and overall quality Start building with these today via the Gemini API in Google AI Studio or try them out in the Google Gemini

Google AI

349,679 görüntüleme • 1 gün önce

Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.
0:22

Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.

Akshay 🚀

39,331 görüntüleme • 5 ay önce

Last week $TEAM outlined a new AI bull case for SaaS, as a source of context to generate better, faster, cheaper AI outcomes. Atlassian demod how Claude Code by itself underperformed an identical instance of Claude Code, on an identical prompt, when the other instance had access to their Teamwork Graph (TWG) which has access to past project files, messages, documents, code bases, employee data, and system integrations (slack, outlook, etc). The added context pointed Claude to the right information to solve the task faster, whereas the instance without context thought more, read more, hallucinated, and got the task incorrect after spending 2x more tokens and running an extra minute. Since token spend is quickly becoming many multiples of traditional software cost for coding use cases (Jira at $10-12/seat vs Anthropic spend per seat in the several hundreds a month), Atlassian makes a compelling case that context pays for itself many times over by helping customers to get more value out of their expensive AI tokens. $MSFT easily has the strongest advantage as a source of differentiated context. Video worth watching.
4:52

Last week $TEAM outlined a new AI bull case for SaaS, as a source of context to generate better, faster, cheaper AI outcomes. Atlassian demod how Claude Code by itself underperformed an identical instance of Claude Code, on an identical prompt, when the other instance had access to their Teamwork Graph (TWG) which has access to past project files, messages, documents, code bases, employee data, and system integrations (slack, outlook, etc). The added context pointed Claude to the right information to solve the task faster, whereas the instance without context thought more, read more, hallucinated, and got the task incorrect after spending 2x more tokens and running an extra minute. Since token spend is quickly becoming many multiples of traditional software cost for coding use cases (Jira at $10-12/seat vs Anthropic spend per seat in the several hundreds a month), Atlassian makes a compelling case that context pays for itself many times over by helping customers to get more value out of their expensive AI tokens. $MSFT easily has the strongest advantage as a source of differentiated context. Video worth watching.

SouthernValue

31,196 görüntüleme • 2 ay önce

New course to bring you up to state-of-the-art at using AI to help you code: Build Apps with Windsurf's AI Coding Agents, built in partnership with WIndsurf (Codeium) and taught by Anshul Ramachandran! AI-assisted IDEs (Integrated Development Environments) make developers’ workflows faster, more efficient, and much more fun. Agentic tools like Windsurf are more than just code autocomplete—they are collaborative coding agents that help you break down complex applications, iterate efficiently, and generate code that spans multiple files. Although a lot of coding assistants share the same underlying large language models for planning and reasoning, a major point of distinction is how they handle tools, keep track of context, and stay aligned with your intent as a developer. For instance, if you make modifications to a class definition in your code and make the same modifications to other classes in the same directory, you might tell the AI agent "Do the same thing in similar places in this directory." Here, tracking your intent means understanding that “the same thing" refers to that recent edit you just made, which must be followed by appropriate search and tool-calling to implement the changes. In this course, you'll learn the inner workings of coding agents, their strengths and limitations, and how to use Windsurf to quickly build several applications. In detail, you'll: - Build a mental model of how agents work by combining human-action tracking, tool integration, and context awareness to carry out an agentic coding workflow. - Learn the challenges of code search and discovery and how a multi-step retrieval approach helps coding agents address them. - Use Windsurf to analyze and understand a large, old codebase and update it to the latest versions of the frameworks and packages it uses. - Build a Wikipedia data analysis app that retrieves, parses, and analyzes word frequencies. - Enhance the performance of your Wikipedia analysis app by adding caching, and through this, also learn how to course-correct when the AI agent produces unexpected results. - Learn tips and tricks such as keyboard shortcuts, autocomplete, and @ mentions to quickly call on agentic capabilities. - Use image/multimodal capabilities of the AI agent to increase your development velocity; you'll see an example of uploading a mockup with sketched-out UI features, and ask the agent to use that to build new functionality to an app. By the end of this course, you’ll understand agentic coding in-depth and know how to use it to make your development process much faster, more efficient, and enjoyable. Please sign up here!
4:01

New course to bring you up to state-of-the-art at using AI to help you code: Build Apps with Windsurf's AI Coding Agents, built in partnership with WIndsurf (Codeium) and taught by Anshul Ramachandran! AI-assisted IDEs (Integrated Development Environments) make developers’ workflows faster, more efficient, and much more fun. Agentic tools like Windsurf are more than just code autocomplete—they are collaborative coding agents that help you break down complex applications, iterate efficiently, and generate code that spans multiple files. Although a lot of coding assistants share the same underlying large language models for planning and reasoning, a major point of distinction is how they handle tools, keep track of context, and stay aligned with your intent as a developer. For instance, if you make modifications to a class definition in your code and make the same modifications to other classes in the same directory, you might tell the AI agent "Do the same thing in similar places in this directory." Here, tracking your intent means understanding that “the same thing" refers to that recent edit you just made, which must be followed by appropriate search and tool-calling to implement the changes. In this course, you'll learn the inner workings of coding agents, their strengths and limitations, and how to use Windsurf to quickly build several applications. In detail, you'll: - Build a mental model of how agents work by combining human-action tracking, tool integration, and context awareness to carry out an agentic coding workflow. - Learn the challenges of code search and discovery and how a multi-step retrieval approach helps coding agents address them. - Use Windsurf to analyze and understand a large, old codebase and update it to the latest versions of the frameworks and packages it uses. - Build a Wikipedia data analysis app that retrieves, parses, and analyzes word frequencies. - Enhance the performance of your Wikipedia analysis app by adding caching, and through this, also learn how to course-correct when the AI agent produces unexpected results. - Learn tips and tricks such as keyboard shortcuts, autocomplete, and @ mentions to quickly call on agentic capabilities. - Use image/multimodal capabilities of the AI agent to increase your development velocity; you'll see an example of uploading a mockup with sketched-out UI features, and ask the agent to use that to build new functionality to an app. By the end of this course, you’ll understand agentic coding in-depth and know how to use it to make your development process much faster, more efficient, and enjoyable. Please sign up here!

Andrew Ng

139,826 görüntüleme • 1 yıl önce

Today, we’re introducing new tools and model updates to help you build, deploy, and scale Voice AI applications.🎙️ 🆕 Speech Understanding: Turn transcripts into actionable data with speaker identification, custom formatting & translation 🆕 LLM Gateway: One API for your voice-to-intelligence pipeline, with GPT, Claude, Gemini & more 🆕 Voice AI Guardrails: End-to-end protection for safe, compliant content Model Upgrades: ✅ 99 languages with auto code-switching ✅ 64% fewer speaker counting errors ✅ 57% better accuracy on critical terms with 1,000-word context Real results: 🔥 Calabrio: 80% boost in customer satisfaction, 22% revenue increase 🔥 Siro: "10/10 customers say 'wow, that insight was crisp'" Build & scale Voice AI in minutes! Try it in our Playground or check the docs. 🚀
0:58

Today, we’re introducing new tools and model updates to help you build, deploy, and scale Voice AI applications.🎙️ 🆕 Speech Understanding: Turn transcripts into actionable data with speaker identification, custom formatting & translation 🆕 LLM Gateway: One API for your voice-to-intelligence pipeline, with GPT, Claude, Gemini & more 🆕 Voice AI Guardrails: End-to-end protection for safe, compliant content Model Upgrades: ✅ 99 languages with auto code-switching ✅ 64% fewer speaker counting errors ✅ 57% better accuracy on critical terms with 1,000-word context Real results: 🔥 Calabrio: 80% boost in customer satisfaction, 22% revenue increase 🔥 Siro: "10/10 customers say 'wow, that insight was crisp'" Build & scale Voice AI in minutes! Try it in our Playground or check the docs. 🚀

AssemblyAI

18,105 görüntüleme • 9 ay önce

New course: Gemini CLI: Code & Create with an Open-Source Agent, built with Google Cloud Tech/Gemini CLI and taught by Jack Wotherspoon. Agentic coding assistants like Gemini CLI are transforming how developers work. This short course teaches you to use Google's open-source agent to coordinate local tools and cloud services for coding and non-coding workflows. Gemini CLI works from your terminal, so it works with your local files and development tools. You can also connect it to services through MCP. Then provide high-level instructions, and it autonomously plans and executes complex workflows. Skills you'll gain: - Build website features and automate code reviews with GitHub ActionsCreate data dashboards that combine local files with cloud data sources - Use MCP servers and extensions to orchestrate workflows across GitHub, Canva, and Google Workspace - Generate social media content from multimedia files like conference recordings I particularly appreciate that Gemini CLI is open-source. You can see exactly how it works, read the prompts it uses, and understand its architecture. The community has contributed thousands of pull requests. Since Gemini 3’s release I've found Gemini CLI highly capable - this is a tool worth having in your toolbox! Whether you're prototyping applications, automating workflows, or working with multimedia content, join to learn to delegate complex tasks and build faster:
2:50

New course: Gemini CLI: Code & Create with an Open-Source Agent, built with Google Cloud Tech/Gemini CLI and taught by Jack Wotherspoon. Agentic coding assistants like Gemini CLI are transforming how developers work. This short course teaches you to use Google's open-source agent to coordinate local tools and cloud services for coding and non-coding workflows. Gemini CLI works from your terminal, so it works with your local files and development tools. You can also connect it to services through MCP. Then provide high-level instructions, and it autonomously plans and executes complex workflows. Skills you'll gain: - Build website features and automate code reviews with GitHub ActionsCreate data dashboards that combine local files with cloud data sources - Use MCP servers and extensions to orchestrate workflows across GitHub, Canva, and Google Workspace - Generate social media content from multimedia files like conference recordings I particularly appreciate that Gemini CLI is open-source. You can see exactly how it works, read the prompts it uses, and understand its architecture. The community has contributed thousands of pull requests. Since Gemini 3’s release I've found Gemini CLI highly capable - this is a tool worth having in your toolbox! Whether you're prototyping applications, automating workflows, or working with multimedia content, join to learn to delegate complex tasks and build faster:

Andrew Ng

124,823 görüntüleme • 6 ay önce

BREAKING: our AI Agents can now deep-research 10,000 accounts faster (and cheaper) than an Uber from JFK. Last month our growth team pushed this hard: 40,000 accounts deep-researched for product launches → personalized outreach → 15+ meetings and a closed-won in 30 days. Most GTM teams don’t lack ideas. They struggle with the cost and complexity of running them at scale. Kunal , who leads our agent infrastructure, saw this firsthand. Adoption climbed past 1M runs per month, but cost was still the ceiling on pushing always-on workflows. After months of evaluating models against real customer workflows, Kunal & team shipped a major upgrade: Optimized agents with peak performance at a 10x cost reduction. Always-on intelligence in outbound becomes practical, not theoretical. What this unlocks: If you’re a cybersecurity company, Unify’s optimized agents can: (1) Monitor your entire TAM for breaches (2) Auto-qualify accounts if they’re B2B + using Auth0 (3) Use real breach context to write outbound that’s timely, relevant, human No manual research. No painful copywriting. No cost tradeoffs. The future of GTM is deploying 100,000 deep-research agents daily to understand every shift in your market. That future is closer than people think.
3:17

BREAKING: our AI Agents can now deep-research 10,000 accounts faster (and cheaper) than an Uber from JFK. Last month our growth team pushed this hard: 40,000 accounts deep-researched for product launches → personalized outreach → 15+ meetings and a closed-won in 30 days. Most GTM teams don’t lack ideas. They struggle with the cost and complexity of running them at scale. Kunal , who leads our agent infrastructure, saw this firsthand. Adoption climbed past 1M runs per month, but cost was still the ceiling on pushing always-on workflows. After months of evaluating models against real customer workflows, Kunal & team shipped a major upgrade: Optimized agents with peak performance at a 10x cost reduction. Always-on intelligence in outbound becomes practical, not theoretical. What this unlocks: If you’re a cybersecurity company, Unify’s optimized agents can: (1) Monitor your entire TAM for breaches (2) Auto-qualify accounts if they’re B2B + using Auth0 (3) Use real breach context to write outbound that’s timely, relevant, human No manual research. No painful copywriting. No cost tradeoffs. The future of GTM is deploying 100,000 deep-research agents daily to understand every shift in your market. That future is closer than people think.

Austin Hughes

41,139 görüntüleme • 7 ay önce

Even my kids know that in a world full of Tesla Robotaxis, Waymo is dunzo. It’s really not that complicated. Waymo needs expensive LiDAR, radar, cameras, specialized hardware, detailed maps, and a massive amount of infrastructure just to operate in certain areas. Tesla’s approach is completely different. Cameras are cheap. Tesla can mass-produce vehicles at a scale Waymo can’t come close to, use the same AI system across millions of cars, collect massive amounts of real-world driving data, and improve the entire fleet through software updates. That’s where the economics become almost impossible to compete with. The cheaper you can build the car, the cheaper you can operate it, and the more vehicles you can put on the road, the cheaper you can eventually make every ride. Waymo might prove Robotaxis can work. Tesla’s goal is to make them cheap enough and build enough of them to be everywhere. That’s the difference people still don’t understand. This isn’t just about who has the better Robotaxi today. It’s about who can build millions of them, drive down the cost per mile, and scale across the world. Even my kids understand the end game. Tesla Robotaxis are going to be everywhere. In the world where Tesla Robotaxis are flooded all around the world, it will very difficult for Waymo to survive.
0:28

Even my kids know that in a world full of Tesla Robotaxis, Waymo is dunzo. It’s really not that complicated. Waymo needs expensive LiDAR, radar, cameras, specialized hardware, detailed maps, and a massive amount of infrastructure just to operate in certain areas. Tesla’s approach is completely different. Cameras are cheap. Tesla can mass-produce vehicles at a scale Waymo can’t come close to, use the same AI system across millions of cars, collect massive amounts of real-world driving data, and improve the entire fleet through software updates. That’s where the economics become almost impossible to compete with. The cheaper you can build the car, the cheaper you can operate it, and the more vehicles you can put on the road, the cheaper you can eventually make every ride. Waymo might prove Robotaxis can work. Tesla’s goal is to make them cheap enough and build enough of them to be everywhere. That’s the difference people still don’t understand. This isn’t just about who has the better Robotaxi today. It’s about who can build millions of them, drive down the cost per mile, and scale across the world. Even my kids understand the end game. Tesla Robotaxis are going to be everywhere. In the world where Tesla Robotaxis are flooded all around the world, it will very difficult for Waymo to survive.

Teslaconomics

32,832 görüntüleme • 12 gün önce

For developers, Gemini 3 Pro offers unparalleled results across every major AI benchmark compared to Gemini 2.5 Pro. Here three ways Gemini 3 Pro can improve your workflow today: 1. Gemini 3 Pro fits right into existing production agent and coding workflows. It is also integrated into development environment experiences across the ecosystem of developer products like Google AI Studio, Gemini CLI, and Android Studio. 2. We introduced Google Google Antigravity, a new agentic development platform that reimagines how the model and IDE work together. It enables developers to manage agents to work at a higher, task-oriented level collaborating with agents while they build. 3. We’ve built Google AI Studio to be your fastest path from a prompt to an AI-native app. Build mode lets you add AI capabilities faster than ever, automatically wiring up the right models and APIs, while features like annotations enable fast and intuitive iteration. Whether you’re building a one-shot prompt game or an interactive landing page from unstructured voice notes, you can bring any idea to life with Gemini 3.
0:48

For developers, Gemini 3 Pro offers unparalleled results across every major AI benchmark compared to Gemini 2.5 Pro. Here three ways Gemini 3 Pro can improve your workflow today: 1. Gemini 3 Pro fits right into existing production agent and coding workflows. It is also integrated into development environment experiences across the ecosystem of developer products like Google AI Studio, Gemini CLI, and Android Studio. 2. We introduced Google Google Antigravity, a new agentic development platform that reimagines how the model and IDE work together. It enables developers to manage agents to work at a higher, task-oriented level collaborating with agents while they build. 3. We’ve built Google AI Studio to be your fastest path from a prompt to an AI-native app. Build mode lets you add AI capabilities faster than ever, automatically wiring up the right models and APIs, while features like annotations enable fast and intuitive iteration. Whether you’re building a one-shot prompt game or an interactive landing page from unstructured voice notes, you can bring any idea to life with Gemini 3.

Google AI

136,589 görüntüleme • 8 ay önce