Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

GPT Engineer app (<- different from CLI) lets backend devs - connect to frontend codebase (on github) - add openapi of the backend - ask for complex frontned changes, get instant previews, which use github codebase as single source of truth example shared in our discord by Kristian Kyvik

Anton Osika

79,815 subscribers

14,157 просмотров • 2 лет назад •via X (Twitter)

Образование Наука и технологии Новости и политика

Anya Rossi• Live Now

Private livecam show

Комментарии: 9

Фото профиля Anton Osika

Anton Osika2 лет назад

waitlist:

Фото профиля Owen Colegrove

Owen Colegrove2 лет назад

it's looking good, Anton

Фото профиля Kostas Livieratos

Kostas Livieratos2 лет назад

how come it's frontend only till now?

Фото профиля Robert Alward

Robert Alward2 лет назад

Sick! Is there a GitHub repo for it?

Фото профиля techfren

techfren2 лет назад

amazing

Фото профиля SGM

SGM2 лет назад

Awesome if I were to give some suggestion I would say that if gpt engineer could have support for more languages and their associated frameworks then it would be pretty nice imo something like like self learning new material would be nuts @antonosika

Фото профиля Shay Ronen 🚀

Shay Ronen 🚀2 лет назад

Can gpt engineer process and understand a whole repository?

Фото профиля Anton Osika

Anton Osika2 лет назад

Yes:) If it’s too large it’s limited

Фото профиля Sharp🦎

Sharp🦎2 лет назад

@rattibha

Похожие видео

👶🤖 Introducing `gpt-engineer` ▸ One prompt generates a codebase ▸ Asks clarifying questions ▸ Generates technical spec ▸ Writes all necessary code ▸ Easy to add your own reasoning steps, modify, and experiment ▸ open source: ▸ Lets you finish a coding project in minutes. swyx scooped me on releasing first ❤️ – similarities to smol but many new innovations, check README. Next, make it bootstrap. Which means: A "gpt engineer" prompt should generate all functionality of the gpt-engineer repo itself.

👶🤖 Introducing `gpt-engineer` ▸ One prompt generates a codebase ▸ Asks clarifying questions ▸ Generates technical spec ▸ Writes all necessary code ▸ Easy to add your own reasoning steps, modify, and experiment ▸ open source: ▸ Lets you finish a coding project in minutes. swyx scooped me on releasing first ❤️ – similarities to smol but many new innovations, check README. Next, make it bootstrap. Which means: A "gpt engineer" prompt should generate all functionality of the gpt-engineer repo itself.

Anton Osika

664,715 просмотров • 3 лет назад

Introducing Deep Graph Codebase to MCP with One Click... Now Available for Gemini CLI too! 🤩 Transform any public GitHub repository into an AI-ready Code Graph by simply changing the URL from to This instantly prepares the repository for seamless integration with AI assistants. It's that easy! You can now use repositories like ollama as a code graph within any project using Gemini CLI... just add the MCP Server JSON configuration to your .gemini/settings.json file

Introducing Deep Graph Codebase to MCP with One Click... Now Available for Gemini CLI too! 🤩 Transform any public GitHub repository into an AI-ready Code Graph by simply changing the URL from to This instantly prepares the repository for seamless integration with AI assistants. It's that easy! You can now use repositories like ollama as a code graph within any project using Gemini CLI... just add the MCP Server JSON configuration to your .gemini/settings.json file

Daniel San

53,516 просмотров • 1 год назад

working theory for a new vibe code workflow: 1. create a proof of concept in v0 2. move to github and clone in a local repo 3. use as ref for agent planning 4. create a backend directory to test API plumbing 5. create a frontend directory to prototype iteratively this way you can repeatedly rip apart the frontend for ideation without worrying about breaking changes to the backend. i really like asking for an open ended "job to be done" (i.e. place a bet with a single tap) with 5-10 variations to feel. it's the modern day wireframing. it's still UI slop but i can get ideas in my head out faster and reveal design shortcomings before polishing or worrying about making components functional. and because the v0 prototype gets you to functional ai features and backend integration fastest, you have both a technical and conceptual reference to use in your agentic planning so your v1 is more predictable with minimal effort.

working theory for a new vibe code workflow: 1. create a proof of concept in v0 2. move to github and clone in a local repo 3. use as ref for agent planning 4. create a backend directory to test API plumbing 5. create a frontend directory to prototype iteratively this way you can repeatedly rip apart the frontend for ideation without worrying about breaking changes to the backend. i really like asking for an open ended "job to be done" (i.e. place a bet with a single tap) with 5-10 variations to feel. it's the modern day wireframing. it's still UI slop but i can get ideas in my head out faster and reveal design shortcomings before polishing or worrying about making components functional. and because the v0 prototype gets you to functional ai features and backend integration fastest, you have both a technical and conceptual reference to use in your agentic planning so your v1 is more predictable with minimal effort.

