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

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

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

На главную

If your whole workflow is one Claude Code instance on your MacBook, you're leaving 10x on the table. Here's why. On your laptop, running 2 agents at once means two copies of your code, and you're constantly fighting over which worktree you're on and whether everything's synced. It caps... out fast. Cloud agents in VMs let you run as many as you want without worrying about any of that. Each one gets its own machine, so the work never collides. Spin up 10, let them all run, and nothing steps on anything else. Watch full ep below on The Startup Ideas Podcast (SIP) 🧃. Thanks to Ryan Carson for sharing the sauce. Cloud agents are probably the future. So is doing half your work from your phone, which sounds insane until you try it once. Then you don't go back.show more

GREG ISENBERG

689,176 subscribers

138,986 просмотров • 5 дней назад •via X (Twitter)

Наука и технологии

Anya Rossi• Live Now

Private livecam show

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

Anthropic Claude Code engineer: "If you're watching Claude write code, you're the QA tester. That's not what you're paid for." In 37 minutes he lays out how to get your keyboard out of the hot path entirely. The shift is /loop. You tell Claude to wake up every 10 minutes and babysit your PRs, and it just does it, while you're nowhere near the laptop. Routines do the same in the cloud, so the work keeps running with your machine closed. He caps it with remote control: any session, on any surface, driven from your phone. Watch the full talk, then grab the setup below.

Anthropic Claude Code engineer: "If you're watching Claude write code, you're the QA tester. That's not what you're paid for." In 37 minutes he lays out how to get your keyboard out of the hot path entirely. The shift is /loop. You tell Claude to wake up every 10 minutes and babysit your PRs, and it just does it, while you're nowhere near the laptop. Routines do the same in the cloud, so the work keeps running with your machine closed. He caps it with remote control: any session, on any surface, driven from your phone. Watch the full talk, then grab the setup below.

Hanako

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

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anatoli Kopadze

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

Here is how to set up a team of AI agents to work on your project without disrupting anything. This is the top 1 upgrade you can do to your development environment: Start using dev containers to isolate agents and run them in parallel in their own cloud containers. Let me show you:

Here is how to set up a team of AI agents to work on your project without disrupting anything. This is the top 1 upgrade you can do to your development environment: Start using dev containers to isolate agents and run them in parallel in their own cloud containers. Let me show you:

Santiago

22,742 просмотров • 10 месяцев назад

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Avthar

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

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

André König

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

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch

GREG ISENBERG

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

OpenClaw is the best AI agent I've ever used. I run it every single day. But if you asked me to run it on my laptop full-time, I'd say you're making a mistake. OpenClaw is brilliant for accessing your files, reading your apps, and running local AI tasks. But running it on your own machine creates real problems nobody talks about: • Who's keeping it secure when it's exposed to the internet? • What happens when your laptop sleeps or shuts down? • Where are the access controls? • Who's blocking bad bots from hitting your instance? • What if you don't want to spend $800 on a Mac Mini just to run it? That's the main issue with local AI agents: your laptop was never meant to be a server. As far as I know, DigitalOcean is the only platform making OpenClaw cloud deployment this simple. And the security setup is actually impressive: • secret token authentication • bad bot blocking • limited user permissions • Docker containerization All of this configured automatically when you spin up a Droplet. I really don't see any other way forward for people who want OpenClaw running 24/7 without the hardware headaches. By the way, DigitalOcean runs everything in full isolation. Only you can message your OpenClaw instance. Setup takes about 5 minutes. No Mac Mini required. Here's the link to get started: DigitalOcean collaborated with me on this post.

OpenClaw is the best AI agent I've ever used. I run it every single day. But if you asked me to run it on my laptop full-time, I'd say you're making a mistake. OpenClaw is brilliant for accessing your files, reading your apps, and running local AI tasks. But running it on your own machine creates real problems nobody talks about: • Who's keeping it secure when it's exposed to the internet? • What happens when your laptop sleeps or shuts down? • Where are the access controls? • Who's blocking bad bots from hitting your instance? • What if you don't want to spend $800 on a Mac Mini just to run it? That's the main issue with local AI agents: your laptop was never meant to be a server. As far as I know, DigitalOcean is the only platform making OpenClaw cloud deployment this simple. And the security setup is actually impressive: • secret token authentication • bad bot blocking • limited user permissions • Docker containerization All of this configured automatically when you spin up a Droplet. I really don't see any other way forward for people who want OpenClaw running 24/7 without the hardware headaches. By the way, DigitalOcean runs everything in full isolation. Only you can message your OpenClaw instance. Setup takes about 5 minutes. No Mac Mini required. Here's the link to get started: DigitalOcean collaborated with me on this post.

