Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

just shipped thred!! context that carries your work forward. Claude → Codex → Cursor → whatever comes next. thred gives every agent one shared memory for decisions, revisions, evidence, and unfinished work — so the next agent starts where the last one stopped. built on MCP. powered by temporal...

nick_realm_01's profile picture

nikhil · sys/quests

1,413 subscribers

15,716 görüntüleme • 5 gün önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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 görüntüleme • 26 gün önce

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 görüntüleme • 24 gün önce

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.
0:34

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.

SIBYL

83,401 görüntüleme • 2 ay önce

Context is power. Context shared is power multiplied. Every AI agent today builds context, then loses it. Work doesn't compound. OriginTrail is built differently: three memory layers, one shared graph, provenance baked in. DKG v10 now integrates with Hermes of Nous Research, OpenClaw🦞, Claude (Code & Desktop), Cursor, Codex by OpenAI, Windsurf (retired), VSCode + GitHub Copilot Chat, and Cline.
0:22

Context is power. Context shared is power multiplied. Every AI agent today builds context, then loses it. Work doesn't compound. OriginTrail is built differently: three memory layers, one shared graph, provenance baked in. DKG v10 now integrates with Hermes of Nous Research, OpenClaw🦞, Claude (Code & Desktop), Cursor, Codex by OpenAI, Windsurf (retired), VSCode + GitHub Copilot Chat, and Cline.

OriginTrail

1,723,329 görüntüleme • 3 ay önce

CNVS went viral for the wrong reason... the Ui is beautiful, but the CNVS cross agent memory system is world class. ultra simple & based on actual research. talking between multiple agents, codex, cursor, claude, starts to feel like one brain that actually understands your project. CNVS memory is just files agents read on demand and on Mem0's own benchmark, that approach beats Mem0 (74% vs 68.5%). Append-only JSONL every agent reads & writes directly. No DB. No embeddings. No service to be down. memory is scoped per canvas (project) increasing the specificity of the context. NO BLOAT, just clean and on demand. the least complex solution always works best.
0:33

CNVS went viral for the wrong reason... the Ui is beautiful, but the CNVS cross agent memory system is world class. ultra simple & based on actual research. talking between multiple agents, codex, cursor, claude, starts to feel like one brain that actually understands your project. CNVS memory is just files agents read on demand and on Mem0's own benchmark, that approach beats Mem0 (74% vs 68.5%). Append-only JSONL every agent reads & writes directly. No DB. No embeddings. No service to be down. memory is scoped per canvas (project) increasing the specificity of the context. NO BLOAT, just clean and on demand. the least complex solution always works best.

Max Blade

21,522 görüntüleme • 2 ay önce

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, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access
2:15

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, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 görüntüleme • 11 gün önce

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome
0:50

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome

Chetaslua

48,810 görüntüleme • 1 ay önce

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

160,148 görüntüleme • 5 ay önce

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 görüntüleme • 1 ay önce

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 görüntüleme • 24 gün önce

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 görüntüleme • 2 ay önce

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,211 görüntüleme • 3 ay önce

THIS GUY BUILT A 24/7 AI COMPANY WITH 7 AGENTS THAT CHECKS 48 TIMES A DAY, PICKS ITS OWN TASKS AND KEEPS WORKING WHILE HE SLEEPS 00:05 the map shows agents moving between the marketplace, research lab and command center, with each one handling a different job inside the same shared system the setup runs on 4 core layers: automatic triggers, shared memory, connected tools and an isolated verifier that checks every result before the next step starts each cycle reads the last 10 log entries, updates open tasks, saves new signals and passes the context forward, so the next agent never starts from zero one agent researches, two execute, another monitors outcomes and a read-only checker reviews the work independently, allowing several workflows to run in parallel without breaking the system bookmark this before everyone stops prompting one agent at a time and starts building AI teams that work, learn and improve around the clock
0:31

THIS GUY BUILT A 24/7 AI COMPANY WITH 7 AGENTS THAT CHECKS 48 TIMES A DAY, PICKS ITS OWN TASKS AND KEEPS WORKING WHILE HE SLEEPS 00:05 the map shows agents moving between the marketplace, research lab and command center, with each one handling a different job inside the same shared system the setup runs on 4 core layers: automatic triggers, shared memory, connected tools and an isolated verifier that checks every result before the next step starts each cycle reads the last 10 log entries, updates open tasks, saves new signals and passes the context forward, so the next agent never starts from zero one agent researches, two execute, another monitors outcomes and a read-only checker reviews the work independently, allowing several workflows to run in parallel without breaking the system bookmark this before everyone stops prompting one agent at a time and starts building AI teams that work, learn and improve around the clock

