Loading video...

Video Failed to Load

Go Home

AI code agents that guess from similar-looking code can miss whats actually broken. GitLab Orbit builds one context graph across your code, pipelines, deployments and production so your agent follows real relationships instead. Plus, it works over MCP with any agent you're using. Watch the demo to learn more,...

gitlab's profile picture

🦊 GitLab

172,866 subscribers

1,784,496 views • 13 days ago •via X (Twitter)

Science & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

2 Comments

Laban's profile picture
Laban13 days ago

Code-similarity misses production failures because the bug lives in the graph: pipelines, deploys, and live state. Exposing that graph over MCP is the harness upgrade autocomplete never was.

Evan Kirstel #B2B #TechFluencer's profile picture
Evan Kirstel #B2B #TechFluencer13 days ago

A coding agent needs to understand more than individual files. It should also know about pipelines, deployments and production issues. Would someone from GitLab come on my show to explain how Orbit builds that context?

Related Videos

GitLab Orbit, now in public beta, is the context graph for the entire software lifecycle. It continuously maps code, work items, pipelines, deployments, and production signals into a single live graph, so agents reason from first-party context instead of fragmented signals.
4:00

GitLab Orbit, now in public beta, is the context graph for the entire software lifecycle. It continuously maps code, work items, pipelines, deployments, and production signals into a single live graph, so agents reason from first-party context instead of fragmented signals.

🦊 GitLab

17,876 views • 4 months ago

Introducing the first agent-to-agent code review solution: Qodo’s Agentic Toolbox. Get full codebase context, your coding rules, and AI code review, brought directly to your coding agent. Available now for Claude Code, OpenAI’s Codex, and Kiro, with support for any MCP-compatible client.
0:51

Introducing the first agent-to-agent code review solution: Qodo’s Agentic Toolbox. Get full codebase context, your coding rules, and AI code review, brought directly to your coding agent. Available now for Claude Code, OpenAI’s Codex, and Kiro, with support for any MCP-compatible client.

Qodo

49,613 views • 1 month ago

Introducing Context7 – stop Cursor, Claude or any LLM from generating broken, outdated code. Feed your AI: ◆ Always up-to-date documentation ◆ Real code examples from official docs so it writes code that actually works. Perfect for Next.js, React, Tailwind & more 👇
2:27

Introducing Context7 – stop Cursor, Claude or any LLM from generating broken, outdated code. Feed your AI: ◆ Always up-to-date documentation ◆ Real code examples from official docs so it writes code that actually works. Perfect for Next.js, React, Tailwind & more 👇

Upstash

80,827 views • 1 year 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 ⭣
0:24

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 • 13 days ago

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:
0:23

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:

Atlassian

21,607 views • 4 months ago

Claude R Perrin Code SDK is under-rated One cool part with Claude Code SDK is that it supports full features out of box: - Skills - Sub agents - Hooks - ... Which means you can use claude code CLI as a debug tool to build agent, and then import to your Claude code powered agent Here is a quick example of a pptx presentation agent using Claude Code SDK + doc skills Code example from AI Builder Club by Kai:
0:25

Claude R Perrin Code SDK is under-rated One cool part with Claude Code SDK is that it supports full features out of box: - Skills - Sub agents - Hooks - ... Which means you can use claude code CLI as a debug tool to build agent, and then import to your Claude code powered agent Here is a quick example of a pptx presentation agent using Claude Code SDK + doc skills Code example from AI Builder Club by Kai:

Jason Zhou

11,981 views • 11 months ago

World's first tool that gives AI coding agents full production context. Until now, AI could write your code, but it had no idea what was actually happening in production. We built Comie to change that. Connect your production stack once, and now Claude Code, Cursor, Codex, or any AI coding agent can: - inspect logs - analyze production databases - debug backend issues - trace production errors - understand real production behavior All directly inside your existing workflow. It takes 60 seconds to setup. We're giving first 50 requests free for every user:
1:07

World's first tool that gives AI coding agents full production context. Until now, AI could write your code, but it had no idea what was actually happening in production. We built Comie to change that. Connect your production stack once, and now Claude Code, Cursor, Codex, or any AI coding agent can: - inspect logs - analyze production databases - debug backend issues - trace production errors - understand real production behavior All directly inside your existing workflow. It takes 60 seconds to setup. We're giving first 50 requests free for every user:

yutish

17,133 views • 5 months ago

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use
1:09

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use

Karan Vaidya

62,030 views • 1 year ago

