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

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

На главную

Quick demo of how I use session to session messaging in Claude Code + Ghostty (Save this and try it in your own workflows) 1- I always start with a regular session and a panel running claude agents 2- The first session becomes the orchestrator. It creates the initial...

dani_avila7's profile picture

Daniel San

33,613 subscribers

47,175 просмотров • 6 дней назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console
0:40

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console

Daniel San

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

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.
0:34

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Daniel San

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

Started working on "Claude HUD" A Claude Code plugin that visualizes: · context remaining in the session · what tools are executing · which subagents are running · claude's to-do list progress If there's enough interest, I'll polish it up and open-source it!
0:20

Started working on "Claude HUD" A Claude Code plugin that visualizes: · context remaining in the session · what tools are executing · which subagents are running · claude's to-do list progress If there's enough interest, I'll polish it up and open-source it!

Jarrod Watts

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

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:
0:20

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:

Yusuf

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

This is incredibly useful for those using Claude Code! I have two computers, and sharing your Claude Code sessions is almost impossible without this. I often start working on something on my desktop, and then want to continue working on the same session (same context, conversation, etc.) on my laptop. The folks at Depot built an integration that solves this problem: You can now start a session on one computer and resume it anywhere else in the world! You can even share it with other team members so they can also contribute to it. Here is an article showing you how the Depot team uses this feature with Claude Code to automate their GitHub Actions Runner updates: Thanks to the team for the effort in building this integration and collaborating with me on this post.
4:29

This is incredibly useful for those using Claude Code! I have two computers, and sharing your Claude Code sessions is almost impossible without this. I often start working on something on my desktop, and then want to continue working on the same session (same context, conversation, etc.) on my laptop. The folks at Depot built an integration that solves this problem: You can now start a session on one computer and resume it anywhere else in the world! You can even share it with other team members so they can also contribute to it. Here is an article showing you how the Depot team uses this feature with Claude Code to automate their GitHub Actions Runner updates: Thanks to the team for the effort in building this integration and collaborating with me on this post.

Santiago

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

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 просмотров • 1 месяц назад

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,640 просмотров • 2 месяцев назад

Most people use Claude Code like a chatbot. That is the mistake. The real power is not in better prompts. It is in controlling the session. /init gives the project memory. /memory keeps the rules alive. /clear removes old context. /compact saves the important parts. /context shows where the tokens go. /rewind fixes bad turns. /plan stops blind edits. /model matches the brain to the task. Claude Code gets 10x better when you stop letting the conversation run itself. Memory. Context. Boundaries. Rollback. Planning. That is the system. Stop asking Claude Code to “just do it”. Teach it what to remember, what to forget, and when to stop. Bookmark this before your next session turns into 40 messages of context debt.
0:33

Most people use Claude Code like a chatbot. That is the mistake. The real power is not in better prompts. It is in controlling the session. /init gives the project memory. /memory keeps the rules alive. /clear removes old context. /compact saves the important parts. /context shows where the tokens go. /rewind fixes bad turns. /plan stops blind edits. /model matches the brain to the task. Claude Code gets 10x better when you stop letting the conversation run itself. Memory. Context. Boundaries. Rollback. Planning. That is the system. Stop asking Claude Code to “just do it”. Teach it what to remember, what to forget, and when to stop. Bookmark this before your next session turns into 40 messages of context debt.

Fluixo

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

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.
1:35

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.

Prajwal Tomar

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

Hermes Agent Desktop App is getting some major UI upgrades! In this short video, I demo how to drag different session context into your current project, as well as how to use multisession tabs and adjust the session panes to get the perfect layout. If you're always working on multiple projects like me, this really makes it easy to keep track of how each agent is working. Looking forward to seeing more upgrades in the Desktop App!
2:48

Hermes Agent Desktop App is getting some major UI upgrades! In this short video, I demo how to drag different session context into your current project, as well as how to use multisession tabs and adjust the session panes to get the perfect layout. If you're always working on multiple projects like me, this really makes it easy to keep track of how each agent is working. Looking forward to seeing more upgrades in the Desktop App!

tonbi

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

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.
1:11

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.

Riley Brown

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

A 22-YEAR-OLD FROM BEIJING BUILT A SECOND BRAIN WITH CLAUDE, MAKES $14,000/MONTH AND HIS AI REMEMBERS EVERY DECISION HE'S EVER MADE Most people open ChatGPT, ask a question and start from zero next session, re-explaining the same context every single time and losing 15–40 minutes per session doing it. He built infrastructure where Claude reads, writes and connects everything in Obsidian automatically so it never resets and compounds with every conversation. This morning he needed a client strategy from 3 months ago. Claude pulled it up instantly and drafted a full email reply in under 20 minutes using context it had been building for months across 6,000+ sessions. Every session adds to the last one and the system now saves him 2–3 hours every single day - 30–90 minutes from automated morning briefing alone, before he even opens his laptop. repo: The repo is free. The advantage it creates is not.
1:14