Hasan Toor

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

Extra! Extra! The Metro Tunnel opens on Sunday November 30. And you can read all about it in this limited run of print. You can pick one up on your commute as you're heading through the city, or from your local station if you're on the Cranbourne, Pakenham or Sunbury Line.

Extra! Extra! The Metro Tunnel opens on Sunday November 30. And you can read all about it in this limited run of print. You can pick one up on your commute as you're heading through the city, or from your local station if you're on the Cranbourne, Pakenham or Sunbury Line.

Jacinta Allan

12,433 просмотров • 8 месяцев назад

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

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

I'm now building Executor full time as a startup! The state of tool calling is a mess: - Everyone is using different agents - You have no idea what actions are going to run - Destructive actions are treated the same as normal Executor lets you set up everything once & use it with any agent. You're able to control what tools can be called, require approval on destructive actions, and invite your team to all use them. Under the hood, it's built on codemode to let you add thousands of tools with 0 context bloat. I've been using it for a month so far and it has completely changed how I interact with agents. There's so much to be built here, immediately next up on the roadmap is workspaces, skills, workflows, and generative ui. Everything is being built open source over at there's a lot more coming on an SDK to embed it into your own agents, a self hostable cloud app, and plugins There's an early beta version over at It's very early on - if you hit any bugs let me know and I'll get them fixed up, excited to share more as I build it!

I'm now building Executor full time as a startup! The state of tool calling is a mess: - Everyone is using different agents - You have no idea what actions are going to run - Destructive actions are treated the same as normal Executor lets you set up everything once & use it with any agent. You're able to control what tools can be called, require approval on destructive actions, and invite your team to all use them. Under the hood, it's built on codemode to let you add thousands of tools with 0 context bloat. I've been using it for a month so far and it has completely changed how I interact with agents. There's so much to be built here, immediately next up on the roadmap is workspaces, skills, workflows, and generative ui. Everything is being built open source over at there's a lot more coming on an SDK to embed it into your own agents, a self hostable cloud app, and plugins There's an early beta version over at It's very early on - if you hit any bugs let me know and I'll get them fixed up, excited to share more as I build it!

Rhys

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

EVERYTHING you NEED to know about Jack Dorsey's AI agent "Slack killer" Buzz (set up, use-cases etc in 38 mins) What we get into: 1. What Buzz actually is and should founders switch from Slack? 2. How to swap the model under any agent and keep all your context? 3. How to talk to your agents live with audio huddles? 4. How to get agents to build and deploy real apps for you, like a full CRM from one ask? 5. How to set up the context loop that feeds your live app data back to your agents? 6. How to share compute so a few people split one machine running a local model? 7. Who it's actually for right now, and what's still rough? Full breakdown on the pod The Startup Ideas Podcast (SIP) 🧃. Thanks to Vinny for jumping on and clearly explaining jack and team's latest product. My TLDR take is Buzz is a glimpse into the future of work. Some of you will roll your eyes at that, and I get it, it's alpha software and it's slow in places. But the core idea, that your context is the foundation and agents build out from there, is right, and that's worth seeing early. Watch Curious what you think

EVERYTHING you NEED to know about Jack Dorsey's AI agent "Slack killer" Buzz (set up, use-cases etc in 38 mins) What we get into: 1. What Buzz actually is and should founders switch from Slack? 2. How to swap the model under any agent and keep all your context? 3. How to talk to your agents live with audio huddles? 4. How to get agents to build and deploy real apps for you, like a full CRM from one ask? 5. How to set up the context loop that feeds your live app data back to your agents? 6. How to share compute so a few people split one machine running a local model? 7. Who it's actually for right now, and what's still rough? Full breakdown on the pod The Startup Ideas Podcast (SIP) 🧃. Thanks to Vinny for jumping on and clearly explaining jack and team's latest product. My TLDR take is Buzz is a glimpse into the future of work. Some of you will roll your eyes at that, and I get it, it's alpha software and it's slow in places. But the core idea, that your context is the foundation and agents build out from there, is right, and that's worth seeing early. Watch Curious what you think

GREG ISENBERG

362,625 просмотров • 1 день назад

