Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

An L8 Principal Engineer at Meta shared his agentic workflow, chapter by chapter: Most agent stack posts talks about models and prompts. He shows the operating system around the model: 09:21 - Choosing agent harnesses 11:24 - Global and project memory 16:12 - Skills, and when they backfire 28:29...

rohit4verse's profile picture

Rohit

24,286 subscribers

34,849 Aufrufe • vor 3 Monaten •via X (Twitter)

Wissenschaft & TechnologieBildung
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Do not spend 2 years learning AI agents the slow way Andrew Ng just shared a complete 2-hour roadmap On becoming an agentic AI engineer in 2026: 00:00 - Learn the foundations of AI agents 12:12 - Design agentic workflows 53:27 - Build agents that work in practice 1:20:30 - Create self-improving loops 1:30:19 - Orchestrate multi-agent systems Most people are still learning how to prompt one model Andrew Ng is already teaching the complete stack: Agents → Workflows → Loops → Multi-Agent Systems Prompting is the old workflow Building autonomous systems is the new one Anthropic pays top engineers up to $750K a year to understand this stack Bookmark this and give it two hours today Then read the full graph engineering guide below
1:48:04

Do not spend 2 years learning AI agents the slow way Andrew Ng just shared a complete 2-hour roadmap On becoming an agentic AI engineer in 2026: 00:00 - Learn the foundations of AI agents 12:12 - Design agentic workflows 53:27 - Build agents that work in practice 1:20:30 - Create self-improving loops 1:30:19 - Orchestrate multi-agent systems Most people are still learning how to prompt one model Andrew Ng is already teaching the complete stack: Agents → Workflows → Loops → Multi-Agent Systems Prompting is the old workflow Building autonomous systems is the new one Anthropic pays top engineers up to $750K a year to understand this stack Bookmark this and give it two hours today Then read the full graph engineering guide below

rari

58,117 Aufrufe • vor 3 Monaten

Anthropic engineers just released the best 1-hour course on building agents with Opus 5.5: "Opus 5.5 is the best model for building agentic systems." 00:00 - intro to Managed Agents 07:45 - Opus 5.5 brain + architecture 23:40 - skills, loops, memory graphs 54:00 - agent dreaming and orchestration Prompts → Agents → Loops → Graphs most people will stop after the architecture chapter and call it an agent the last twenty minutes are where the agents start running each other same model, same tokens, completely different week watch it today the full article is below, save it while it is still early ↓
1:38:21

Anthropic engineers just released the best 1-hour course on building agents with Opus 5.5: "Opus 5.5 is the best model for building agentic systems." 00:00 - intro to Managed Agents 07:45 - Opus 5.5 brain + architecture 23:40 - skills, loops, memory graphs 54:00 - agent dreaming and orchestration Prompts → Agents → Loops → Graphs most people will stop after the architecture chapter and call it an agent the last twenty minutes are where the agents start running each other same model, same tokens, completely different week watch it today the full article is below, save it while it is still early ↓

Residual

31,929 Aufrufe • vor 23 Tagen

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 free, and the best thing on graph engineering I have come across Prompts → Agents → Loops → Graphs most people will stop after the memory chapter and call it a system he saves the last twenty minutes for the layer above all of it same model, same tokens, completely different week watch it today the step-by-step guide is below, save it while it is still early ↓
1:13:16

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 free, and the best thing on graph engineering I have come across Prompts → Agents → Loops → Graphs most people will stop after the memory chapter and call it a system he saves the last twenty minutes for the layer above all of it same model, same tokens, completely different week watch it today the step-by-step guide is below, save it while it is still early ↓

Residual

96,159 Aufrufe • vor 1 Monat

MOST PEOPLE BUILD AI AGENTS BACKWARDS. They start with prompts, then add tools, memory, subagents, dashboards, and a graph nobody can debug. Then they wonder why the agent is expensive, confused, and unreliable. The better order is simple: harness first loop second graph only when needed A harness gives the model a workspace, tools, permissions, logs, and a definition of done. A loop lets it try, fail, read feedback, repair, and stop. A graph only makes sense when the workflow branches: approvals, parallel work, durable state, different routes, restart recovery. A graph is not a smarter prompt. A loop is not a production system. A harness is not just a system prompt. Most agents do not fail because the model is weak. They fail because nobody defined what success means.
2:07