0xDesigner

14,912 просмотров • 6 месяцев назад

Your Google Maps listing gets views… but you don’t own the traffic. Build a full website or app from a single prompt with Autocoder. Autocoder generates frontend, backend, and database instantly — giving you a ready-to-deploy product in minutes. Features: Prompt → Full App → Deployment ☑️ Fully exportable frontend + backend code ☑️ Export complete source code ☑️ Instant custom domain launch ☑️ Templates for cafes, portfolios, e-commerce & local businesses ☑️ Built-in admin dashboard (manage content, users, bookings) 📈 Turn Google Maps traffic into your own website visitors with Autocoder. ⚡ What you get: • Ready-to-use backend + database (no developer needed) • Built-in admin dashboard to manage content, users, and bookings • Scalable workflow for building sites for multiple local businesses • Full source code export for Pro users to modify or extend AutoCoder.cc #Autocoder #AIWeb #NoCodeAI #WebGenerator

Your Google Maps listing gets views… but you don’t own the traffic. Build a full website or app from a single prompt with Autocoder. Autocoder generates frontend, backend, and database instantly — giving you a ready-to-deploy product in minutes. Features: Prompt → Full App → Deployment ☑️ Fully exportable frontend + backend code ☑️ Export complete source code ☑️ Instant custom domain launch ☑️ Templates for cafes, portfolios, e-commerce & local businesses ☑️ Built-in admin dashboard (manage content, users, bookings) 📈 Turn Google Maps traffic into your own website visitors with Autocoder. ⚡ What you get: • Ready-to-use backend + database (no developer needed) • Built-in admin dashboard to manage content, users, and bookings • Scalable workflow for building sites for multiple local businesses • Full source code export for Pro users to modify or extend AutoCoder.cc #Autocoder #AIWeb #NoCodeAI #WebGenerator

Ai With Piyas

20,612 просмотров • 3 месяцев назад

OPENAI TEAM: GPT-5 SPOTS HIDDEN SECURITY DECISION IN MINUTES "When we got access to GPT-5, we immediately set about using it on our actual work. As a test, we asked it to tell us something non-obvious about our codebase. Within a couple of minutes, it dove into the codebase, identified a particular system we use for remote code execution, and spotted a non-obvious architecture decision we had made. It also understood why we made that decision, to harden our security." Source: OpenAI

OPENAI TEAM: GPT-5 SPOTS HIDDEN SECURITY DECISION IN MINUTES "When we got access to GPT-5, we immediately set about using it on our actual work. As a test, we asked it to tell us something non-obvious about our codebase. Within a couple of minutes, it dove into the codebase, identified a particular system we use for remote code execution, and spotted a non-obvious architecture decision we had made. It also understood why we made that decision, to harden our security." Source: OpenAI

Mario Nawfal

66,009 просмотров • 11 месяцев назад

Different AI models find different bugs. So why not use all of them? Try this out in Copilot CLI: 1. Run /review 2. Ask it to use multiple model providers at once for a multi-agent code review 3. Get the highest possible signal and catch bugs before anyone else Evan Boyle shows how it's done. ▶️

Different AI models find different bugs. So why not use all of them? Try this out in Copilot CLI: 1. Run /review 2. Ask it to use multiple model providers at once for a multi-agent code review 3. Get the highest possible signal and catch bugs before anyone else Evan Boyle shows how it's done. ▶️

GitHub

47,649 просмотров • 4 месяцев назад

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.

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 просмотров • 1 месяц назад

🔥 💻 🎥 How to provide o1 Pro with your FULL CODEBASE through the ChatGPT Cursor connection yesterday I recorded a video connecting o1 Pro to Cursor through the ChatGPT Desktop app more than one person commented on how limiting it is for o1 Pro to only have access to a single open file in Cursor here's a walkthrough of how you can provide o1 Pro with your FULL CODEBASE as context instead of just a single file: 1. Write a Python function that concatenates full codebase into a single snapshot in a .txt file (link in comment) 2. Open that "codebase_snapshot.txt" in a separate Cursor pane 3. Go to the ChatGPT app and ask it what context it has access to through Cursor - should say it has two files with one of them being the codebase snapshot and boom there ya go. o1 Pro has access to everything in your codebase full walkthrough here 👇

