Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

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:show more

Yusuf

1,425 subscribers

220,215 Aufrufe • vor 2 Monaten •via X (Twitter)

Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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 context, then distributes the work across other sessions using forks 3- Each fork starts with that context + a prompt telling it what to work on 4- I rename each session with ctrl + r to keep things organized and make it easy to message them from the main session 5- Using @ I send messages to the sessions that are running and ask them to report their task status back, so the main session always knows what everyone is working on This way, I only need 2 or 3 panels open and can switch between tasks as needed The days of opening endless terminal panels and running Claude Code 100 times just to look productive are over! What we need now is ORCHESTATION one main session coordinating everything through session messaging + Agent View And the key is context, build it in the main session first, then fork from there That’s what makes the entire workflow click

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 context, then distributes the work across other sessions using forks 3- Each fork starts with that context + a prompt telling it what to work on 4- I rename each session with ctrl + r to keep things organized and make it easy to message them from the main session 5- Using @ I send messages to the sessions that are running and ask them to report their task status back, so the main session always knows what everyone is working on This way, I only need 2 or 3 panels open and can switch between tasks as needed The days of opening endless terminal panels and running Claude Code 100 times just to look productive are over! What we need now is ORCHESTATION one main session coordinating everything through session messaging + Agent View And the key is context, build it in the main session first, then fork from there That’s what makes the entire workflow click

Daniel San

47,525 Aufrufe • vor 11 Tagen

Claude Tag has completely changed the way I do work for the last 4 months. Except… it's not Claude Tag. Anthropic only announced that a few hours ago, and I don't even have access yet. But I did build a version of it for myself which I've been using for months now. Here's how. 4 months ago, inspired by the success of OpenClaw, I wondered what would happen if I let Claude Code on its own computer 24x7. So I built a simple harness that allowed me to turn any Mac into an AI employee with Claude Code headless mode (-p). Today, I manage 3 such AI employees. It started with Luo Ji — my and my brother Piyush Agarwal's AI co-founder, running in our personal Slack. Luo does real work for us. We've been writing a 100% of the code for 3 products on Slack with Luo now. It manages our emails and gives us a little brief each day with things we need to take action on. And so much more. And it's not just the two of us. On the consulting team at Every 🪨, we run Claudie and for the editorial team, Andy. Same architecture, same Slack, months of real work. They help the teams with work related to project management, chief-of-staff work, data hygiene, building decks, writing first drafts, even browsing X on their own account for AI updates. So it's mindblowing to see that Anthropic landed on the exact same architecture I did. Claude Tag is an AI employee that lives in your Slack workspace and does work autonomously. Anthropic says they've been running it internally for the better part of this year — opening PRs, doing real work. And so have I. So has my whole team. The architectural decisions Anthropic baked into Claude Tag are the ones we arrived at too: - Built on Claude Code - Uses its own accounts - A separate employee per team - Slack as the interface This is the future of work, and I've been living it for months. I've shifted all of my workflows — code, PRs, even the non-technical stuff — out of Claude Code and the Claude app and into Slack. I've had entire weeks where I never opened Claude Code on my laptop. Here's a video walkthrough of how I've been using this in real life.

Claude Tag has completely changed the way I do work for the last 4 months. Except… it's not Claude Tag. Anthropic only announced that a few hours ago, and I don't even have access yet. But I did build a version of it for myself which I've been using for months now. Here's how. 4 months ago, inspired by the success of OpenClaw, I wondered what would happen if I let Claude Code on its own computer 24x7. So I built a simple harness that allowed me to turn any Mac into an AI employee with Claude Code headless mode (-p). Today, I manage 3 such AI employees. It started with Luo Ji — my and my brother Piyush Agarwal's AI co-founder, running in our personal Slack. Luo does real work for us. We've been writing a 100% of the code for 3 products on Slack with Luo now. It manages our emails and gives us a little brief each day with things we need to take action on. And so much more. And it's not just the two of us. On the consulting team at Every 🪨, we run Claudie and for the editorial team, Andy. Same architecture, same Slack, months of real work. They help the teams with work related to project management, chief-of-staff work, data hygiene, building decks, writing first drafts, even browsing X on their own account for AI updates. So it's mindblowing to see that Anthropic landed on the exact same architecture I did. Claude Tag is an AI employee that lives in your Slack workspace and does work autonomously. Anthropic says they've been running it internally for the better part of this year — opening PRs, doing real work. And so have I. So has my whole team. The architectural decisions Anthropic baked into Claude Tag are the ones we arrived at too: - Built on Claude Code - Uses its own accounts - A separate employee per team - Slack as the interface This is the future of work, and I've been living it for months. I've shifted all of my workflows — code, PRs, even the non-technical stuff — out of Claude Code and the Claude app and into Slack. I've had entire weeks where I never opened Claude Code on my laptop. Here's a video walkthrough of how I've been using this in real life.

Nityesh

36,790 Aufrufe • vor 2 Monaten

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.

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 Aufrufe • vor 10 Monaten

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.

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,353,501 Aufrufe • vor 1 Monat

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.

Palani — oss/acc

13,971 Aufrufe • vor 2 Monaten

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

815,862 Aufrufe • vor 2 Monaten

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

André König

36,124 Aufrufe • vor 4 Monaten