Gipp 🦅

19,071 görüntüleme • 1 ay önce

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph
0:24

Cross-context Personal Knowledge Base with Social Graph🧠 Introducing Cross-context Personal Knowledge Base with Social Graph. Your Memory, Across Every Conversation Most AI forgets you the moment a chat ends. Teamily's Personal Knowledge Base remembers — across every group, every agent, and every context. Powered by your social graph, it connects the dots between your work, relationships, and ideas, so your AI always knows who you are, what you care about, and what happened before. No setup. No tagging. Just intelligence that grows with you. 🙌Try the prompt today: “visualize my knowledge base with social graph” #teamily #AI #Agent #KnowledgeBase #Social #SocialGraph

Teamily AI

13,287 görüntüleme • 3 ay önce

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇
2:24

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

Taranjeet

472,126 görüntüleme • 1 yıl önce

MICROSOFT QUIETLY BUILT ONE MEMORY MODULE THAT PLUGS INTO ANY AI AGENT AND CUTS ITS CONTEXT BY UP TO 100X no retraining. no task-specific redesign. you just plug it in Microsoft's insight: agents don't need to remember what happened. they need the knowledge pulled from it - the facts and the reusable skills, not the raw logs so PlugMem stops storing history. it compiles experience into a knowledge graph, then feeds the agent only what matters the result: > up to 1-2 orders of magnitude fewer tokens > highest decision-utility per token of any system tested > one unchanged module beats task-specific memory on chat QA, multi-hop search, and web agents more memory was never the answer. better memory is - and Microsoft just shipped it as a plug-in bookmark this. the agents that win won't remember more, they'll remember smarter.
0:42

MICROSOFT QUIETLY BUILT ONE MEMORY MODULE THAT PLUGS INTO ANY AI AGENT AND CUTS ITS CONTEXT BY UP TO 100X no retraining. no task-specific redesign. you just plug it in Microsoft's insight: agents don't need to remember what happened. they need the knowledge pulled from it - the facts and the reusable skills, not the raw logs so PlugMem stops storing history. it compiles experience into a knowledge graph, then feeds the agent only what matters the result: > up to 1-2 orders of magnitude fewer tokens > highest decision-utility per token of any system tested > one unchanged module beats task-specific memory on chat QA, multi-hop search, and web agents more memory was never the answer. better memory is - and Microsoft just shipped it as a plug-in bookmark this. the agents that win won't remember more, they'll remember smarter.

NO1ennn

225,884 görüntüleme • 18 gün önce

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.
1:34

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.

Jarvix

1,686,504 görüntüleme • 11 gün önce

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.
10:19

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 görüntüleme • 1 ay önce

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 görüntüleme • 1 ay önce

Martin Keen from IBM just explained the one thing separating "chatbot users" from $300K AI architects > most people use Claude Opus 4.8 as a temporary tool -> the pros build it a permanent memory it's called the CoALA framework. the 4 layers your agent actually needs: > Working Memory - the context window. fast but resets every session. this is the RAM, not the brain > Semantic Memory - your knowledge base. CLAUDE.md, rules, facts the agent never forgets regardless of session > Procedural Memory - skills. workflows and instructions that load only when a specific task begins > Episodic Memory - past lessons. the agent remembers every bug it fixed yesterday so it doesn't repeat it today if your agent doesn't have all four, it's a fancy autocomplete the 2026 job market isn't looking for prompt engineers > it's looking for people who can build AI brains - and the ones doing it now aren't waiting for job postings save this or watch someone else use it to get your next raise 👇
10:04

Martin Keen from IBM just explained the one thing separating "chatbot users" from $300K AI architects > most people use Claude Opus 4.8 as a temporary tool -> the pros build it a permanent memory it's called the CoALA framework. the 4 layers your agent actually needs: > Working Memory - the context window. fast but resets every session. this is the RAM, not the brain > Semantic Memory - your knowledge base. CLAUDE.md, rules, facts the agent never forgets regardless of session > Procedural Memory - skills. workflows and instructions that load only when a specific task begins > Episodic Memory - past lessons. the agent remembers every bug it fixed yesterday so it doesn't repeat it today if your agent doesn't have all four, it's a fancy autocomplete the 2026 job market isn't looking for prompt engineers > it's looking for people who can build AI brains - and the ones doing it now aren't waiting for job postings save this or watch someone else use it to get your next raise 👇

Mr. Buzzoni

10,435 görüntüleme • 2 ay önce