Claude can now prompt its own SESSIONS. I built the boss.
Claude now has the ability to interact with multiple sessions, allowing a streamlined orchestration of tasks through an agent called Larry. This integration can simplify task management and enhance productivity by enabling a single main session to oversee various sub-sessions or tasks.
Summary
The transcript discusses the new capabilities of Claude, an AI system that can now communicate across multiple running sessions. The speaker introduces an orchestrator agent called Larry, designed to manage and delegate tasks efficiently. By linking specific tasks with Claude session IDs, the system aims to maintain an organized workflow within a folder structure, facilitating the tracking of completed, in-progress, and canceled tasks. The speaker emphasizes the need for clear organization to avoid task overload, and discusses the potential to create a ‘deliverables management system.’ As Claude interacts with different sessions, it demonstrates the capacity to autonomously handle background tasks and communicate updates back to the main session, thereby reducing the need for constant oversight from the user. The ultimate goal is to create a structured system that effectively integrates various projects and ensures that deliverables align with specific objectives, while also enabling improved visibility and efficiency in the workflow.
Key Insights
- Claude's capability to speak to different sessions allows it to not only look up content but also inject prompts into these running sessions.
- The key advantage of using the orchestrator agent Larry is to allow a single main session to manage multiple tasks without needing to reopen individual sessions.
- By attaching Claude session IDs to tasks, it's possible to maintain full context throughout the workflow, allowing the orchestrator to effectively delegate work.
- The framework features commands that Claude can execute, which are snippets that can be triggered to streamline task management within the folder system.
- The speaker argues for a structure that connects deliverables with corresponding projects to ensure that tasks are always aligned with broader goals, avoiding random work that does not contribute to objectives.
Topics
Transcript
[0:00] I don't know if you heard it, but Claude is now able to talk to different sessions. So, if you have several sessions open and you open a new one, it can actually talk to the other sessions. Not only look up the content, but actually inject prompts into these running sessions. And that's really powerful. And for those who don't know, if you use claude, all these sessions get stored locally on your device. they have all their own ID. That's when you [0:31] say resume session, you were able to find these different sessions based on the IDs. And I used this already in the past to let AI look up any context from previous sessions. Now,…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
Your knowledge should outlive every AI tool you use.
The speaker clarifies the distinction between the ICOR methodology (a tool-agnostic productivity framework) and its implementations like the ICOR for Life scaffold and myPKA AI team, emphasizing that users can adopt the core principles in any tool they prefer. They announce plans to restructure their membership platform by separating these components to reduce confusion and help users understand they're not locked into specific tools or systems.
Claude alone took 3 minutes. With Jev, 21 seconds.
A demonstration comparing AI slide deck creation using Claude alone versus Claude integrated with Jev, showing that the hybrid approach completed the task in 21 seconds for $8 with proper formatting, while Claude-only took 3+ minutes and cost $49 with poor formatting.
Why I stick to Claude for work (most of the time)
The creator demonstrates why Claude is their preferred AI for work by comparing it with ChatGPT across multiple tests, showing that Claude better adheres to custom instructions and agentic workflows defined in local folder structures. The key advantage lies in using organized, LLM-agnostic folder systems with agents.md files rather than relying on auto-memory features.
You are using the wrong Claude for work! (Here is proof)
A video demonstrating that Claude Code is significantly more powerful than Claude Cowork for professional knowledge workers, showing how Claude Code better understands folder context, enforces safety rules, orchestrates sub-agents with different models, and creates persistent file outputs rather than temporary artifacts.
Obsidian is the tool I teach in. Keep the one you have.
The creator addresses criticism about switching to Obsidian after previously promoting other tools, clarifying that his tool-agnostic ICOR methodology remains unchanged and that Obsidian is simply an interface layer for his folder-based system. He emphasizes that the underlying folder structure, AI automation, and productivity principles are identical regardless of which tool visualizes the content.