🔥 💻 🎥 How to provide o1 Pro with your FULL CODEBASE through the ChatGPT Cursor connection yesterday I recorded a video connecting o1 Pro to Cursor through the ChatGPT Desktop app more than one person commented on how limiting it is for o1 Pro to only have access to a single open file in Cursor here's a walkthrough of how you can provide o1 Pro with your FULL CODEBASE as context instead of just a single file: 1. Write a Python function that concatenates full codebase into a single snapshot in a .txt file (link in comment) 2. Open that "codebase_snapshot.txt" in a separate Cursor pane 3. Go to the ChatGPT app and ask it what context it has access to through Cursor - should say it has two files with one of them being the codebase snapshot and boom there ya go. o1 Pro has access to everything in your codebase full walkthrough here 👇

Dan McAteer

99,719 просмотров • 1 год назад

> Launching: @TheRepolyze - a free, open-source AI-powered tool that helps you deeply understand any public GitHub repository in seconds. > Just paste the repo URL and instantly get: • Clear, actionable insights into the codebase • Beautiful architecture & dependency diagrams • Code quality overview, strengths, weaknesses & potential red flags • Exportable PDF/Markdown reports for sharing or reference > Say goodbye to spending hours (or days) manually digging through unfamiliar code - whether you're contributing, reviewing, onboarding, or just exploring open source. > Built for developers, by developers. > Reposts and feedback greatly appreciated - let's get this in front of more devs! ❤️ > If you find it useful, please star the repo on GitHub to show support & help it grow

> Launching: @TheRepolyze - a free, open-source AI-powered tool that helps you deeply understand any public GitHub repository in seconds. > Just paste the repo URL and instantly get: • Clear, actionable insights into the codebase • Beautiful architecture & dependency diagrams • Code quality overview, strengths, weaknesses & potential red flags • Exportable PDF/Markdown reports for sharing or reference > Say goodbye to spending hours (or days) manually digging through unfamiliar code - whether you're contributing, reviewing, onboarding, or just exploring open source. > Built for developers, by developers. > Reposts and feedback greatly appreciated - let's get this in front of more devs! ❤️ > If you find it useful, please star the repo on GitHub to show support & help it grow

Manish Kumar

32,858 просмотров • 4 месяцев назад

introducing OpenBench v1, an open framework for measuring AI performance and efficiency for your codebase and use case. Companies are realizing that you can't simply tokenmaxx, and are frantically looking for better ways to use and measure AI use and efficiency. One approach is evidenced by the rise in model routers: OpenRouter, Cloudflare, Databricks, Vercel, and now Ramp to name a few. But they'll also need the ability to evaluate how agents are performing in their actual use cases and codebase. A good example is DoorDash's recent evals on their codebase and prs. This will become even more important as companies explore different model + harness combinations. OpenBench will be built to this direction, focusing on the cross between correctness vs efficiency in both token use and latency. Starting off, OpenBench makes it easy for anyone to add to the task set, and run a variety of harness + models. The framework also makes it easy to add any custom harness variant, for example I've been testing codex variants with ablations against the stock codex harness. OpenBench will also have tooling to help with discovering/adding reliable tasks from your repo. Today I have integrated harnesses: codex, claude, cursor, devin, grok build, pi, and eval'ed them for different models like gpt 5.6-sol, GLM 5.2, Kimi K3, Grok 4.5, etc. measuring correctness %, token use (in/out/cache), and latency.

introducing OpenBench v1, an open framework for measuring AI performance and efficiency for your codebase and use case. Companies are realizing that you can't simply tokenmaxx, and are frantically looking for better ways to use and measure AI use and efficiency. One approach is evidenced by the rise in model routers: OpenRouter, Cloudflare, Databricks, Vercel, and now Ramp to name a few. But they'll also need the ability to evaluate how agents are performing in their actual use cases and codebase. A good example is DoorDash's recent evals on their codebase and prs. This will become even more important as companies explore different model + harness combinations. OpenBench will be built to this direction, focusing on the cross between correctness vs efficiency in both token use and latency. Starting off, OpenBench makes it easy for anyone to add to the task set, and run a variety of harness + models. The framework also makes it easy to add any custom harness variant, for example I've been testing codex variants with ablations against the stock codex harness. OpenBench will also have tooling to help with discovering/adding reliable tasks from your repo. Today I have integrated harnesses: codex, claude, cursor, devin, grok build, pi, and eval'ed them for different models like gpt 5.6-sol, GLM 5.2, Kimi K3, Grok 4.5, etc. measuring correctness %, token use (in/out/cache), and latency.