the bottleneck Karpathy keeps pointing at isn't the model. it's the file you wrote three months ago telling it how to work. his whole framing: code isn't the verb anymore. > you express your will to agents 16 hours a day. > running more of them in parallel is the unlock. > and he drops this line halfway through, no fanfare: "now you can have optimization over the instructions." that's the sentence. the instructions are the new bottleneck. and almost nobody has a process for optimizing them. i built one for myself. it reads 100 of my past Claude Code sessions and rewrites my CLAUDE.md from what the transcripts show, not from what i thought i wrote. one Saturday morning later: a 38-line memory file. 73% of my old CLAUDE.md got deleted. most of it was one-off corrections that hardened into permanent rules months ago and were quietly steering every agent i ran. four behavior patterns surfaced that i had never written down. the loudest one: my prose corrections outnumber code corrections 8.2 to 1. that ratio was running silently through every session for 90 days. you don't need a smarter model. you need an instruction file that still describes how you actually work. listen to the podcast for the framing. open the article for the script that does the optimization.

the bottleneck Karpathy keeps pointing at isn't the model. it's the file you wrote three months ago telling it how to work. his whole framing: code isn't the verb anymore. > you express your will to agents 16 hours a day. > running more of them in parallel is the unlock. > and he drops this line halfway through, no fanfare: "now you can have optimization over the instructions." that's the sentence. the instructions are the new bottleneck. and almost nobody has a process for optimizing them. i built one for myself. it reads 100 of my past Claude Code sessions and rewrites my CLAUDE.md from what the transcripts show, not from what i thought i wrote. one Saturday morning later: a 38-line memory file. 73% of my old CLAUDE.md got deleted. most of it was one-off corrections that hardened into permanent rules months ago and were quietly steering every agent i ran. four behavior patterns surfaced that i had never written down. the loudest one: my prose corrections outnumber code corrections 8.2 to 1. that ratio was running silently through every session for 90 days. you don't need a smarter model. you need an instruction file that still describes how you actually work. listen to the podcast for the framing. open the article for the script that does the optimization.

Mnimiy

50,181 Aufrufe • vor 3 Monaten

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,692 Aufrufe • vor 2 Monaten

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.

am.will

16,916 Aufrufe • vor 6 Monaten

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. 🧵

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 Aufrufe • vor 1 Monat

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 Aufrufe • vor 1 Monat

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

JJ Englert

29,809 Aufrufe • vor 4 Monaten

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 Aufrufe • vor 2 Monaten

I have been testing Grok Bot for the last week and it's EXCELLENT It is your own personal fleet of AI agents doing work for you 24/7 In this video I give you a FULL walkthrough of the tool, how it works, and how to 100x your productivity with it SpaceXAI COOKED

I have been testing Grok Bot for the last week and it's EXCELLENT It is your own personal fleet of AI agents doing work for you 24/7 In this video I give you a FULL walkthrough of the tool, how it works, and how to 100x your productivity with it SpaceXAI COOKED

Alex Finn

135,468 Aufrufe • vor 19 Tagen

Klarna CEO Sebastian Siemiatkowski never learned how to code. But after a summer using Cursor, he now brings working prototypes to meetings instead of asking engineers to interpret his ideas: “Because I'm not an engineer, I've been vibe coding my whole life.” “I come into the meeting room, there's tons of product people and engineers. I say, ‘I think we should build an app that kind of does this, and it should work like that.’ They try to make sense of what is saying.” “I've never seen the code. I don't know how they made it. It's beautiful, I like our app. I think it's nice but, I don't know how it works.” “So to me, I've been vibe coding for 20 years. The only difference is now I'm sitting with a computer, and I'm doing it with AI and it's coming back with the prototype in 20 minutes.”

Klarna CEO Sebastian Siemiatkowski never learned how to code. But after a summer using Cursor, he now brings working prototypes to meetings instead of asking engineers to interpret his ideas: “Because I'm not an engineer, I've been vibe coding my whole life.” “I come into the meeting room, there's tons of product people and engineers. I say, ‘I think we should build an app that kind of does this, and it should work like that.’ They try to make sense of what is saying.” “I've never seen the code. I don't know how they made it. It's beautiful, I like our app. I think it's nice but, I don't know how it works.” “So to me, I've been vibe coding for 20 years. The only difference is now I'm sitting with a computer, and I'm doing it with AI and it's coming back with the prototype in 20 minutes.”

sourcery

149,352 Aufrufe • vor 7 Monaten

Anthropic shows this video to every new employee. Someone re-uploaded it. I hope Anthropic doesn't see this. 14 minutes of how the Claude team actually uses Claude in real work. I watched the recording last night and kept pausing it. Each time realizing I've been using Claude like a toy. claude.md + loops is what makes Claude stop fighting you and start working for you. Most people will keep using Claude the hard way.

Anthropic shows this video to every new employee. Someone re-uploaded it. I hope Anthropic doesn't see this. 14 minutes of how the Claude team actually uses Claude in real work. I watched the recording last night and kept pausing it. Each time realizing I've been using Claude like a toy. claude.md + loops is what makes Claude stop fighting you and start working for you. Most people will keep using Claude the hard way.

Raytar

257,844 Aufrufe • vor 2 Monaten

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 Aufrufe • vor 1 Jahr

Today we open the Zapier SDK to everyone. If you're building with AI agents, this is for you. I've been using this for 2 months. It's totally changed how I do my job. You install it in your coding agent. Cursor, Claude Code, Codex, whatever you use. Now that agent has access to 8,000+ apps through Zapier and can do anything those APIs can do. I think it’s the most powerful thing we’ve launched in years. Now in open beta. Just give this link right to your agent:

Today we open the Zapier SDK to everyone. If you're building with AI agents, this is for you. I've been using this for 2 months. It's totally changed how I do my job. You install it in your coding agent. Cursor, Claude Code, Codex, whatever you use. Now that agent has access to 8,000+ apps through Zapier and can do anything those APIs can do. I think it’s the most powerful thing we’ve launched in years. Now in open beta. Just give this link right to your agent:

Wade Foster

175,178 Aufrufe • vor 4 Monaten

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

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 Aufrufe • vor 17 Tagen