MOST PEOPLE BUILD AI AGENTS BACKWARDS. They start with prompts, then add tools, memory, subagents, dashboards, and a graph nobody can debug. Then they wonder why the agent is expensive, confused, and unreliable. The better order is simple: harness first loop second graph only when needed A harness gives the model a workspace, tools, permissions, logs, and a definition of done. A loop lets it try, fail, read feedback, repair, and stop. A graph only makes sense when the workflow branches: approvals, parallel work, durable state, different routes, restart recovery. A graph is not a smarter prompt. A loop is not a production system. A harness is not just a system prompt. Most agents do not fail because the model is weak. They fail because nobody defined what success means.

Fluixo

12,244 Aufrufe • vor 3 Monaten

An ex-Google engineer just dropped a free 2-hour course on graph engineering and AI agents From prompts to self-improving agents 👇 0% → 00:00 - know when to use loops vs graphs 20% → 20:29 - benchmark 5 memory layers head to head 40% → 49:29 - 8 lessons from AI founders and investors 60% → 1:08:17 - see how a self-improving agent learns 80% → 1:28:12 - wire up tracing and evals 100% → 1:47:15 - understand semantic vs episodic memory Most people still think an agent is just a prompt with tools This shows what actually runs around the model, with open-source code and live demos Worth more than most paid agent courses Bookmark it and watch this weekend 👇
1:58:45

An ex-Google engineer just dropped a free 2-hour course on graph engineering and AI agents From prompts to self-improving agents 👇 0% → 00:00 - know when to use loops vs graphs 20% → 20:29 - benchmark 5 memory layers head to head 40% → 49:29 - 8 lessons from AI founders and investors 60% → 1:08:17 - see how a self-improving agent learns 80% → 1:28:12 - wire up tracing and evals 100% → 1:47:15 - understand semantic vs episodic memory Most people still think an agent is just a prompt with tools This shows what actually runs around the model, with open-source code and live demos Worth more than most paid agent courses Bookmark it and watch this weekend 👇

spect

24,212 Aufrufe • vor 1 Monat

SpaceXAI just dropped full guide on how to run multiple agents "I stopped running Grok Bot as separate chats. now every project gets its own AI team, manager and task board" one Projects Manager agent creates the project, opens the channel and assigns the right agents: • coder • researcher • writer every team gets its own context, tasks and workspace → instead of managing prompts, you manage teams → instead of running one agent, you run an organization SpaceXAI shared the full setup, roles and workflow for running multiple GrokBot teams at once worth more than 100 multi-agent posts on X save now, then read how to build a parallel agent system in the article below
0:32

SpaceXAI just dropped full guide on how to run multiple agents "I stopped running Grok Bot as separate chats. now every project gets its own AI team, manager and task board" one Projects Manager agent creates the project, opens the channel and assigns the right agents: • coder • researcher • writer every team gets its own context, tasks and workspace → instead of managing prompts, you manage teams → instead of running one agent, you run an organization SpaceXAI shared the full setup, roles and workflow for running multiple GrokBot teams at once worth more than 100 multi-agent posts on X save now, then read how to build a parallel agent system in the article below

0xRafy

12,230 Aufrufe • vor 1 Monat

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 Aufrufe • vor 1 Monat

Andrew Ng just released a free 2-hour course on complete Harness Engineering How to go from one prompt to a reliable system of agents that can run, test, and improve themselves: 09:14 - Build your first agent from scratch 33:11 - Master agent loops 1:02:46 - Turn loops into reliable workflows 1:30:15 - Build agents that improve their own work 1:49:05 - Run the complete system without supervision Model → Harness → Reliable Software Most agent tutorials stop once the model can call a tool This one shows you how to build the infrastructure around it within the first 20 minutes Most people are still prompting one agent at a time Andrew Ng is already teaching the layer above: Harnesses that give agents context, tools, tests, and feedback Watch this brilliant course and build the harness Then read the full architecture below ↓
1:48:52

