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

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

На главную

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects,...

DeRonin_'s profile picture

Ronin

110,794 subscribers

14,481 просмотров • 4 дней назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:
1:13

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:

Priyank Ahuja

13,228 просмотров • 18 дней назад

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓
3:29

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

Charly Wargnier

203,456 просмотров • 17 дней назад

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call
1:07

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call

Shadow Nick

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

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.
0:30

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

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

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.
0:22

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

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

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵
0:34

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

Hasan

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

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.
8:17

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

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

Buzz is Slack where the agents are teammates instead of integrations. Here's what that unlocks: Agents: - The ones you start with are just defaults - Edit them, add your own, write their instructions like a system prompt Swappable Harness: - This is the killer feature - Swap Claude Code, Codex, Goose under the same agent Context: - Every chat you've had with that agent carries over to the new harness - Global skills and skill files come too Think: Slack = the shape Agents = the teammates Harness = the engine you can change without losing anything "I get model fatigue" is a real thing. Buzz sits one layer above it.
3:58

Buzz is Slack where the agents are teammates instead of integrations. Here's what that unlocks: Agents: - The ones you start with are just defaults - Edit them, add your own, write their instructions like a system prompt Swappable Harness: - This is the killer feature - Swap Claude Code, Codex, Goose under the same agent Context: - Every chat you've had with that agent carries over to the new harness - Global skills and skill files come too Think: Slack = the shape Agents = the teammates Harness = the engine you can change without losing anything "I get model fatigue" is a real thing. Buzz sits one layer above it.

The Startup Ideas Podcast (SIP) 🧃

43,416 просмотров • 19 дней назад

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

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

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

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

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
38:43

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

551,065 просмотров • 19 дней назад

Google just dropped a free 1-hour course On building complete agent systems from scratch: 07:02 - Build your first AI agent 13:34 - Give every agent a specialized skill 23:08 - Engineer the right context 32:56 - Connect agents into graphs 54:11 - Run 1,000 agents in autonomous loops One agent saves you an hour A thousand agents replace the team you cannot afford to hire Most people are still learning how to prompt one chatbot Google is already teaching how to build entire agent systems Agent → Skills → Context → Graphs → Loops Single agents are the old workflow Agent swarms are the new one This free 1-hour course is worth more than most paid agent engineering programs Bookmark it before everyone starts building the same thing Then build your first agent with the guide below
1:05:19

Google just dropped a free 1-hour course On building complete agent systems from scratch: 07:02 - Build your first AI agent 13:34 - Give every agent a specialized skill 23:08 - Engineer the right context 32:56 - Connect agents into graphs 54:11 - Run 1,000 agents in autonomous loops One agent saves you an hour A thousand agents replace the team you cannot afford to hire Most people are still learning how to prompt one chatbot Google is already teaching how to build entire agent systems Agent → Skills → Context → Graphs → Loops Single agents are the old workflow Agent swarms are the new one This free 1-hour course is worth more than most paid agent engineering programs Bookmark it before everyone starts building the same thing Then build your first agent with the guide below

rari

27,639 просмотров • 15 дней назад

Anthropic's Claude team just showed how to give your AI agents real memory in under 18 minutes. Free. From the people who built it. You've been building agents that forget everything between sessions. This fixes that tonight. One person + 10 agents with memory + dreaming = a team that runs 24/7, learns from every task, and improves itself overnight. Worth more than any $500 AI agent course. Bookmark it. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
24:22

Anthropic's Claude team just showed how to give your AI agents real memory in under 18 minutes. Free. From the people who built it. You've been building agents that forget everything between sessions. This fixes that tonight. One person + 10 agents with memory + dreaming = a team that runs 24/7, learns from every task, and improves itself overnight. Worth more than any $500 AI agent course. Bookmark it. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

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

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.
16:29

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.

Yarchi

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

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.
34:07

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

West Lord

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