Matthew Lam

78,725 просмотров • 19 часов назад

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."

MTS

26,902 просмотров • 2 месяцев назад

These days you can access AI agents that execute commands, browse the web, and coordinate with other agents. But you should always make sure they're safe to use! 👀 Season 4 of GitHub's Secure Code Game lets you test your knowledge by hacking one yourself. Get started in minutes right from your browser with GitHub Codespaces (for free!). 👇

These days you can access AI agents that execute commands, browse the web, and coordinate with other agents. But you should always make sure they're safe to use! 👀 Season 4 of GitHub's Secure Code Game lets you test your knowledge by hacking one yourself. Get started in minutes right from your browser with GitHub Codespaces (for free!). 👇

GitHub

65,293 просмотров • 3 месяцев назад

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

Nav Toor

392,570 просмотров • 3 месяцев назад

This is my assignment for a SF startup as a backend and infra engineer the main goal was to build a workflow engine that executes directed acyclic graphs of tasks for this assessment the task would arbitrary HTTP endpoints. But I replaced it with my own usage of news aggregator from hackernews, github (top repos for VAE, and libs related to Pytorch) and threads on reddit related to topic ML This I can use in many paid gigs too as a CD deployements like test > build > deploy staging > tests > deploy prod > notify but for now it handles simple tasks and its built on go, redis, grpc with htmx and tailwindcss

This is my assignment for a SF startup as a backend and infra engineer the main goal was to build a workflow engine that executes directed acyclic graphs of tasks for this assessment the task would arbitrary HTTP endpoints. But I replaced it with my own usage of news aggregator from hackernews, github (top repos for VAE, and libs related to Pytorch) and threads on reddit related to topic ML This I can use in many paid gigs too as a CD deployements like test > build > deploy staging > tests > deploy prod > notify but for now it handles simple tasks and its built on go, redis, grpc with htmx and tailwindcss

Mrinal

144,678 просмотров • 5 месяцев назад