Andrew Ng just released a free 2-hour course on complete Harness Engineering How to go from one prompt to a reliable system of agents that can run, test, and improve themselves: 09:14 - Build your first agent from scratch 33:11 - Master agent loops 1:02:46 - Turn loops into reliable workflows 1:30:15 - Build agents that improve their own work 1:49:05 - Run the complete system without supervision Model → Harness → Reliable Software Most agent tutorials stop once the model can call a tool This one shows you how to build the infrastructure around it within the first 20 minutes Most people are still prompting one agent at a time Andrew Ng is already teaching the layer above: Harnesses that give agents context, tools, tests, and feedback Watch this brilliant course and build the harness Then read the full architecture below ↓

Ichigo

101,815 Aufrufe • vor 2 Monaten

IBM engineers just released a 40-minute deep dive into “Agent Engineering” for building production-ready AI agents “80% of building an AI agent has nothing to do with the model. It is frameworks, tools, skills and risk controls.” 00:00 - the 5 core concepts behind every AI agent 11:07 - choosing frameworks for tools, memory and orchestration 23:01 - when agents need MCP, skills or both 31:04 - designing AI architecture around real production risk The core stack: Agent → Framework → MCP → Skills → Risk → Production This 40-minute workshop will teach you more about production AI agents than most $500 Agent Engineering courses. Watch it today, then read the full agent engineering playbook in the article below ↓
37:51

IBM engineers just released a 40-minute deep dive into “Agent Engineering” for building production-ready AI agents “80% of building an AI agent has nothing to do with the model. It is frameworks, tools, skills and risk controls.” 00:00 - the 5 core concepts behind every AI agent 11:07 - choosing frameworks for tools, memory and orchestration 23:01 - when agents need MCP, skills or both 31:04 - designing AI architecture around real production risk The core stack: Agent → Framework → MCP → Skills → Risk → Production This 40-minute workshop will teach you more about production AI agents than most $500 Agent Engineering courses. Watch it today, then read the full agent engineering playbook in the article below ↓

Morlex

14,597 Aufrufe • vor 3 Monaten

Google just showed the part of the agent stack most people are still underestimating. Not the model. Not the chat UI. The memory substrate around the agent. In this Antigravity segment, Google describes an agent-first environment built around: - agent conversations - agent-produced artifacts - multi-agent orchestration - subagents - hooks - asynchronous task management That is not a nicer IDE. It is what happens when software stops being a sequence of chats and starts becoming a persistent workforce. Karl's article explains why the winning agents will not just be the ones with the smartest rented model. They will be the ones that remember what they did, what they learned, what changed, and what can be trusted. Full breakdown below.
1:25

Google just showed the part of the agent stack most people are still underestimating. Not the model. Not the chat UI. The memory substrate around the agent. In this Antigravity segment, Google describes an agent-first environment built around: - agent conversations - agent-produced artifacts - multi-agent orchestration - subagents - hooks - asynchronous task management That is not a nicer IDE. It is what happens when software stops being a sequence of chats and starts becoming a persistent workforce. Karl's article explains why the winning agents will not just be the ones with the smartest rented model. They will be the ones that remember what they did, what they learned, what changed, and what can be trusted. Full breakdown below.

Karl Mehta

13,930 Aufrufe • vor 4 Monaten

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓
2:05:53

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Lunar

405,009 Aufrufe • vor 3 Monaten

Codex is not just a coding agent anymore. It is becoming a skill-based operating system. Most people still ask it to “build the app”. Better builders give it specialised skills: frontend design browser automation market research lead research Figma implementation copywriting customer research cold email content strategy That is the real shift. One agent with no skills guesses. One agent with the right skills follows a process. The next advantage is not who writes the longest prompt. It is who builds the best toolbelt around the agent. Stop starting every task from zero. Give Codex the skills for the job. Bookmark this before you ask a general agent to do specialist work again.
0:31

Codex is not just a coding agent anymore. It is becoming a skill-based operating system. Most people still ask it to “build the app”. Better builders give it specialised skills: frontend design browser automation market research lead research Figma implementation copywriting customer research cold email content strategy That is the real shift. One agent with no skills guesses. One agent with the right skills follows a process. The next advantage is not who writes the longest prompt. It is who builds the best toolbelt around the agent. Stop starting every task from zero. Give Codex the skills for the job. Bookmark this before you ask a general agent to do specialist work again.

Fluixo

