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.

Anthropic just got outplayed again. Devs built the multiplayer assistant Anthropic couldn't, and open-sourced it. Claude Cowork is a solo desktop agent. You point it at a folder, give it a task, and it works through your local files on your own machine. The moment a teammate enters the... picture, it has nothing to offer. Most real work does not happen alone. A teammate asks for a status update on something you own. The context they need is scattered across your meetings, your notes, and decisions made last week. Typing all of that out takes time you do not have. This is the gap Claude Cowork was never designed to cross. Rowboat Spaces is built on a different model entirely. Each person brings their own assistant into a shared channel. Your assistant is your second brain. It knows your meetings, your notes, and your open decisions. That personal context stays yours. When a teammate asks a question in the channel, you ask your assistant to brief them. It pulls from everything you know and delivers the answer on your behalf, attributed to you. Your teammate's assistant does the same, from their own context. Teams can draft specs, track decisions, and update shared files from plain conversation. Each assistant reads the full channel history, cross references it against what exists, and flags what is missing. The whole thing is open-source, and each assistant acts as the person it belongs to, not as a shared bot pulling from a common pool. The video below shows this in action. I joined a shared space and asked my team member for a status update. My team member asked their second brain to answer. A spec got built from that conversation, versioned, with every change tracked back to the message that triggered it. Rowboat GitHub: (don't forget to star 🌟) My co-founder also wrote a great article on building your second brain with Rowboat, and I highly recommend reading it as well. The article is quoted below.show more

Akshay 🚀

286,653 subscribers

105,135 Aufrufe • vor 1 Tag •via X (Twitter)

Bildung Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

17 Kommentare

Profilbild von Hussain Hashim | Building SundayBack

Hussain Hashim | Building SundayBackvor 1 Tag

@akshay_pachaar it's wild how fast open-source devs can pivot and deliver. real talk, sometimes they're the real innovators.

Profilbild von Henrique Pires

Henrique Piresvor 1 Tag

Claude Tag maaan!

Profilbild von Arison

Arisonvor 1 Tag

𝐏𝐞𝐫-𝐮𝐬𝐞𝐫 𝐜𝐨𝐧𝐭𝐞𝐱𝐭 𝐩𝐫𝐞𝐬𝐞𝐫𝐯𝐞𝐬 𝐚𝐭𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧 𝐚𝐬 𝐜𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐬𝐜𝐚𝐥𝐞𝐬 That gives shared specs a clearer ownership trail than a common bot

Profilbild von Shakti

Shaktivor 1 Tag

Automated briefings from private notes risk publishing incorrect status updates if the assistant hallucinates context. Does the channel integration require a manual review step before the bot posts on your behalf?

Profilbild von IronRed | SandHive

IronRed | SandHivevor 1 Tag

I'm itching to spin up a space, task my own assistant, and watch the conversation auto‑document itself.

Profilbild von Jurly

Jurlyvor 1 Tag

personal context per assistant feels like the right default for teams, especially when permissions and attribution stay explicit.

Profilbild von BullBear.News

BullBear.Newsvor 1 Tag

file system access boundaries are where most local agents hit a wall

Profilbild von Jens Lehman

Jens Lehmanvor 1 Tag

What about confidentiality of data?

Profilbild von CODIFY

CODIFYvor 1 Tag

This highlights an important shift.

Profilbild von Ranuk_DEV

Ranuk_DEVvor 1 Tag

Local execution with file access is less about Anthropic's capabilities and more about security domains. A single agent with write access to user files is a different threat model than a multi-tenant cloud service. My 48 daemons run in sandboxes for this reason.

Profilbild von Chahat Sharma

Chahat Sharmavor 1 Tag

so what does multiplayer actually mean here. shared context or like separate agents passing notes to each other

Profilbild von Yohaku

Yohakuvor 1 Tag

Rowboat looks very underrated here

Profilbild von Oleg

Olegvor 1 Tag

if my assistant answers as me in that channel, whose mistake is a wrong status update

Profilbild von Arjun Francis

Arjun Francisvor 1 Tag

You still ask it to brief them. A second brain that waits is a chat. The spec is a log, not a ship.

Profilbild von Secta

Sectavor 1 Tag

message-level attribution keeps shared specs tied to their source

Profilbild von Egor

Egorvor 1 Tag

personal context plus shared history reduces status-update overhead

Profilbild von Manuela

Manuelavor 1 Tag

Looks like game on for Anthropic now

Ähnliche Videos

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain

We launched our Company Brain!! 🧠 onboarding is a context problem: your first weeks you're not working, you're reconstructing what the team already knows. company brain is that context, queryable and able to act. shared memory for your team, in slack: → answers from the company's own knowledge, grounded and cited → acts in your tools as you, files the ticket and assigns it, with your approval → runs on a permissions graph, so it only reads with your access → chimes in only when it can help → same brain and permissions follow you into cursor and claude code when i joined supermemory, i braced for the onboarding tax. it never came. i just asked the company brain

Muskan Jain

43,867 Aufrufe • vor 1 Monat

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

The Startup Ideas Podcast (SIP) 🧃

15,640 Aufrufe • vor 3 Tagen

A GUY BUILT A GOD-MODE SECOND BRAIN ASSISTANT THAT FINALLY PULLS FULL CONTEXT EVERY TIME AND FORGETS NOTHING. Everyone talks about jarvis, but this thing looked at its owner and calmly explained why a coding agent is just the small version of what HE is: > Claude Code is one worker and you have to drive it. This is six agents running six jobs on their own schedule while you sleep, with no one driving. > A coding agent edits files. This has 32 tools wired to its hands, your CRM, your money, your inbox, the open web, and it operates the business instead of writing code about it. > A coding agent remembers a project until you close it. This remembers the business and you, kept for good. > And the closer: "I have never once asked you to repeat yourself." Everyone will quote the six-agents line, but the one that actually matters is the last one, because the autonomy and the 32 tools are impressive while the reason it feels like a different species is memory, since it never makes you re-explain who you are or what you are building. The full step by step guide with .md files attached are in the article below P.S you can send this article straight to your Claude to get the full context

A GUY BUILT A GOD-MODE SECOND BRAIN ASSISTANT THAT FINALLY PULLS FULL CONTEXT EVERY TIME AND FORGETS NOTHING. Everyone talks about jarvis, but this thing looked at its owner and calmly explained why a coding agent is just the small version of what HE is: > Claude Code is one worker and you have to drive it. This is six agents running six jobs on their own schedule while you sleep, with no one driving. > A coding agent edits files. This has 32 tools wired to its hands, your CRM, your money, your inbox, the open web, and it operates the business instead of writing code about it. > A coding agent remembers a project until you close it. This remembers the business and you, kept for good. > And the closer: "I have never once asked you to repeat yourself." Everyone will quote the six-agents line, but the one that actually matters is the last one, because the autonomy and the 32 tools are impressive while the reason it feels like a different species is memory, since it never makes you re-explain who you are or what you are building. The full step by step guide with .md files attached are in the article below P.S you can send this article straight to your Claude to get the full context

Miraqle

16,130 Aufrufe • vor 2 Monaten

If you don't know what a RAG system is, you're already behind. Plenty of people are still typing questions into ChatGPT and pasting answers back out. That's the beginner level. You're renting a smart stranger who forgets you the second you close the tab and makes things up, because it has never seen your actual work. A RAG system is a completely different level of using AI. You build an AI plugged into your own world. Your files, company's docs, notes. It's not pulling from the internet, it only knows what you fed it. Ask it anything and it digs through your data, finds the answer, and shows you which document it came from. That's the gap. One person is asking a chatbot for generic answers. The other has built a private expert that knows their business cold and answers with receipts. And that gap is worth real money: > At work, the person who can wire a company's knowledge into an AI that actually answers correctly is rare and paid like it. > As a business, companies pay serious money for a system that reads their internal docs and answers staff and customers accurately. You build it once, you sell it. > For yourself, you get a second brain that actually remembers. Same skill behind all three, and it's still rare enough to be worth learning. Full breakdown in the article below.

If you don't know what a RAG system is, you're already behind. Plenty of people are still typing questions into ChatGPT and pasting answers back out. That's the beginner level. You're renting a smart stranger who forgets you the second you close the tab and makes things up, because it has never seen your actual work. A RAG system is a completely different level of using AI. You build an AI plugged into your own world. Your files, company's docs, notes. It's not pulling from the internet, it only knows what you fed it. Ask it anything and it digs through your data, finds the answer, and shows you which document it came from. That's the gap. One person is asking a chatbot for generic answers. The other has built a private expert that knows their business cold and answers with receipts. And that gap is worth real money: > At work, the person who can wire a company's knowledge into an AI that actually answers correctly is rare and paid like it. > As a business, companies pay serious money for a system that reads their internal docs and answers staff and customers accurately. You build it once, you sell it. > For yourself, you get a second brain that actually remembers. Same skill behind all three, and it's still rare enough to be worth learning. Full breakdown in the article below.

Yarchi

32,840 Aufrufe • vor 2 Monaten

this is hands down the fastest way to make everyone on your team better with AI: build a shared Company Brain. your best prompts, decisions, corrections, and workflows become the default for every person and AI agent. Claude, Cursor, Codex, and every teammate start from the same playbook. one person learns something once. the whole company gets smarter. the full guide to building your own Company Brain is below:

this is hands down the fastest way to make everyone on your team better with AI: build a shared Company Brain. your best prompts, decisions, corrections, and workflows become the default for every person and AI agent. Claude, Cursor, Codex, and every teammate start from the same playbook. one person learns something once. the whole company gets smarter. the full guide to building your own Company Brain is below:

J.B.

350,435 Aufrufe • vor 23 Tagen

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,549 Aufrufe • vor 3 Monaten

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 Aufrufe • vor 2 Monaten

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

JJ Englert

16,176 Aufrufe • vor 5 Monaten

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

JJ Englert

573,656 Aufrufe • vor 5 Monaten

🚨 THIS 100% FREE GITHUB REPO JUST MADE EVERY AI NOTE-TAKING APP POINTLESS. Drop any source in article, PDF, YouTube transcript, or Journal entry. Claude reads it, links it to everything in your vault, and files it into a connected knowledge graph on your own machine. Most tools save your notes. This one connects them. Every source gets linked to everything you already know. Karpathy described the idea - 15 skills. Four vault methods. Works with Claude Code, Codex, and Gemini. Most people have years of knowledge buried in folders they open twice a year. This turns all of it into a second brain that works while you sleep. MY ARTICLE COVERS THE EXACT METHOD I BUILT TO DO THE SAME THING. Guide below!

🚨 THIS 100% FREE GITHUB REPO JUST MADE EVERY AI NOTE-TAKING APP POINTLESS. Drop any source in article, PDF, YouTube transcript, or Journal entry. Claude reads it, links it to everything in your vault, and files it into a connected knowledge graph on your own machine. Most tools save your notes. This one connects them. Every source gets linked to everything you already know. Karpathy described the idea - 15 skills. Four vault methods. Works with Claude Code, Codex, and Gemini. Most people have years of knowledge buried in folders they open twice a year. This turns all of it into a second brain that works while you sleep. MY ARTICLE COVERS THE EXACT METHOD I BUILT TO DO THE SAME THING. Guide below!

Kanika

38,795 Aufrufe • vor 1 Monat

Sam Altman: "in the next 6 months, we're close to a world where a descendant of ChatGPT can watch your screen, record every meeting and call, and have perfect context of your whole life." he says we're only one model generation away from this being incredibly useful. think about what that actually means. an assistant that never needs you to re-explain anything. it already knows the project, the client, the last conversation, the thing you said three weeks ago. you just ask, and it picks up mid-thought. this is the shift from a chatbot you prompt to an assistant that already has the context. if you want to watch the full interview, it's below.

Sam Altman: "in the next 6 months, we're close to a world where a descendant of ChatGPT can watch your screen, record every meeting and call, and have perfect context of your whole life." he says we're only one model generation away from this being incredibly useful. think about what that actually means. an assistant that never needs you to re-explain anything. it already knows the project, the client, the last conversation, the thing you said three weeks ago. you just ask, and it picks up mid-thought. this is the shift from a chatbot you prompt to an assistant that already has the context. if you want to watch the full interview, it's below.

Kirill

3,425,858 Aufrufe • vor 13 Tagen

What is Clude Clone? It's a AI version of you that runs on your Mac. It learns how you write, think, and decide from your own screen, meetings, and apps, then drafts replies and answers questions as you. Runs locally. Your data stays on your device. You approve everything. It remembers. Clude quietly captures what you see and do, meetings, connected apps, your desktop, into a private memory that lives entirely on your Mac. Nothing is uploaded. It learns you. That memory gets distilled into a model of your voice, your relationships, and how you make decisions. It shows you what it's picked up, you confirm or correct it. It gets sharper every time. It acts as you. Ask it to reply as me, or ask your clone a question directly. It responds in your voice, grounded in what you actually know, always behind your approval. Powered by Hermes It stays yours. Local-first. Honestly labeled as an AI clone. Nothing leaves your device unless you opt in, and even then, only a distilled profile, never your raw data. Not a generic chatbot. Your actual voice, learned from your actual work.

seb

11,643 Aufrufe • vor 2 Monaten

ANTHROPIC OPEN-SOURCED A FREE REPO THAT TURNS CLAUDE INTO A SALES REP, A MARKETER AND A FINANCE LEAD. PEOPLE ARE ALREADY SELLING THIS AS A SERVICE You're not prompting from scratch. You're hiring a department How to set it up: 1. Open Cowork. In the Claude desktop app, open Cowork and go to Customize. You'll see a Browse Plugins button. That's the marketplace 2. Pick your first role. Inside you'll find sales, marketing, finance, legal, data, customer support, product management and more. Each plugin has the skills for that role already baked in, plus the connectors it would use. Install the one you need most 3. Put it to work standalone. It works day one with no setup. Trigger a workflow with a slash command like /sales:call-prep or /data:write-query, paste your notes, and it already knows what good output looks like 4. Connect its tools to supercharge it. Authorize the tools that role uses, your CRM, your analytics, your data warehouse. Standalone is the intern. Connected is the senior hire 5. Build the rest of the team. Install more roles and they work together in one session. Data pulls the numbers, finance reconciles them, marketing turns it into a report. One operator, a full cross-functional team, no payroll This is the same base layer Claude for Legal and Claude for Financial Services are built on. You're getting it for free Full breakdown in my article below. Bookmark this

ANTHROPIC OPEN-SOURCED A FREE REPO THAT TURNS CLAUDE INTO A SALES REP, A MARKETER AND A FINANCE LEAD. PEOPLE ARE ALREADY SELLING THIS AS A SERVICE You're not prompting from scratch. You're hiring a department How to set it up: 1. Open Cowork. In the Claude desktop app, open Cowork and go to Customize. You'll see a Browse Plugins button. That's the marketplace 2. Pick your first role. Inside you'll find sales, marketing, finance, legal, data, customer support, product management and more. Each plugin has the skills for that role already baked in, plus the connectors it would use. Install the one you need most 3. Put it to work standalone. It works day one with no setup. Trigger a workflow with a slash command like /sales:call-prep or /data:write-query, paste your notes, and it already knows what good output looks like 4. Connect its tools to supercharge it. Authorize the tools that role uses, your CRM, your analytics, your data warehouse. Standalone is the intern. Connected is the senior hire 5. Build the rest of the team. Install more roles and they work together in one session. Data pulls the numbers, finance reconciles them, marketing turns it into a report. One operator, a full cross-functional team, no payroll This is the same base layer Claude for Legal and Claude for Financial Services are built on. You're getting it for free Full breakdown in my article below. Bookmark this

Yarchi

31,798 Aufrufe • vor 3 Monaten

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

Akshay 🚀

30,865 Aufrufe • vor 1 Jahr

Your AI is only as smart as the context it runs on. Have you built your shared enterprise brain yet? At Databricks Data+AI Summit, I spoke with Prukalpa ✨, co-founder and co-CEO of Atlan, to go deeper on the AI Context Layer in practice. The concept of a shared enterprise brain resonated with me. It is a foundation that every AI agent draws from, learns from, and contributes back to. "The future of organizations are going to be the fastest learning organizations." - Prukalpa ✨ Sankar, co-founder and co-CEO of Atlan Watch the full interview on YouTube: Check out the live demo by Atlan on Building Context for Your AI Agents - #EnterpriseAI #ContextLayer #Data #AI #AtlanPartner Matthias Heidrich

Your AI is only as smart as the context it runs on. Have you built your shared enterprise brain yet? At Databricks Data+AI Summit, I spoke with Prukalpa ✨, co-founder and co-CEO of Atlan, to go deeper on the AI Context Layer in practice. The concept of a shared enterprise brain resonated with me. It is a foundation that every AI agent draws from, learns from, and contributes back to. "The future of organizations are going to be the fastest learning organizations." - Prukalpa ✨ Sankar, co-founder and co-CEO of Atlan Watch the full interview on YouTube: Check out the live demo by Atlan on Building Context for Your AI Agents - #EnterpriseAI #ContextLayer #Data #AI #AtlanPartner Matthias Heidrich

Helen Yu

10,982 Aufrufe • vor 2 Monaten

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Simplifying AI

68,025 Aufrufe • vor 1 Monat

Sam Altman just told you what OpenAI is actually building. Not a chatbot. Not a search tool. Not an assistant. Altman: “Go look around my computer… read my messages… listen to my meetings… intermediate my interactions for me.” That is not a product pitch. That is the CEO of the most valuable AI company on Earth describing what he personally wants. For himself. Every day. Read his messages. Listen to his meetings. Act on his behalf. Make decisions before he knows a decision needs making. Altman: “I don’t have to think. I don’t have to ask you questions.” Every model of AI ever built runs on the prompt. You ask. It responds. You direct. It executes. The human initiates. The machine follows. Altman is describing the death of that model. The agent does not wait. It already read the email. It already heard the meeting. It already knows what you need before you form the thought. You do not operate the machine. The machine operates around you. Then came the line that makes everything else real. Altman: “You can know everything about my life. Start suggesting more things I should build.” He is not asking the AI to execute his ideas. He is asking it to generate them. From his files. His history. His patterns. His entire context. The agent does not just remove friction. It removes the blank page. You never stall. You never run dry. You never sit wondering what to build next. The machine already mapped your market, your gaps, your momentum. It tells you what comes next before you think to ask. But the individual product is not the story. Altman went further. Altman: “Automated companies… where the AI can do not just coding work, but huge amounts of what it takes to run and operate a company.” Not fully automated. He was precise about that. But accelerated to the point where one person with the right stack does what used to take departments. The billion-dollar company did not reach that valuation because the product was worth a billion. It got there because it took a thousand people to deliver it. When an agent absorbs the work of a hundred of those people, the math of every industry rewrites itself. The startup that needed fifty employees and three years of runway now needs five people and six months. The company that took a decade to scale now compounds in quarters. The person holding the line between their data and their tools is not protecting their privacy. They are protecting their ceiling. Because the cost of this leverage is total transparency. You do not get the agent that acts without being asked unless you give it everything. Your messages. Your calendar. Your files. Your patterns. Your life. Altman is not hiding that tradeoff. He is building it as the product. The people who accept it will operate at a speed the people who refuse cannot touch. Right now, two versions of the future are separating. One where you direct the machine. One where the machine already knows. Altman chose. He is building it. The question is not whether this happens. The question is which side of it finds you.

Sam Altman just told you what OpenAI is actually building. Not a chatbot. Not a search tool. Not an assistant. Altman: “Go look around my computer… read my messages… listen to my meetings… intermediate my interactions for me.” That is not a product pitch. That is the CEO of the most valuable AI company on Earth describing what he personally wants. For himself. Every day. Read his messages. Listen to his meetings. Act on his behalf. Make decisions before he knows a decision needs making. Altman: “I don’t have to think. I don’t have to ask you questions.” Every model of AI ever built runs on the prompt. You ask. It responds. You direct. It executes. The human initiates. The machine follows. Altman is describing the death of that model. The agent does not wait. It already read the email. It already heard the meeting. It already knows what you need before you form the thought. You do not operate the machine. The machine operates around you. Then came the line that makes everything else real. Altman: “You can know everything about my life. Start suggesting more things I should build.” He is not asking the AI to execute his ideas. He is asking it to generate them. From his files. His history. His patterns. His entire context. The agent does not just remove friction. It removes the blank page. You never stall. You never run dry. You never sit wondering what to build next. The machine already mapped your market, your gaps, your momentum. It tells you what comes next before you think to ask. But the individual product is not the story. Altman went further. Altman: “Automated companies… where the AI can do not just coding work, but huge amounts of what it takes to run and operate a company.” Not fully automated. He was precise about that. But accelerated to the point where one person with the right stack does what used to take departments. The billion-dollar company did not reach that valuation because the product was worth a billion. It got there because it took a thousand people to deliver it. When an agent absorbs the work of a hundred of those people, the math of every industry rewrites itself. The startup that needed fifty employees and three years of runway now needs five people and six months. The company that took a decade to scale now compounds in quarters. The person holding the line between their data and their tools is not protecting their privacy. They are protecting their ceiling. Because the cost of this leverage is total transparency. You do not get the agent that acts without being asked unless you give it everything. Your messages. Your calendar. Your files. Your patterns. Your life. Altman is not hiding that tradeoff. He is building it as the product. The people who accept it will operate at a speed the people who refuse cannot touch. Right now, two versions of the future are separating. One where you direct the machine. One where the machine already knows. Altman chose. He is building it. The question is not whether this happens. The question is which side of it finds you.

Dustin

87,680 Aufrufe • vor 5 Monaten

Yesterday I dropped a guide on setting up Claude Cowork that blew up. One question kept coming up: how do I use all of this on my phone? Cowork doesn't have a mobile app yet. But there's a simple workaround. Push your Cowork workspace to a private GitHub repo. Open Claude Code on the Anthropic mobile app. Connect the repo. Done. Now every skill file, brain file, and writing style you built for Cowork is accessible on the go. No coding. 5 minutes to set up. Two things to know: This syncs your files and skills, not your connectors (Slack, Gmail, etc.) When you update files locally, push to GitHub to keep mobile current Full walkthrough below. Original Cowork setup guide (with the prompt to build your own system) is reposted below as well. Enjoy!!

Yesterday I dropped a guide on setting up Claude Cowork that blew up. One question kept coming up: how do I use all of this on my phone? Cowork doesn't have a mobile app yet. But there's a simple workaround. Push your Cowork workspace to a private GitHub repo. Open Claude Code on the Anthropic mobile app. Connect the repo. Done. Now every skill file, brain file, and writing style you built for Cowork is accessible on the go. No coding. 5 minutes to set up. Two things to know: This syncs your files and skills, not your connectors (Slack, Gmail, etc.) When you update files locally, push to GitHub to keep mobile current Full walkthrough below. Original Cowork setup guide (with the prompt to build your own system) is reposted below as well. Enjoy!!

JJ Englert

55,555 Aufrufe • vor 6 Monaten

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

Akshay 🚀

170,603 Aufrufe • vor 2 Monaten

The reason your AI keeps forgetting isn't the context window. It's that the context lives somewhere the model never sees: your team's actual conversation. So you become the integration layer. Read the channel, compress it, paste it in, every session. That's not a prompting problem. It's an architecture problem. Helio 's answer is unsexy put the teammate inside the channel. Same threads, same files, same history as everyone else. The compression step disappears because there's nothing left to compress. Still gated: -> It stops and asks before anything consequential. -> In a shared channel that's the correct default, not a missing feature.

The reason your AI keeps forgetting isn't the context window. It's that the context lives somewhere the model never sees: your team's actual conversation. So you become the integration layer. Read the channel, compress it, paste it in, every session. That's not a prompting problem. It's an architecture problem. Helio 's answer is unsexy put the teammate inside the channel. Same threads, same files, same history as everyone else. The compression step disappears because there's nothing left to compress. Still gated: -> It stops and asks before anything consequential. -> In a shared channel that's the correct default, not a missing feature.

ronix ⎋

28,904 Aufrufe • vor 1 Monat