Vibe Coding with Codex - Complete Guide Build a Web App, Desktop App & iOS App with Codex + GPT‑5.5 (No Coding Needed, Beginner Friendly) In this video you will learn: > Vibe Coding Basics + Vocab > How to build a web app using Codex > Add db, auth + storage with Firebase > Github Basics > Add AI Features (API's) > Deploy to internet (Vercel) > Convert Web App into Desktop app & iOS App Chapters 00:00 Intro 01:12 Setting up Codex 01:57 The basics of Vibe Coding and Codex 02:20 Projects, Files, App 03:45 Example App - Microsoft Paint 04:25 Running app locally 06:39 Save My Code - Use Github 10:37 Quick Review before building app 12:24 Building a web app - The Prompt 15:32 Creating Web App Project 16:34 Explaining Firebase (Database, Storage, Auth) 18:42 Setting up Firebase Project 22:54 Prompting Codex to build our app 24:49 Inspect Element - Console 26:24 Verify Data being Stored in Database 27:51 Making Changes to App 31:29 Fixing Storage Permissions with Codex 32:20 GPT API - Adding AI to our app 36:20 Making more changes using screenshots 39:02 Queuing vs Steering 40:23 Deploying our app to Vercel (App on Internet) 43:09 Convert web app to desktop app and iOS app 47:15 Web App and Desktop App work Now 48:36 Now let's run the iOS app 50:27 All three apps work! 51:11 Making Changes to iOS app 52:51 Testing agent skill feature of our app 53:55 Summary of what we did

Vibe Coding with Codex - Complete Guide Build a Web App, Desktop App & iOS App with Codex + GPT‑5.5 (No Coding Needed, Beginner Friendly) In this video you will learn: > Vibe Coding Basics + Vocab > How to build a web app using Codex > Add db, auth + storage with Firebase > Github Basics > Add AI Features (API's) > Deploy to internet (Vercel) > Convert Web App into Desktop app & iOS App Chapters 00:00 Intro 01:12 Setting up Codex 01:57 The basics of Vibe Coding and Codex 02:20 Projects, Files, App 03:45 Example App - Microsoft Paint 04:25 Running app locally 06:39 Save My Code - Use Github 10:37 Quick Review before building app 12:24 Building a web app - The Prompt 15:32 Creating Web App Project 16:34 Explaining Firebase (Database, Storage, Auth) 18:42 Setting up Firebase Project 22:54 Prompting Codex to build our app 24:49 Inspect Element - Console 26:24 Verify Data being Stored in Database 27:51 Making Changes to App 31:29 Fixing Storage Permissions with Codex 32:20 GPT API - Adding AI to our app 36:20 Making more changes using screenshots 39:02 Queuing vs Steering 40:23 Deploying our app to Vercel (App on Internet) 43:09 Convert web app to desktop app and iOS app 47:15 Web App and Desktop App work Now 48:36 Now let's run the iOS app 50:27 All three apps work! 51:11 Making Changes to iOS app 52:51 Testing agent skill feature of our app 53:55 Summary of what we did

Riley Brown

146,128 просмотров • 2 месяцев назад

VIBE CODING TUTORIAL: Creating a Viral Meme Mobile App Without Any Coding in 20 minutes! You can now build multi-step AI workflows on a drag and drop platform, and then connect that workflow to your vibe coded mobile app, in a single cursor prompt. This only scratches the surface on the different workflows you can create like this. IN THIS VIDEO 00:00 Intro 00:36 Overview: MultiStep AI Backend on GLIF 01:33 Using Glif as an API 03:49 The backend for our app 04:36 Structured Outputs (Important for Vibe Coding, skip if you know what these are) 06:40 Image Workflow for the meme 08:34 Let's Protototype on 11:09 Setting this up with Cursor 18:40 Testing with

VIBE CODING TUTORIAL: Creating a Viral Meme Mobile App Without Any Coding in 20 minutes! You can now build multi-step AI workflows on a drag and drop platform, and then connect that workflow to your vibe coded mobile app, in a single cursor prompt. This only scratches the surface on the different workflows you can create like this. IN THIS VIDEO 00:00 Intro 00:36 Overview: MultiStep AI Backend on GLIF 01:33 Using Glif as an API 03:49 The backend for our app 04:36 Structured Outputs (Important for Vibe Coding, skip if you know what these are) 06:40 Image Workflow for the meme 08:34 Let's Protototype on 11:09 Setting this up with Cursor 18:40 Testing with

Riley Brown

58,068 просмотров • 1 год назад

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

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

Hugo

54,481 просмотров • 4 месяцев назад

Factory is better than Devin, Codex, and Jules, and it's not even close. This is not just a fully autonomous software engineer but also a product manager and researcher. It's the entire package you need to build a new project or dramatically expand an existing one. I recorded a quick video so you can see how it works. You can use these autonomous Droids from Factory. Here is what they can do: 1. Build a full production-grade app from scratch 2. Develop new features for an existing codebase 3. Migrations or refactors on your codebase 4. Build integrations 5. Generate complete feature specifications 6. Solve and close issues from your issue management system 7. Do deep research on any software topics And Factory can connect to Linear, GitHub, Google Drive, Slack, Jira, Sentry, GitLab, and Notion to do its work. You can use any of the big models to do what you need.

Factory is better than Devin, Codex, and Jules, and it's not even close. This is not just a fully autonomous software engineer but also a product manager and researcher. It's the entire package you need to build a new project or dramatically expand an existing one. I recorded a quick video so you can see how it works. You can use these autonomous Droids from Factory. Here is what they can do: 1. Build a full production-grade app from scratch 2. Develop new features for an existing codebase 3. Migrations or refactors on your codebase 4. Build integrations 5. Generate complete feature specifications 6. Solve and close issues from your issue management system 7. Do deep research on any software topics And Factory can connect to Linear, GitHub, Google Drive, Slack, Jira, Sentry, GitLab, and Notion to do its work. You can use any of the big models to do what you need.

Santiago

70,099 просмотров • 1 год назад

"You can't VibeCode Complex Apps" they said. That is until "VAAPs" became a thing. You can vibecode your frontend like mzulali did here, and then plug in an n8n agent as the backend. All you have to do is use a webhook to connect them. Ask the vibecode to send data to your n8n webhook url and then await its response. Make sure that the trigger of your agent workflow is a webhook. His workflow was an agent that has access to fal workflows... Each tool is like a different creative "skill" that the AI agent can call when necessary. This will get much easier to create when VibeCode releases their official n8n integration.

"You can't VibeCode Complex Apps" they said. That is until "VAAPs" became a thing. You can vibecode your frontend like mzulali did here, and then plug in an n8n agent as the backend. All you have to do is use a webhook to connect them. Ask the vibecode to send data to your n8n webhook url and then await its response. Make sure that the trigger of your agent workflow is a webhook. His workflow was an agent that has access to fal workflows... Each tool is like a different creative "skill" that the AI agent can call when necessary. This will get much easier to create when VibeCode releases their official n8n integration.

Learn to VibeCode

18,981 просмотров • 1 год назад

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,

Oren Melamed

13,275 просмотров • 2 месяцев назад