A 22-YEAR-OLD FROM BEIJING BUILT A SECOND BRAIN WITH CLAUDE, MAKES $14,000/MONTH AND HIS AI REMEMBERS EVERY DECISION HE'S EVER MADE Most people open ChatGPT, ask a question and start from zero next session, re-explaining the same context every single time and losing 15–40 minutes per session doing it. He built infrastructure where Claude reads, writes and connects everything in Obsidian automatically so it never resets and compounds with every conversation. This morning he needed a client strategy from 3 months ago. Claude pulled it up instantly and drafted a full email reply in under 20 minutes using context it had been building for months across 6,000+ sessions. Every session adds to the last one and the system now saves him 2–3 hours every single day - 30–90 minutes from automated morning briefing alone, before he even opens his laptop. repo: The repo is free. The advantage it creates is not.

Noisy

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

#WATCH | Delhi | On the Winter Session of the Parliament, Congress MP Jairam Ramesh says, "I was very surprised that this winter session was called so late. It's usually convened between November 20th and 23rd, and 24th December, lasting three to four weeks. I was surprised that this time the session will begin on December 1st and last only 15 days... I don't understand what the government is running away from. Is the session being shortened because of Delhi's pollution? Is there no legislation or bill? Is there no topic for debate?... They just want to end it as a formality as quickly as possible. This is the first time we've seen this... Yes, sessions are shortened before elections, so does this indicate that Lok Sabha elections are coming?..."
3:22

#WATCH | Delhi | On the Winter Session of the Parliament, Congress MP Jairam Ramesh says, "I was very surprised that this winter session was called so late. It's usually convened between November 20th and 23rd, and 24th December, lasting three to four weeks. I was surprised that this time the session will begin on December 1st and last only 15 days... I don't understand what the government is running away from. Is the session being shortened because of Delhi's pollution? Is there no legislation or bill? Is there no topic for debate?... They just want to end it as a formality as quickly as possible. This is the first time we've seen this... Yes, sessions are shortened before elections, so does this indicate that Lok Sabha elections are coming?..."

ANI

53,623 просмотров • 9 месяцев назад

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.
0:52

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.

Yam Peleg

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

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.
0:24

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.

CyrilXBT

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

I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.
5:57

I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.

Vinny

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

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!
0:31

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!

am.will

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

We started Learning how to build AI agents & tools from scratch, on Nov 2, In the first two sessions we learned from the very basics: - One API call to the claude endpoint - How to use a tool - How to use that api with tool to solve business problems and automations - How to build a simple chat - How to use tools in that chat - How to use that chat logic to build ai agents and subagents / tools - Blog automation - Presentation builder - Text only AI, then image generation. Now we are gonna be doing the third and last online session, on Sunday, Nov 30th! Where we will learn how a complex ai tool like NotebookLM works! So obviously like any other sane person would do, i started cloning and rebuilding NoteebookLM from scratch all over again yesterday, and in a couple of more days the whole product will be ready! Which will be the focus of our last session, where we will learn: AI chat, RAG, Images, Videos, Realtime Transcription ( streaming ), Memories, Project Context, Subagents( yes a bunch of them ), Deep Research, LLM powered Websearch and much more! Also you would get the notes, access to the codebase of LocalLM (NotebookLM clone for personal use ) Link to the session - ( Free for all ) ( if you have not attended the first & second session or gone through the recordings, it is highly advisable to go through them to get the most out of this session 3, details to acces the recordings in the thread! ) GrowthX
1:06

We started Learning how to build AI agents & tools from scratch, on Nov 2, In the first two sessions we learned from the very basics: - One API call to the claude endpoint - How to use a tool - How to use that api with tool to solve business problems and automations - How to build a simple chat - How to use tools in that chat - How to use that chat logic to build ai agents and subagents / tools - Blog automation - Presentation builder - Text only AI, then image generation. Now we are gonna be doing the third and last online session, on Sunday, Nov 30th! Where we will learn how a complex ai tool like NotebookLM works! So obviously like any other sane person would do, i started cloning and rebuilding NoteebookLM from scratch all over again yesterday, and in a couple of more days the whole product will be ready! Which will be the focus of our last session, where we will learn: AI chat, RAG, Images, Videos, Realtime Transcription ( streaming ), Memories, Project Context, Subagents( yes a bunch of them ), Deep Research, LLM powered Websearch and much more! Also you would get the notes, access to the codebase of LocalLM (NotebookLM clone for personal use ) Link to the session - ( Free for all ) ( if you have not attended the first & second session or gone through the recordings, it is highly advisable to go through them to get the most out of this session 3, details to acces the recordings in the thread! ) GrowthX

Neel Seth

17,615 просмотров • 9 месяцев назад

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.
2:29

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Nikos

14,770 просмотров • 4 дней назад

Claude Code + Opus 4 is the best agentic coding tool in the world and it’s not close. It’s a: - masterful full-stack dev - with great product sense - that’s a delight to work with - and easy to use If you’re not using it you are behind. Watch for a 72min build session & tips.
1:12:13

Claude Code + Opus 4 is the best agentic coding tool in the world and it’s not close. It’s a: - masterful full-stack dev - with great product sense - that’s a delight to work with - and easy to use If you’re not using it you are behind. Watch for a 72min build session & tips.

Mckay Wrigley

319,940 просмотров • 1 год назад