So, in order to move forward in AI's assistant roadmap, here is my insight about the video. A MUST for newbies. I really loved how simple the demo shows how the system works. Moving claude.md to agents.md is a smart move, and great for my case: I use Cline and Antigravity combined with Claude Code on same folders. Great work @iscalelabs!

Building a multi-agent MCP product with a dev team. We're debating architecture at the routing/state layer. Our current design uses layered index.md files — ICM-style. The top-level index routes query type, agent-specific indexes define stage contracts, Layer 3 holds the stable reference files, Layer 4 is the per-run working content. Clean separation, low token overhead, human-readable at every step. The question on the table: LangGraph vs. staying with the index.md architecture. The argument for LangGraph is state management — persisting data between agents mid-conversation without passing full JSON payloads downstream. The argument against is that we may not have that problem yet, and adding a framework dependency before the problem is real creates overhead without payoff. Jake's paper draws a hard line on where ICM does and doesn't work. Complex automated branching mid-pipeline is one of the failure modes flaged. Is that the trigger? Meaning: if agents need to share state mid-run rather than just receive the previous agent's output, is that the point where a framework like LangGraph earns its weight over a file-based architecture? Or is there a hybrid approach — ICM for context scoping, LangGraph only for the state graph layer — worth considering before we commit either direction?

"Hello everyone! 👋 I'm Javier, and my coding knowledge consists of HTML+CSS, and basic JS+PHP. My real thing is storytelling. I started using Claude Code in VSC with an academic project I was doing by hand: a historical archive manager (backend). For that project, I needed documentation, so I created a new project that crawls sources and indexes them, extracting the facts. The succession of needs to resolve generated several projects (one per day), all interrelated: distillation of pictorial styles, image generation, video editing (integrated via Python with DaVinci Resolve), audio generation... All of them operational, with a minimum viable feature test. During the process, Claude encountered execution frictions, many thanks to VSC's LINT extensions (Docker stuff, system paths, nomenclature like python vs. py...) and reasoning issues (overlooking instructions or paths), so I started (well, Claude did) to establish a system that logged these frictions to avoid them in the future. My approach was to keep everything on track as much as possible with code, which is deterministic: hooks (preferably pre-tool), access doors to edit Claude's memory files, etc. Everything documented both in the repo and in the GitHub commits. At this point, I needed something to organize the chaos of ideas I had for each project, to monitor the repo ecosystem (health, status), and to log useful info like repos, documentation, etc. So I created the 'Organization' repo, to rule them all, with an update propagation system. In theory, it was perfect: absolutely everything was logged. The problem is that almost everything went into a drawer to be forgotten. Too much context in Claude's reasoning, poorly mapped. I discovered Karpathy and Obsidian, and started moving the useful info from 'Organization' to a new version, creating a vault with more segmented info, and keeping Claude on track when consulting it (using Kepano's skills: https://github.com/kepano/obsidian-skills/tree/main).

We officially launched the new Clief Notes Agent, and I wanted to check in with you. Have you had a chance to talk to it yet? If you have, I’d love to hear how it went. And if you’ve run into any questions, confusion, or issues getting started, drop them in the comments below. The goal is to make it easier to find what you need, know what to focus on next, and get more out of everything already inside Clief Notes. So, How’s your experience been so far?

Saw one of the software engineers on the agent team post this today. Thought it was nice to see them finally seeing the light