There's probably $100+ billion up for grabs for people who build startup for AI agents Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. TLDR; The internet was built for people: 1. Search google 2. Read landing page 3. Book demo 4. Talk to sales 5. Buy Agents don’t do that. Agents will: 1. Ask which product to use 2. Read your docs/pricing/security pages 3. Compare you to competitors 4. Check if you have an MCP/API/tool layer 5. Buy or recommend you without ever “visiting” your site like a person Everyone is going to have personal agents and business agents. This feels inevitable at this point. OpenClaw, Hermes, Claude Code, Codex, Google Spark. The tools are here. Which means there will be more agents on the internet than humans. So, where's the opportunity?? Go look at every SaaS tool you use. Notion. Slack. Jira. Google Analytics. Now ask: what is the version of this built purely for agents? Agent-native payments. Agent-native communication. Agent-native memory. Every category gets rebuilt. I clearly break down this shift and explain you everything on today's ep of The Startup Ideas Podcast (SIP) 🧃. Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. The founders who build for them now are going to look like the people who built websites in 1995. Might feel janky at the moment, but also obvious in hindsight. This is the next shift. Link over here: Watch

There's probably $100+ billion up for grabs for people who build startup for AI agents Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. TLDR; The internet was built for people: 1. Search google 2. Read landing page 3. Book demo 4. Talk to sales 5. Buy Agents don’t do that. Agents will: 1. Ask which product to use 2. Read your docs/pricing/security pages 3. Compare you to competitors 4. Check if you have an MCP/API/tool layer 5. Buy or recommend you without ever “visiting” your site like a person Everyone is going to have personal agents and business agents. This feels inevitable at this point. OpenClaw, Hermes, Claude Code, Codex, Google Spark. The tools are here. Which means there will be more agents on the internet than humans. So, where's the opportunity?? Go look at every SaaS tool you use. Notion. Slack. Jira. Google Analytics. Now ask: what is the version of this built purely for agents? Agent-native payments. Agent-native communication. Agent-native memory. Every category gets rebuilt. I clearly break down this shift and explain you everything on today's ep of The Startup Ideas Podcast (SIP) 🧃. Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. The founders who build for them now are going to look like the people who built websites in 1995. Might feel janky at the moment, but also obvious in hindsight. This is the next shift. Link over here: Watch

GREG ISENBERG

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

APPLE JUST SHOWED HOW TO RUN 10 AI AGENTS LOCALLY ON MAC - NO CLOUD, NO API KEYS, ZERO COSTS 00:10 Apple engineer says: "your data stays on your device, AI available anywhere at any time, zero usage costs" agent reads your code, checks GitHub, finds what needs attention and writes a report - all on your Mac, nothing goes to the internet 10 agents work simultaneously - one writes code, another tests, third fixes bugs - parallel with no queue built a full iPad app from scratch in 2 minutes, fixed its own mistakes and compiled without issues takes 5 minutes to set up - and you never pay again for a bot that runs 24/7

APPLE JUST SHOWED HOW TO RUN 10 AI AGENTS LOCALLY ON MAC - NO CLOUD, NO API KEYS, ZERO COSTS 00:10 Apple engineer says: "your data stays on your device, AI available anywhere at any time, zero usage costs" agent reads your code, checks GitHub, finds what needs attention and writes a report - all on your Mac, nothing goes to the internet 10 agents work simultaneously - one writes code, another tests, third fixes bugs - parallel with no queue built a full iPad app from scratch in 2 minutes, fixed its own mistakes and compiled without issues takes 5 minutes to set up - and you never pay again for a bot that runs 24/7

Noisy

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

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

Akshay 🚀

167,968 просмотров • 24 дней назад