Google Senior Engineer Annie Wang just dropped a free hands-on course on Graph RAG agents, from scratch: Setup → Graph Schema → Embeddings → Hybrid Search (RRF) → ADK Agent → Deploy 0% → 0:00 – a Graph RAG agent with ADK 25% → 13:01 – Build the graph schema and visualize your data 77% → 39:16 – Hybrid search + RRF 84% → 43:05 – Wiring up the ADK agent: runner, session service, memory service 100% → 51:06 – Final demo and deploying the agent with FastAPI This is one of the few guides that walks through real code and architecture, from an empty project to a working agent. Watch it, then build it yourself
51:06

Google Senior Engineer Annie Wang just dropped a free hands-on course on Graph RAG agents, from scratch: Setup → Graph Schema → Embeddings → Hybrid Search (RRF) → ADK Agent → Deploy 0% → 0:00 – a Graph RAG agent with ADK 25% → 13:01 – Build the graph schema and visualize your data 77% → 39:16 – Hybrid search + RRF 84% → 43:05 – Wiring up the ADK agent: runner, session service, memory service 100% → 51:06 – Final demo and deploying the agent with FastAPI This is one of the few guides that walks through real code and architecture, from an empty project to a working agent. Watch it, then build it yourself

Morty

19,362 views • 1 month ago

Don't waste 2 years learning to build AI agents. An Anthropic engineer who built Claude Code tells you what to learn from scratch instead. 60 minutes course. Free: 00:00 - AI agent architecture 24:47 - LangGraph AI agent 29:15 - building AI agents live Prompting is the old job. Building AI agent loops is the new one. Bookmark now & watch it. Then build your own AI agent with the guide below.
1:01:03

Don't waste 2 years learning to build AI agents. An Anthropic engineer who built Claude Code tells you what to learn from scratch instead. 60 minutes course. Free: 00:00 - AI agent architecture 24:47 - LangGraph AI agent 29:15 - building AI agents live Prompting is the old job. Building AI agent loops is the new one. Bookmark now & watch it. Then build your own AI agent with the guide below.

Roan

59,666 views • 2 months ago

Google just dropped the best 1-hour course on Graph Engineering: from one agent to Loops and Graphs 00:00 – Your first AI agent 08:24 – Build agent memory 28:34 – Agentic loops 40:04 – How to build MCP 1:00:22 – Graph engineering This 1-hour watch replaces any $500 course you could pay for. Watch it, then try your first graph with the step-by-step guide below
1:12:14

Google just dropped the best 1-hour course on Graph Engineering: from one agent to Loops and Graphs 00:00 – Your first AI agent 08:24 – Build agent memory 28:34 – Agentic loops 40:04 – How to build MCP 1:00:22 – Graph engineering This 1-hour watch replaces any $500 course you could pay for. Watch it, then try your first graph with the step-by-step guide below

Mahax

129,345 views • 29 days ago

Today we're launching It gives any AI agent ready-to-use security context for thousands of open source projects, built from each project's commit history of security fixes and its disclosed CVEs. Useful whether your agent is writing code or reviewing it for bugs. Free, no auth, over MCP and API.
1:10

Today we're launching It gives any AI agent ready-to-use security context for thousands of open source projects, built from each project's commit history of security fixes and its disclosed CVEs. Useful whether your agent is writing code or reviewing it for bugs. Free, no auth, over MCP and API.

ProjectDiscovery

41,259 views • 3 months ago

New short course: Building Code Agents with Hugging Face smolagents! Learn how to build code agents in this course, created in collaboration with Hugging Face, and taught by Thomas Wolf, its co-founder and CSO, and m_ric, Hugging Face’s Project Lead on Agents. Tool-calling agents use LLMs to generate multiple function calls sequentially to complete a complex sequence of tasks. They generate one function call, execute it, observe, reason, and decide what to do next. Code agents take a different approach. They consolidate all these calls into a single block of code, letting the LLM lay out an entire action plan at once, which can be executed efficiently to provide more reliable results. You’ll learn how to code agents using smolagents, a lightweight agentic framework from Hugging Face. Along the way, you’ll learn how to run LLM-generated code safely and develop an evaluation system to optimize your code agent for production. In detail, you’ll learn: - How agentic systems have evolved, gaining greater levels of agency over time—and why code agents are a next step. - How code agents write their actions in code. - When code agents outperform function-calling agents. - How to run code agents safely in your system using a constrained Python interpreter and sandboxing using E2B. - To trace, debug, and assess the code agent to optimize its behaviours for complex requests. - How to build a research multi-agent system that can find information online and organize it into an interactive report. By the end of this course, you’ll know how to build and run code agents using smolagents, and deploy them safely with a structured evaluation system in your projects. Please sign up here!
2:17