26,556 Aufrufe • vor 4 Monaten

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓
2:04:23

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓

Lunar

12,509 Aufrufe • vor 2 Monaten

Most AI agents do not fail because the prompt is weak. They fail because there is no loop around the prompt. A real loop: - Finds work - Executes - Verifies - Saves state - Stops or escalates If an agent can say “done” without tests, a budget cap and an independent verifier, you built a demo. Prompts make you the operator. Loops make the agent useful while you are offline.
1:12

Most AI agents do not fail because the prompt is weak. They fail because there is no loop around the prompt. A real loop: - Finds work - Executes - Verifies - Saves state - Stops or escalates If an agent can say “done” without tests, a budget cap and an independent verifier, you built a demo. Prompts make you the operator. Loops make the agent useful while you are offline.

Fluixo

16,419 Aufrufe • vor 3 Monaten

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below
2:14:04

Google just released a free 2-hour+ course on full agent engineering. How to go from one prompt to a system that runs while you sleep: 38:46 - Build your first AI agent 54:46 - Connect MCP tools 1:12:43 - Run agents with four loop patterns 1:20:57 - Turn agent loops into graphs 2:22:31 - Build the complete autonomous system Most people are still building one agent and stopping there. Google is already teaching the full stack: Agents → Tools → Loops → Graphs → Autonomous Systems Single agents are the old workflow. Systems that run without you are the new one. This course is worth more than most paid agent engineering bootcamps. Bookmark and watch it today Then read the full graph engineering playbook below

Lunar

198,150 Aufrufe • vor 3 Monaten

Agents need more than a model. Jensen Huang breaks down the enterprise agent stack: models, orchestration, tools with skills, and a secure runtime to hold it all together. This is the NVIDIA toolkit for agents:
0:48

Agents need more than a model. Jensen Huang breaks down the enterprise agent stack: models, orchestration, tools with skills, and a secure runtime to hold it all together. This is the NVIDIA toolkit for agents:

NVIDIA

40,806 Aufrufe • vor 5 Monaten

THIS 11-PAGE CLAUDE LOOP ENGINEERING PLAYBOOK IS THE CHEAT CODE FOR SENIOR DEV PROMOTIONS typing prompts line by line won't get you hired. you need to know how to design self-prompting loops: > Discovery: agent finds its own work from logs, failing tests, and commits > Handoff: tasks execute in isolated git worktrees to prevent parallel collisions > Verification: a second reviewer agent audits the builder's code to catch blind spots > Persistence and Scheduling: code writes to disk and loops run 24/7 on a timer the shift is simple: stop prompting the agent, build the system that prompts it read the full setup blueprint 👇
0:33

THIS 11-PAGE CLAUDE LOOP ENGINEERING PLAYBOOK IS THE CHEAT CODE FOR SENIOR DEV PROMOTIONS typing prompts line by line won't get you hired. you need to know how to design self-prompting loops: > Discovery: agent finds its own work from logs, failing tests, and commits > Handoff: tasks execute in isolated git worktrees to prevent parallel collisions > Verification: a second reviewer agent audits the builder's code to catch blind spots > Persistence and Scheduling: code writes to disk and loops run 24/7 on a timer the shift is simple: stop prompting the agent, build the system that prompts it read the full setup blueprint 👇

Mr. Buzzoni

44,637 Aufrufe • vor 4 Monaten

Every agent needs its own computer: my conversation with Ivan Burazin, CEO of Daytona, about sandboxes and the emerging agent stack. 00:00 Intro 02:13 What is an AI agent sandbox? 03:17 Security risks of running agents locally 05:17 Stateful vs. stateless hyperscalers 07:04 The history of cloud IDEs and the end of localhost 09:45 Do all AI agents need a sandbox? 12:26 Sandbox use cases: RL evals & background agents 14:10 Unpacking the emerging AI Agent Stack 16:20 The unsolved problem of agent memory and learning 19:37 Where sandboxes fit in the agent harness 21:35 OpenAI, Anthropic, and agent SDKs 23:06 Ivan's founder journey: From CodeAnywhere to Daytona 26:59 GTM strategies and building developer communities 33:48 Why customer support is your best GTM strategy 35:34 Leveraging Twitter during the AI super cycle 40:50 The technical anatomy of a sandbox 41:53 Why fast spin-up speeds maximize GPU efficiency 46:09 Firecracker, QEMU, and isolation primitives 49:58 Why sandbox snapshots and state forking matter 51:40 Why Daytona built a custom scheduler from scratch 55:24 The challenge of long-running stateful sandboxes 58:10 The build your own sandbox trap 1:01:03 Why AI agents might trigger a global CPU shortage 1:02:46 The future of the AI Agent Stack
1:05:15