We’ve been in private beta with a human + AI workspace similar to Buzz, with a few really important differences: (We previously built a company backed by Slack that sold to Atlassian, so we've been thinking about this problem for a while) - Agents reply by default unless you specifically flip to “team chat.” This feels 10x better than having to @ mention the agent every time. - It’s all in the cloud, with shared compute spread across a set of VMs. Way smoother onboarding, and yes, you can still connect your claude/codex subscriptions - You don’t create an army of agents. Number of agents is a vanity metric. Instead, you create shared computers, each one is a “space” where you define shared memory, connectors, skills, automations, etc. The Type agent pulls the appropriate context from the space where you have the conversation. - You can connect it to Slack to make it easy for your team to adopt and slowly move over rather than having to rip out Slack day 1. We’re working with a couple dozen forward thinking companies, who have told us “the whole team loves type”, “it’s the most used app on my computer”, and “type gives you superpowers” Here's a demo of how it works. Reply if you want to test it out!
5:09

We’ve been in private beta with a human + AI workspace similar to Buzz, with a few really important differences: (We previously built a company backed by Slack that sold to Atlassian, so we've been thinking about this problem for a while) - Agents reply by default unless you specifically flip to “team chat.” This feels 10x better than having to @ mention the agent every time. - It’s all in the cloud, with shared compute spread across a set of VMs. Way smoother onboarding, and yes, you can still connect your claude/codex subscriptions - You don’t create an army of agents. Number of agents is a vanity metric. Instead, you create shared computers, each one is a “space” where you define shared memory, connectors, skills, automations, etc. The Type agent pulls the appropriate context from the space where you have the conversation. - You can connect it to Slack to make it easy for your team to adopt and slowly move over rather than having to rip out Slack day 1. We’re working with a couple dozen forward thinking companies, who have told us “the whole team loves type”, “it’s the most used app on my computer”, and “type gives you superpowers” Here's a demo of how it works. Reply if you want to test it out!

Fletcher Richman

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

I've built a team of AI agents to run my business. Here's the exact order I follow: Step 1: Pick a role (executive assistant, head of marketing, etc.) Step 2: Open Claude Code and interview your way into context files "Ask me questions to build this out" Step 3: Build skills through daily use - Daily briefs - Meeting prep - Custom workflows Step 4: Get it all working reliably first. Step 5: THEN migrate to autonomous harnesses like OpenClaw. Most people jump straight to Step 5. That's why their agents break. Start with one agent. One role. Get it right. Then scale
3:19

I've built a team of AI agents to run my business. Here's the exact order I follow: Step 1: Pick a role (executive assistant, head of marketing, etc.) Step 2: Open Claude Code and interview your way into context files "Ask me questions to build this out" Step 3: Build skills through daily use - Daily briefs - Meeting prep - Custom workflows Step 4: Get it all working reliably first. Step 5: THEN migrate to autonomous harnesses like OpenClaw. Most people jump straight to Step 5. That's why their agents break. Start with one agent. One role. Get it right. Then scale

The Startup Ideas Podcast (SIP) 🧃

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

Personal AGI is 3-6 months away. I'm already living in it. Here's my Obsidian setup: - Obsidian vault built since November 2025 - Markdowns about every person, project, and task - Limitless mic pulling daily transcripts straight in - Agents that read all of it before every task Obsidian is: - A second brain for you - A first brain for your agents My agents have full context before every task. That's the whole game.
1:55

Personal AGI is 3-6 months away. I'm already living in it. Here's my Obsidian setup: - Obsidian vault built since November 2025 - Markdowns about every person, project, and task - Limitless mic pulling daily transcripts straight in - Agents that read all of it before every task Obsidian is: - A second brain for you - A first brain for your agents My agents have full context before every task. That's the whole game.

The Startup Ideas Podcast (SIP) 🧃

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

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain
1:50

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain

Muskan Jain

39,732 просмотров • 17 дней назад

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?
2:54

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?

Milind S

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