New short course: Building Code Agents with Hugging Face smolagents! Learn how to build code agents in this course, created in collaboration with Hugging Face, and taught by Thomas Wolf, its co-founder and CSO, and m_ric, Hugging Face’s Project Lead on Agents. Tool-calling agents use LLMs to generate multiple function calls sequentially to complete a complex sequence of tasks. They generate one function call, execute it, observe, reason, and decide what to do next. Code agents take a different approach. They consolidate all these calls into a single block of code, letting the LLM lay out an entire action plan at once, which can be executed efficiently to provide more reliable results. You’ll learn how to code agents using smolagents, a lightweight agentic framework from Hugging Face. Along the way, you’ll learn how to run LLM-generated code safely and develop an evaluation system to optimize your code agent for production. In detail, you’ll learn: - How agentic systems have evolved, gaining greater levels of agency over time—and why code agents are a next step. - How code agents write their actions in code. - When code agents outperform function-calling agents. - How to run code agents safely in your system using a constrained Python interpreter and sandboxing using E2B. - To trace, debug, and assess the code agent to optimize its behaviours for complex requests. - How to build a research multi-agent system that can find information online and organize it into an interactive report. By the end of this course, you’ll know how to build and run code agents using smolagents, and deploy them safely with a structured evaluation system in your projects. Please sign up here!

Andrew Ng

127,724 views • 1 year ago

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access
2:15

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 views • 2 months ago

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

229,473 views • 5 months ago

Introducing the Orca Mobile Emulator. AI agents can now use mobile apps inside Orca ADE. Each worktree gets its own emulator — so you and your agents can build, test, debug, and validate mobile flows right where the code lives. Works with Codex, Claude Code, OpenCode, or any agent.
0:35

Introducing the Orca Mobile Emulator. AI agents can now use mobile apps inside Orca ADE. Each worktree gets its own emulator — so you and your agents can build, test, debug, and validate mobile flows right where the code lives. Works with Codex, Claude Code, OpenCode, or any agent.

Orca ADE

31,191 views • 4 months ago

We gave Pi Code persistent memory with Mem0 Launching the Mem0 plugin for Pi Code: persistent, scoped, semantic memory across sessions and projects. It captures what matters, searches by meaning, and brings the right context back when your agent needs it. Try it out: pi install npm:@ mem0/pi-agent-plugin
0:43

We gave Pi Code persistent memory with Mem0 Launching the Mem0 plugin for Pi Code: persistent, scoped, semantic memory across sessions and projects. It captures what matters, searches by meaning, and brings the right context back when your agent needs it. Try it out: pi install npm:@ mem0/pi-agent-plugin

mem0

25,051 views • 3 months ago

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:
1:39

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:

DeepLearning.AI

56,896 views • 2 months ago

.Postman is now natively available in your favorite coding agent! The new Postman CLI is designed to bring API engineering for agents: 1️⃣ Works in Git and your code repo - Just drop Postman where your agent lives and works. 2️⃣ No GUI - Work in your coding agent. Bring up the Postman UI for review and approval. 3️⃣ No sign-up - Get started right away. Sign-up when you have to save your work and want more. Install once, work in your agent. Run npm install -g postman-cli, then postman init. This loads Postman's skills into your coding agent so it can create collections, write tests, and much more. Available as a plugin for all coding agents! The skills cover the API lifecycle: find APIs your org already has, generate tests that catch regressions, mock an API before it exists, watch live endpoints for downtime and drift, run checks in CI on every commit, and run performance tests. You can also extend the abilities of your agent with the Context Graph. An agent often sees only the code that is accessible to them. The Context Graph API gives it a map of your team's infrastructure, APIs, and services, and how they depend on each other. As your agent works, you stay the reviewer. Your agent does the work from the command line. Open Postman when you want to review or approve it. Check out more at
0:37

.Postman is now natively available in your favorite coding agent! The new Postman CLI is designed to bring API engineering for agents: 1️⃣ Works in Git and your code repo - Just drop Postman where your agent lives and works. 2️⃣ No GUI - Work in your coding agent. Bring up the Postman UI for review and approval. 3️⃣ No sign-up - Get started right away. Sign-up when you have to save your work and want more. Install once, work in your agent. Run npm install -g postman-cli, then postman init. This loads Postman's skills into your coding agent so it can create collections, write tests, and much more. Available as a plugin for all coding agents! The skills cover the API lifecycle: find APIs your org already has, generate tests that catch regressions, mock an API before it exists, watch live endpoints for downtime and drift, run checks in CI on every commit, and run performance tests. You can also extend the abilities of your agent with the Context Graph. An agent often sees only the code that is accessible to them. The Context Graph API gives it a map of your team's infrastructure, APIs, and services, and how they depend on each other. As your agent works, you stay the reviewer. Your agent does the work from the command line. Open Postman when you want to review or approve it. Check out more at

Abhinav Asthana

493,187 views • 13 days ago