Every agent needs its own computer: my conversation with Ivan Burazin, CEO of Daytona, about sandboxes and the emerging agent stack. 00:00 Intro 02:13 What is an AI agent sandbox? 03:17 Security risks of running agents locally 05:17 Stateful vs. stateless hyperscalers 07:04 The history of cloud IDEs and the end of localhost 09:45 Do all AI agents need a sandbox? 12:26 Sandbox use cases: RL evals & background agents 14:10 Unpacking the emerging AI Agent Stack 16:20 The unsolved problem of agent memory and learning 19:37 Where sandboxes fit in the agent harness 21:35 OpenAI, Anthropic, and agent SDKs 23:06 Ivan's founder journey: From CodeAnywhere to Daytona 26:59 GTM strategies and building developer communities 33:48 Why customer support is your best GTM strategy 35:34 Leveraging Twitter during the AI super cycle 40:50 The technical anatomy of a sandbox 41:53 Why fast spin-up speeds maximize GPU efficiency 46:09 Firecracker, QEMU, and isolation primitives 49:58 Why sandbox snapshots and state forking matter 51:40 Why Daytona built a custom scheduler from scratch 55:24 The challenge of long-running stateful sandboxes 58:10 The build your own sandbox trap 1:01:03 Why AI agents might trigger a global CPU shortage 1:02:46 The future of the AI Agent Stack

Matt Turck

12,242 Aufrufe • vor 5 Monaten

Moving your Coding Agents to the Cloud (ft. Codex Desktop & GPT-6 Astra) 00:00 The limitations of running agents locally 01:13 Parallel development and Git worktrees 02:03 Moving your coding agent to a remote machine 02:25 Introducing Railway Cloud Agents 02:52 Installing the CLI and signing in 03:03 Configuring your project and default agent 03:42 Bringing your agent skills 04:24 Connecting the Codex desktop app 04:48 How SSH configuration works 05:10 Adding the SSH connection in Codex 05:39 Creating a remote project and starting a chat 06:09 Long-running tasks and remote execution 06:26 ChatGPT mobile access 07:03 Using Railway from your coding agent 07:15 Orchestrating multiple cloud agents
8:20

Moving your Coding Agents to the Cloud (ft. Codex Desktop & GPT-6 Astra) 00:00 The limitations of running agents locally 01:13 Parallel development and Git worktrees 02:03 Moving your coding agent to a remote machine 02:25 Introducing Railway Cloud Agents 02:52 Installing the CLI and signing in 03:03 Configuring your project and default agent 03:42 Bringing your agent skills 04:24 Connecting the Codex desktop app 04:48 How SSH configuration works 05:10 Adding the SSH connection in Codex 05:39 Creating a remote project and starting a chat 06:09 Long-running tasks and remote execution 06:26 ChatGPT mobile access 07:03 Using Railway from your coding agent 07:15 Orchestrating multiple cloud agents

Railway

82,044 Aufrufe • vor 2 Monaten

Andrew Ng just released a free 2-hour course on complete Graph Engineering How to go from one prompt to 100 agents that loop, improve, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it finished Andrew Ng is already teaching everything that comes next: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow Systems that improve and run without you are the next one This 2-hour course is worth more than most $500 agent engineering programs Bookmark it and watch before everyone catches up Then read how to run 1,000 agents from one prompt below ↓
1:51:29

Andrew Ng just released a free 2-hour course on complete Graph Engineering How to go from one prompt to 100 agents that loop, improve, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it finished Andrew Ng is already teaching everything that comes next: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow Systems that improve and run without you are the next one This 2-hour course is worth more than most $500 agent engineering programs Bookmark it and watch before everyone catches up Then read how to run 1,000 agents from one prompt below ↓

reira

14,899 Aufrufe • vor 2 Monaten