Professor Sani Lawan Malumfashi Has this to say to all average Nigerians (sic: those outside the corridor of power where stealing happens): As a Nigerian, you should know that you are on your own. You're your own caretaker. Do not for once think that the govt cares. This simple if you consider that you literally provide everything for yourself: you drill your borehole if you want water. You provide yourself electricity by installing solsr systems or generators. If you want good health care, you go to private hospital and pay. If you want good education for your wards, you take them to private schools as well. Yet, you pay taxes. You literally benefit nothing from the govt. Instead, it is the govt that benefits from you. We fund the govt and the officials with our taxes. Therefore, under this hardship of life, as a Nigerian, this is what I suggest you do: 1. Be your own caretaker. 2. Anything that's not a necessity in life, let it slide. The time for excessive spending & enjoyment has been snatched away. This is a time of survival. If you are a fleet of cars, reduce them to one. The number of air conditioners in your house, reduce them or put them off, on your fan. Shawarma, chocolates, ice creams the kids consume, reduce them. Tap the kids on their shoulders. Tell them the reality of today. English breakfast might not be affordable anymore, return to the traditional ones you can afford. If you have beef for protein in your meal fine, if not, add some beans into the soup. It is another source of protein. (Sic: because egg isn't for average civil servants now). 3. Your health is the most important thing you have. Try as much as you can to avoid going to the hospital. Work hard for your health and pray for good health. The hospitals are in terrible state. You might go with headache and return home with an infection or bigger sickness. As a Nigerian, you're your president. You are your teacher. You are your governor. You're your local govt chairman. You're your security. You're all on your own. Forget anything and focus on your well-being. Own your own life. Again, avoid anything that will put you at loggerheads with the govt. Because if you do, the moment the power decides to kidnap you (arrest you); remember your family depend on you to feed. When you're away, you're only putting them in a more serious situation. Anyone who is stepping out of their homes should do so prepared. Prepare for the unimaginable. Anything can happen to you. Rely more on God. Present to Him your problems. (Sic: report every wicked leader to God. Only Him can deal with the situation).

Professor Sani Lawan Malumfashi Has this to say to all average Nigerians (sic: those outside the corridor of power where stealing happens): As a Nigerian, you should know that you are on your own. You're your own caretaker. Do not for once think that the govt cares. This simple if you consider that you literally provide everything for yourself: you drill your borehole if you want water. You provide yourself electricity by installing solsr systems or generators. If you want good health care, you go to private hospital and pay. If you want good education for your wards, you take them to private schools as well. Yet, you pay taxes. You literally benefit nothing from the govt. Instead, it is the govt that benefits from you. We fund the govt and the officials with our taxes. Therefore, under this hardship of life, as a Nigerian, this is what I suggest you do: 1. Be your own caretaker. 2. Anything that's not a necessity in life, let it slide. The time for excessive spending & enjoyment has been snatched away. This is a time of survival. If you are a fleet of cars, reduce them to one. The number of air conditioners in your house, reduce them or put them off, on your fan. Shawarma, chocolates, ice creams the kids consume, reduce them. Tap the kids on their shoulders. Tell them the reality of today. English breakfast might not be affordable anymore, return to the traditional ones you can afford. If you have beef for protein in your meal fine, if not, add some beans into the soup. It is another source of protein. (Sic: because egg isn't for average civil servants now). 3. Your health is the most important thing you have. Try as much as you can to avoid going to the hospital. Work hard for your health and pray for good health. The hospitals are in terrible state. You might go with headache and return home with an infection or bigger sickness. As a Nigerian, you're your president. You are your teacher. You are your governor. You're your local govt chairman. You're your security. You're all on your own. Forget anything and focus on your well-being. Own your own life. Again, avoid anything that will put you at loggerheads with the govt. Because if you do, the moment the power decides to kidnap you (arrest you); remember your family depend on you to feed. When you're away, you're only putting them in a more serious situation. Anyone who is stepping out of their homes should do so prepared. Prepare for the unimaginable. Anything can happen to you. Rely more on God. Present to Him your problems. (Sic: report every wicked leader to God. Only Him can deal with the situation).

𝐇𝐢𝐝𝐢𝐦𝐚, 𝐏𝐡.𝐃.

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

GPT 5.6 SOL IS HERE! How to run your personal + business life with GPT 5.6 Sol + Codex (full 49 min masterclass) We tested it for 30 days and the video it's the CLEAREST look at the FUTURE of work: Here's what's possible once you set it up: 1. Your inbox becomes cards every morning, each with a summary and a reply drafted in your own voice. Y 2. Your Slack, meeting notes, and company updates can turn into one daily feed with a clear next action. It learns what you care about over time and rewrites its own prompts to get sharper. 3. You can give your agent its own email address, so your other tools and even your team's Slack bot email it directly and it just handles things. 4. You can have it watch you do a task once and turn it into a skill it repeats forever. 5. You can set a long goal and walk away. You can have it run for 20 hours straight, and fine-tune your own models, something that was out of reach for non-engineers 12 months ago. How to start: Open Codex, give it access to your computer, and ask it to suggest things it could do for you based on how you already work. Full episode on The Startup Ideas Podcast (SIP) 🧃 (thanks Dan Shipper 📧 for sharing your entire workflow and review of GPT 5.6) Start with one boring task, get it working, and build from there. You'll learn exactly how to make something similar. GPT 5.6 Sol is impressive. Sol (according to openAI benchmarks) is the best coding model out right now. It set a new state of the art on Terminal-Bench 2.1 at 88.8%, and its "ultra mode" hits 91.9%, beating Claude Opus 4.8, Fable 5, and even Mythos 5 this masterclass is 100% free, like always. For more The Startup Ideas Podcast (SIP) 🧃 Watch

GPT 5.6 SOL IS HERE! How to run your personal + business life with GPT 5.6 Sol + Codex (full 49 min masterclass) We tested it for 30 days and the video it's the CLEAREST look at the FUTURE of work: Here's what's possible once you set it up: 1. Your inbox becomes cards every morning, each with a summary and a reply drafted in your own voice. Y 2. Your Slack, meeting notes, and company updates can turn into one daily feed with a clear next action. It learns what you care about over time and rewrites its own prompts to get sharper. 3. You can give your agent its own email address, so your other tools and even your team's Slack bot email it directly and it just handles things. 4. You can have it watch you do a task once and turn it into a skill it repeats forever. 5. You can set a long goal and walk away. You can have it run for 20 hours straight, and fine-tune your own models, something that was out of reach for non-engineers 12 months ago. How to start: Open Codex, give it access to your computer, and ask it to suggest things it could do for you based on how you already work. Full episode on The Startup Ideas Podcast (SIP) 🧃 (thanks Dan Shipper 📧 for sharing your entire workflow and review of GPT 5.6) Start with one boring task, get it working, and build from there. You'll learn exactly how to make something similar. GPT 5.6 Sol is impressive. Sol (according to openAI benchmarks) is the best coding model out right now. It set a new state of the art on Terminal-Bench 2.1 at 88.8%, and its "ultra mode" hits 91.9%, beating Claude Opus 4.8, Fable 5, and even Mythos 5 this masterclass is 100% free, like always. For more The Startup Ideas Podcast (SIP) 🧃 Watch

GREG ISENBERG

154,352 просмотров • 20 дней назад

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 просмотров • 21 дней назад

I built a Claude skill that turns Claude Code into your personal coding tutor. The core insight: Claude Opus 4.5 is already the best tutor in the world. Anthropic cooked with this model! It has incredible emotional intelligence and deep coding knowledge. What this skill does is just provide a harness—a way for Claude to agentically build the right context about YOU so it can personalize the tutoring experience in exactly the right way. Here's what makes it work: Learner profile from day one. The first time you use it, Claude interviews you. It asks about your programming background, your goal (where do you want this to take you?), and who you are as a person. This gets saved and informs every single tutorial it ever writes for you. From the very first interaction, everything is 100% personalized. Tutorials that use YOUR code. When you ask to learn something, Claude doesn't give you generic examples from some blog post. It finds examples in the actual codebase you're working in. This makes concepts stick in a way abstract examples never do. Quiz mode with spaced repetition. You can run "/quiz-me" and Claude will test you on concepts you've learned. It tracks your understanding score for each tutorial. Then it uses spaced repetition to prioritize the next quiz—concepts you're shaky on come back in 2 days, concepts you've mastered fade to 55+ day intervals. It literally builds retention into the learning process. One central knowledge base across all your projects. Whether you're joining a new company and want to understand their codebase, learning from an open source project, or leveling up on your own vibe-coded project—all your tutorials live in one place (~/coding-tutor-tutorials/). So your personal coding-tutor accompanies you across all your coding adventures. The whole thing is a feedback loop: learn → quiz → retain → learn more → quiz → retain. Your tutorials evolve, your knowledge compounds, and Claude gets better at teaching YOU specifically over time. To install it in Claude Code: • Run /plugin to open the plugin manager • Add marketplace nityeshaga/claude-code-essentials • Enable coding-tutor plugin Here's the Github: And here's 20-mins of me walking you through how to use this plugin and how it works 👇🏽 Let me know if you use it to teach yourself something cool!

Nityesh

64,540 просмотров • 7 месяцев назад

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

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

Marc Andreessen explains the Onion Theory of Risk and the best way to raise capital for your business: "You can think about a startup on day one as having every conceivable kind of risk." "The way to think about it is—you're peeling away risk as you go and by achieving milestones. And then as you achieve milestones, you're both making progress in your business, and you're justifying raising more capital." Marc Andreessen 🇺🇸 on Y Combinator

Marc Andreessen explains the Onion Theory of Risk and the best way to raise capital for your business: "You can think about a startup on day one as having every conceivable kind of risk." "The way to think about it is—you're peeling away risk as you go and by achieving milestones. And then as you achieve milestones, you're both making progress in your business, and you're justifying raising more capital." Marc Andreessen 🇺🇸 on Y Combinator

a16z

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