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

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

На главную

> Define an API > Tell the agent when to call the API > Set it live > It verifies the logged in user and makes API calls with their user_id > The user can do anything on your app by asking the AI Agent I think a lot...

55,715 просмотров • 1 год назад •via X (Twitter)

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

Фото профиля Taylor Johnson
Taylor Johnson1 год назад

The reason apps/websites won’t do this is because it abstracts them from the user. There’s going to be an interesting period where some apps play ball with agents and some don’t. I think over time most will end up letting agents do things but it will take time.

Фото профиля Yasser
Yasser1 год назад

Yeah it will take time but i think you will start seeing it in a few big apps in 2025

Фото профиля Shuayb
Shuayb1 год назад

Can I follow along how to do this with the v0 docs ?

Фото профиля Yanis Ameziane
Yanis Ameziane1 год назад

Can you explain the challenges of building such à system

Фото профиля scan
scan1 год назад

Intent recognition💪

Фото профиля BoredGeekSociety | AI & Automation
BoredGeekSociety | AI & Automation1 год назад

@yasser_elsaid_ can you upload a document via the chat ? Some senarios require asking users for files

Фото профиля Cybertrip.family
Cybertrip.family1 год назад

It already exists:

Фото профиля Julian Harris
Julian Harris1 год назад

I used something similar back in the 90s with MacOS “scriptability”. It exists today in the form of Applescript / OSAscript & now you can use Javascript. Cf Webintents as well.

Фото профиля Allan Caman
Allan Caman1 год назад

Awesome feature! Does it work in when calling through API?

Фото профиля Yasser
Yasser1 год назад

yes, you define the API in chatbase (URL, parameters, body, etc..) and the agent will call it when it needs to.

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

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

I built a mobile app to check Paddle revenue (because they don't have one): 👉 - Use your Paddle API key (read-only and scoped) - Live data with beautiful and useful graphs built with native Swift UI. - Multi-account supported, unified revenue metrics. - Data stay on device, no server (api requests are sent directly from your phone) - Home widgets - I made it free to download on App Store (once it's approved) - Buy the source code for $19 and customize it however you want (save 5hrs of prompting if you try to do it yourself). Some interesting facts about this side project: - I vibe coded with 100% claude code remotely on my Mac Mini (with my AI assistant setup) in less than 24 hours. - I have read 0 line of code in this project and never opened Xcode myself. - My AI assistant designed the app with GPT Image 2, built the app with Swift UI, test it on simulator (via screenshots), send the test build to TestFlight for me to test, and invited me to the app store connect account so I can test on my phone, then the AI submitted the app to App Store and currently waiting for approval. - For the website, I ask it to come up with a domain name, I bought it via manually and give it access via Cloudflare API, the AI design and create a static website with GitHub, test it with lighthouse CLI, deploy via GitHub pages, config the domain DNS, deploy the website. - Then I sign up an account with Polar payment, create an API key and ask the AI to setup a store, add payment, link with the account, and add the payment to the website. The entire process happened in the last 24 hours with me only talking to the AI via Telegram. This is such a fun side project not only to create an app that I wish exists, but also to push the limit of what I can use AI for, and so far I'm very impressed. I'll create so much more apps! It feels like I have unlocked a super power.

Tony Dinh

43,634 просмотров • 1 месяц назад