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

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

На главную

Introducing SuperIsland — Dynamic Island for Mac, with extensions 🚀 SuperIsland turns your Mac's notch into a living, breathing widget space, just like Dynamic Island on iPhone. But we go further: it's programmable. Built-in features: 🎵 Live Media Player with playback controls 📅 Calendar widget for upcoming events 🌤️...

nullbytes00's profile picture

Shobhit - Building SuperCmd

1,370 subscribers

22,016 просмотров • 5 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

I built my first macOS app :) Live on the App Store now: Meet NotchShelf. A small utility that lives in the notch and gives you quick access to things you actually need during the day. Built entirely with SwiftUI. What it does: 📂 Quick Shelf: A temporary holding zone for drag-and-drop files. 💻 Screenshot Magnet: Automatically catches screenshots for quick and easy access 📅 Calendar View: Have a quick glance at your events. 📸 One-tap camera: A one-tap camera check before your next meeting. 📝 Quick Note: Jot down important quick notes for thoughts, reminders, or meeting points. and many more advancements and new features coming really soon!
0:33

I built my first macOS app :) Live on the App Store now: Meet NotchShelf. A small utility that lives in the notch and gives you quick access to things you actually need during the day. Built entirely with SwiftUI. What it does: 📂 Quick Shelf: A temporary holding zone for drag-and-drop files. 💻 Screenshot Magnet: Automatically catches screenshots for quick and easy access 📅 Calendar View: Have a quick glance at your events. 📸 One-tap camera: A one-tap camera check before your next meeting. 📝 Quick Note: Jot down important quick notes for thoughts, reminders, or meeting points. and many more advancements and new features coming really soon!

OG

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

I have made over $100k shipping projects with ai. Productivity has gone through the roof but its more stressful than ever tbh. Thats why I built CNVS. Its a place for Ai to not just make you more efficient, but also more organized, like a monk shipping at light speed. Every project gets its own canvas, so you can effortlessly switch between them. Each canvas gets a "recipe", so you can hop right back into deep work in seconds. Eliminating the cognitive overhead of getting started. I built 14 beautiful themes so your brain can start associating the theme with the project. PS - its really hard shipping apps, i hope CNVS makes you feel more in control of your life <3 built with love from a dad working away in the basement. PPS - its a lifetime license because you don't need any more subscriptions in your life. Im shipping new features and improvements based on user feedback every week. PPPS - this uses all your exsisting ai subs ( claude code, codex, cursor, etc.. )
2:25

I have made over $100k shipping projects with ai. Productivity has gone through the roof but its more stressful than ever tbh. Thats why I built CNVS. Its a place for Ai to not just make you more efficient, but also more organized, like a monk shipping at light speed. Every project gets its own canvas, so you can effortlessly switch between them. Each canvas gets a "recipe", so you can hop right back into deep work in seconds. Eliminating the cognitive overhead of getting started. I built 14 beautiful themes so your brain can start associating the theme with the project. PS - its really hard shipping apps, i hope CNVS makes you feel more in control of your life <3 built with love from a dad working away in the basement. PPS - its a lifetime license because you don't need any more subscriptions in your life. Im shipping new features and improvements based on user feedback every week. PPPS - this uses all your exsisting ai subs ( claude code, codex, cursor, etc.. )

Max Blade

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

✨ The power of AI cutting-edge technology to revolutionize Immersive experience within Earniverse. ✨ Today, get an introduction of some of the core AI features inside Earniverse! 🌊 State-of-the-art Ocean AI Simulation to Immerse yourself in stunning realism 🌤️ Dynamic Skies where AI seamlessly adjusts lighting and atmospheric conditions to match your surroundings, creating a truly dynamic environment that responds to your every move. 🌦️ AI Meteo Management system to ensure that weather changes naturally and organically, driven by AI algorithms that mimic real-world patterns ⚙️ And that's not all – our Performance Management has taken a giant leap forward. 📈 AI technology intelligently optimizes resource usage, by enhancing graphics quality as you approach specific 3D elements in the map. The closer your look, the higher the quality of graphics you'll experience without putting down your hardware, all in real-time! 🎥 Curious to see the magic in action? Check out the video to witness how our AI-powered system delivers top-notch performance and ultra-realistic simulations. 📹👀 🌐 The future of virtual reality is here, and it's waiting for you in Earniverse Metaverse! Join us on this exhilarating journey as we redefine what's possible in the realm of immersive experiences. 🚀 #Earniverse #Metaverse #ImmersiveReality #AI #Performance #Simulation
0:25

✨ The power of AI cutting-edge technology to revolutionize Immersive experience within Earniverse. ✨ Today, get an introduction of some of the core AI features inside Earniverse! 🌊 State-of-the-art Ocean AI Simulation to Immerse yourself in stunning realism 🌤️ Dynamic Skies where AI seamlessly adjusts lighting and atmospheric conditions to match your surroundings, creating a truly dynamic environment that responds to your every move. 🌦️ AI Meteo Management system to ensure that weather changes naturally and organically, driven by AI algorithms that mimic real-world patterns ⚙️ And that's not all – our Performance Management has taken a giant leap forward. 📈 AI technology intelligently optimizes resource usage, by enhancing graphics quality as you approach specific 3D elements in the map. The closer your look, the higher the quality of graphics you'll experience without putting down your hardware, all in real-time! 🎥 Curious to see the magic in action? Check out the video to witness how our AI-powered system delivers top-notch performance and ultra-realistic simulations. 📹👀 🌐 The future of virtual reality is here, and it's waiting for you in Earniverse Metaverse! Join us on this exhilarating journey as we redefine what's possible in the realm of immersive experiences. 🚀 #Earniverse #Metaverse #ImmersiveReality #AI #Performance #Simulation

Earniverse

109,684 просмотров • 3 лет назад

growing your Twitch stream means posting short-form video on TikTok/Shorts/Reels. love it or hate it, that's the reality now. "at least one video a day" you hear everywhere. you probably already know this. you probably feel guilty for not posting enough. THAT ENDS NOW Shortify was just released into Early Access, and it changes the dynamic entirely. you already create mountains of content every time you go live. you just need help getting it out. the Highlight Hunter from FrostyTools already does incredible work finding those great moments for you at the press of a button. now, you can Shortify any of those hunted clips into a postable vertical video for short-form content, complete with dead air removal, advanced captions, attention-keeping cuts, and dynamic focus. these are the "daily vitamins" of content. you have to keep up with them every day, but they bring huge benefits when you do. you probably just don't have the time to keep up with it, especially if you're still learning how. it doesn't have to be like that anymore! if you're already editing, this can free up your time and focus to work on more ambitious projects, especially longer-form content. using it is SUPER easy: - sign into your FrostyTools dashboard via your Twitch account - run the Highlight Hunter on one of your VODs (or go to a hunted VOD if you already use it) - hit the 'Shortify' button on the moments you like best for your socials - in a minute or two, have your Shortified video ready to download and post! remember: you already make tons of content, you just need tools to get it out!
1:03

growing your Twitch stream means posting short-form video on TikTok/Shorts/Reels. love it or hate it, that's the reality now. "at least one video a day" you hear everywhere. you probably already know this. you probably feel guilty for not posting enough. THAT ENDS NOW Shortify was just released into Early Access, and it changes the dynamic entirely. you already create mountains of content every time you go live. you just need help getting it out. the Highlight Hunter from FrostyTools already does incredible work finding those great moments for you at the press of a button. now, you can Shortify any of those hunted clips into a postable vertical video for short-form content, complete with dead air removal, advanced captions, attention-keeping cuts, and dynamic focus. these are the "daily vitamins" of content. you have to keep up with them every day, but they bring huge benefits when you do. you probably just don't have the time to keep up with it, especially if you're still learning how. it doesn't have to be like that anymore! if you're already editing, this can free up your time and focus to work on more ambitious projects, especially longer-form content. using it is SUPER easy: - sign into your FrostyTools dashboard via your Twitch account - run the Highlight Hunter on one of your VODs (or go to a hunted VOD if you already use it) - hit the 'Shortify' button on the moments you like best for your socials - in a minute or two, have your Shortified video ready to download and post! remember: you already make tons of content, you just need tools to get it out!

Ken aka Frosty

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

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.
0:55

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

We just shipped a completely new concept for web interaction. Live on three․ws, we are thrilled to showcase this demo of persistent, interactive 3D AI Agents that live right in your browser. As the first mover in this space, we are achieving what hasn't been done before: seamlessly bridging the gap between traditional flat web pages and fully immersive, spatial 3D environments. We are fundamentally shifting how humans experience the internet. Here's how. Intelligent AI Agents. Your 3D companion drops right into the screen, tracks your cursor, and interacts with you based on the exact page you are viewing. Context-Aware Guide. Knows exactly where visitors are. It can point out and encourage clicks on the most important parts of a site. Highly Interactive. Turns to follow your cursor in real-time, waves when you navigate, and idles naturally. Playground Mode. Click your avatar and it seamlessly detaches into a full-page 3D stroll or platformer right in the browser. Use keyboard arrows on desktop and joystick on mobile. Choose Your Avatar. Pick exactly who walks the web with you from a fully customizable, hot-swappable roster. Polite & Lightweight. Built with smart compression and shared animation files. It monitors browser memory to guarantee zero slowdowns and respects "reduced motion" accessibility settings. Flat websites will be gone before you know it. The future is interactive, the future is intelligent. It's time to break AI out the chatbox. three․ws
3:00

We just shipped a completely new concept for web interaction. Live on three․ws, we are thrilled to showcase this demo of persistent, interactive 3D AI Agents that live right in your browser. As the first mover in this space, we are achieving what hasn't been done before: seamlessly bridging the gap between traditional flat web pages and fully immersive, spatial 3D environments. We are fundamentally shifting how humans experience the internet. Here's how. Intelligent AI Agents. Your 3D companion drops right into the screen, tracks your cursor, and interacts with you based on the exact page you are viewing. Context-Aware Guide. Knows exactly where visitors are. It can point out and encourage clicks on the most important parts of a site. Highly Interactive. Turns to follow your cursor in real-time, waves when you navigate, and idles naturally. Playground Mode. Click your avatar and it seamlessly detaches into a full-page 3D stroll or platformer right in the browser. Use keyboard arrows on desktop and joystick on mobile. Choose Your Avatar. Pick exactly who walks the web with you from a fully customizable, hot-swappable roster. Polite & Lightweight. Built with smart compression and shared animation files. It monitors browser memory to guarantee zero slowdowns and respects "reduced motion" accessibility settings. Flat websites will be gone before you know it. The future is interactive, the future is intelligent. It's time to break AI out the chatbox. three․ws

three.ws

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

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

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

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!
1:38

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!

Jake Mor

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

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)
0:24

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

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

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.
0:27

Introducing my newest app, TethrX, made with Grok 4.5 to access Grok Build on your phone. TethrX connects to Grok Build running on your own computer, so you can start a task from anywhere, follow Grok's reasoning as it works, approve every command before it runs, and review the code it writes. Your code never leaves your machine. The public TestFlight is now open, and a demonstration is below. You pair your phone by scanning a QR code, either on your local network or from anywhere through Tailscale. From there TethrX streams Grok's reasoning, tool calls, command output and file changes as they happen, and asks your approval before anything runs. Plan mode lets you read the plan before the work begins. When a task finishes you can review exactly what changed. TethrX lists the modified files in your project, shows a diff for each one, and lets you commit or discard the work without leaving your phone. The app supports slash commands, including /compact and any skills you have installed, along with voice dictation, queued messages and reusable prompts. Sessions can be searched and organised into folders, and you can pair several computers and switch between them. Siri can start a task or tell you what Grok is doing without opening the app, a home screen widget shows whether Grok is working, and a Live Activity tracks progress on your lock screen and Dynamic Island. Every session reports its context window, token usage and cost, the app can be locked behind Face ID, and your computer is kept awake for as long as a task is running. TethrX requires Grok Build installed and signed in on your computer, together with Node.js 20 or newer. A single command starts the bridge: npx tethrx-bridge TethrX is open source under the Apache License 2.0. Both the iOS client and the local bridge are available here: Grok 4.5 helped a lot, thanks to SpaceXAI for making Grok 4.5 exceptional.

Myrhe𝕩

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

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.
1:11

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.

Akshay 🚀

116,449 просмотров • 6 дней назад

TradingView to Screener & Marketsmith Extension ⚠️Please before asking in comment or DM, how to install, please read the full post, i have given the instructions also, and if you still cant follow it, You will find plenty of video on youtube on how to install the plugin, or ask AI⚠️ 🙏This was a killer timesaver tool for me, Hope it helps all, please share your feedbacks or gratitude in comments, will be sharing more plugin like this in future as well ☑️Overview This Chrome Extension natively integrates with TradingView, adding quick-access buttons to your top chart header. These buttons allow you to instantly view fundamental financial data for the currently active stock symbol on or evaluate it on MarketSmith India. > Features : > Screener New Tab: Opens the consolidated financials page for the current active TradingView symbol in a new browser tab. > Screener Splitscreen: Toggles a bottom-half split screen (iframe) inside the TradingView tab to load the page directly over your charts, letting you perform fundamental and technical analysis synchronously. > Marketsmith New Tab: Opens the stock evaluation page on MarketSmith India for the active symbol in a new tab. > This extension utilizes the Manifest V3 standard APIs and works smoothly across all modern Chromium-based browsers, including: Google Chrome Microsoft Edge Brave Browser Vivaldi Opera Arc Browser ⭐ Installation Instructions (Local/Unpacked) -> 1)Download or keep this entire extension folder on your computer. 1) Download or keep this entire extension folder on your computer: For Google Chrome: type chrome://extensions/ in the address bar. For Microsoft Edge: type edge://extensions/ in the address bar. For Brave: type brave://extensions/ in the address bar. Enable Developer mode using the toggle switch (usually located in the top-right corner). 3) Click the Load unpacked button that appears. 4) In the file explorer popup, choose this exact directory (the folder containing the manifest.json file). 5) The extension is now successfully installed! Open up TradingView to play around with the newly injected buttons in the top header. Github Repo ->
0:50

TradingView to Screener & Marketsmith Extension ⚠️Please before asking in comment or DM, how to install, please read the full post, i have given the instructions also, and if you still cant follow it, You will find plenty of video on youtube on how to install the plugin, or ask AI⚠️ 🙏This was a killer timesaver tool for me, Hope it helps all, please share your feedbacks or gratitude in comments, will be sharing more plugin like this in future as well ☑️Overview This Chrome Extension natively integrates with TradingView, adding quick-access buttons to your top chart header. These buttons allow you to instantly view fundamental financial data for the currently active stock symbol on or evaluate it on MarketSmith India. > Features : > Screener New Tab: Opens the consolidated financials page for the current active TradingView symbol in a new browser tab. > Screener Splitscreen: Toggles a bottom-half split screen (iframe) inside the TradingView tab to load the page directly over your charts, letting you perform fundamental and technical analysis synchronously. > Marketsmith New Tab: Opens the stock evaluation page on MarketSmith India for the active symbol in a new tab. > This extension utilizes the Manifest V3 standard APIs and works smoothly across all modern Chromium-based browsers, including: Google Chrome Microsoft Edge Brave Browser Vivaldi Opera Arc Browser ⭐ Installation Instructions (Local/Unpacked) -> 1)Download or keep this entire extension folder on your computer. 1) Download or keep this entire extension folder on your computer: For Google Chrome: type chrome://extensions/ in the address bar. For Microsoft Edge: type edge://extensions/ in the address bar. For Brave: type brave://extensions/ in the address bar. Enable Developer mode using the toggle switch (usually located in the top-right corner). 3) Click the Load unpacked button that appears. 4) In the file explorer popup, choose this exact directory (the folder containing the manifest.json file). 5) The extension is now successfully installed! Open up TradingView to play around with the newly injected buttons in the top header. Github Repo ->

Roshan Kumar

14,810 просмотров • 6 месяцев назад

I built a Claude skill that turns Claude Code into your personal coding tutor. The core insight: Claude Opus 4.5 is already the best tutor in the world. Anthropic cooked with this model! It has incredible emotional intelligence and deep coding knowledge. What this skill does is just provide a harness—a way for Claude to agentically build the right context about YOU so it can personalize the tutoring experience in exactly the right way. Here's what makes it work: Learner profile from day one. The first time you use it, Claude interviews you. It asks about your programming background, your goal (where do you want this to take you?), and who you are as a person. This gets saved and informs every single tutorial it ever writes for you. From the very first interaction, everything is 100% personalized. Tutorials that use YOUR code. When you ask to learn something, Claude doesn't give you generic examples from some blog post. It finds examples in the actual codebase you're working in. This makes concepts stick in a way abstract examples never do. Quiz mode with spaced repetition. You can run "/quiz-me" and Claude will test you on concepts you've learned. It tracks your understanding score for each tutorial. Then it uses spaced repetition to prioritize the next quiz—concepts you're shaky on come back in 2 days, concepts you've mastered fade to 55+ day intervals. It literally builds retention into the learning process. One central knowledge base across all your projects. Whether you're joining a new company and want to understand their codebase, learning from an open source project, or leveling up on your own vibe-coded project—all your tutorials live in one place (~/coding-tutor-tutorials/). So your personal coding-tutor accompanies you across all your coding adventures. The whole thing is a feedback loop: learn → quiz → retain → learn more → quiz → retain. Your tutorials evolve, your knowledge compounds, and Claude gets better at teaching YOU specifically over time. To install it in Claude Code: • Run /plugin to open the plugin manager • Add marketplace nityeshaga/claude-code-essentials • Enable coding-tutor plugin Here's the Github: And here's 20-mins of me walking you through how to use this plugin and how it works 👇🏽 Let me know if you use it to teach yourself something cool!
21:41

I built a Claude skill that turns Claude Code into your personal coding tutor. The core insight: Claude Opus 4.5 is already the best tutor in the world. Anthropic cooked with this model! It has incredible emotional intelligence and deep coding knowledge. What this skill does is just provide a harness—a way for Claude to agentically build the right context about YOU so it can personalize the tutoring experience in exactly the right way. Here's what makes it work: Learner profile from day one. The first time you use it, Claude interviews you. It asks about your programming background, your goal (where do you want this to take you?), and who you are as a person. This gets saved and informs every single tutorial it ever writes for you. From the very first interaction, everything is 100% personalized. Tutorials that use YOUR code. When you ask to learn something, Claude doesn't give you generic examples from some blog post. It finds examples in the actual codebase you're working in. This makes concepts stick in a way abstract examples never do. Quiz mode with spaced repetition. You can run "/quiz-me" and Claude will test you on concepts you've learned. It tracks your understanding score for each tutorial. Then it uses spaced repetition to prioritize the next quiz—concepts you're shaky on come back in 2 days, concepts you've mastered fade to 55+ day intervals. It literally builds retention into the learning process. One central knowledge base across all your projects. Whether you're joining a new company and want to understand their codebase, learning from an open source project, or leveling up on your own vibe-coded project—all your tutorials live in one place (~/coding-tutor-tutorials/). So your personal coding-tutor accompanies you across all your coding adventures. The whole thing is a feedback loop: learn → quiz → retain → learn more → quiz → retain. Your tutorials evolve, your knowledge compounds, and Claude gets better at teaching YOU specifically over time. To install it in Claude Code: • Run /plugin to open the plugin manager • Add marketplace nityeshaga/claude-code-essentials • Enable coding-tutor plugin Here's the Github: And here's 20-mins of me walking you through how to use this plugin and how it works 👇🏽 Let me know if you use it to teach yourself something cool!

Nityesh

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

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.
3:10

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.

Tristan

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

Hey. This one is for all you early adopters out there! Like I’m sure many of you do, every morning an agent preps me for my day - calendar, news, last 24hrs of Slack - in a morning briefing. But mine lands in my Spotify library, so I can listen to it on my commute. Same app, same experience, same everywhere. Many of us at Spotify have been living with this for a while and find it really useful. So today we're opening it up to see if you do too? Now, your agent of choice can create a Personal Podcast and save it directly to your Spotify library. It's private. It's yours. And it plays everywhere Spotify plays. The use cases feel obvious once you have it: for example a morning briefing built from your calendar and inbox. A deep dive on your class notes before an exam. A travel itinerary narrated for your flight. We've always believed Spotify should be the home for all your audio. Music, podcasts, audiobooks – so why not also the things you make for yourself? Try it out with OpenClaw, Claude Code, or Codex. Install the Save to Spotify CLI from GitHub on desktop and follow the directions. Describe the Personal Podcast you want to hear and ask your agent to save it to Spotify. It will show up in Your Library. Early, rough around some edges, and genuinely exciting. Try it out and let us know what you think? Link in comments 👇
0:24

Hey. This one is for all you early adopters out there! Like I’m sure many of you do, every morning an agent preps me for my day - calendar, news, last 24hrs of Slack - in a morning briefing. But mine lands in my Spotify library, so I can listen to it on my commute. Same app, same experience, same everywhere. Many of us at Spotify have been living with this for a while and find it really useful. So today we're opening it up to see if you do too? Now, your agent of choice can create a Personal Podcast and save it directly to your Spotify library. It's private. It's yours. And it plays everywhere Spotify plays. The use cases feel obvious once you have it: for example a morning briefing built from your calendar and inbox. A deep dive on your class notes before an exam. A travel itinerary narrated for your flight. We've always believed Spotify should be the home for all your audio. Music, podcasts, audiobooks – so why not also the things you make for yourself? Try it out with OpenClaw, Claude Code, or Codex. Install the Save to Spotify CLI from GitHub on desktop and follow the directions. Describe the Personal Podcast you want to hear and ask your agent to save it to Spotify. It will show up in Your Library. Early, rough around some edges, and genuinely exciting. Try it out and let us know what you think? Link in comments 👇

Gustav Söderström

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

Send this to ANYONE on your team using AI agents with Claude/Codex skills: If I were you, I'd put your BEST AI skills in a GitHub repo, turn that repo into a PLUGIN, and have your team INSTALL it in Claude/Codex with auto update on. Why? 1. Everyone gets the same AI SOPs instead of 10 versions floating around Slack 2. When one person improves a skill, the whole team gets the better version. 3. New hires can start with your best workflows instead of a blank AI setup (this is a BIG deal). 4. If someone breaks a skill, you can roll it back with version control. 5. Personal skills can stay personal, while team skills become shared company infrastructure (and an asset!). 6. Your best AI processes stay with the company when someone leaves. 7. You can chain skills together for bigger workflows, like titles -> thumbnails -> descriptions -> YouTube publish. 8. You can track which skills are actually being used and delete the ones collecting dust. 9. You get less slop because the agent has real instructions, examples, taste, and process. 10. Your team moves from single-player AI to multiplayer AI. (thanks to AI with Remy | Learn AI for coming onto The Startup Ideas Podcast (SIP) 🧃) Watch full breakdown here (clearly explained): I don't know why I didn't do this before. The more I think about it, the more obvious it feels: your AI workflows should be version controlled company assets. It kinda feels like the difference between “we use AI” and “we actually operate with AI". Enjoy.
32:26

Send this to ANYONE on your team using AI agents with Claude/Codex skills: If I were you, I'd put your BEST AI skills in a GitHub repo, turn that repo into a PLUGIN, and have your team INSTALL it in Claude/Codex with auto update on. Why? 1. Everyone gets the same AI SOPs instead of 10 versions floating around Slack 2. When one person improves a skill, the whole team gets the better version. 3. New hires can start with your best workflows instead of a blank AI setup (this is a BIG deal). 4. If someone breaks a skill, you can roll it back with version control. 5. Personal skills can stay personal, while team skills become shared company infrastructure (and an asset!). 6. Your best AI processes stay with the company when someone leaves. 7. You can chain skills together for bigger workflows, like titles -> thumbnails -> descriptions -> YouTube publish. 8. You can track which skills are actually being used and delete the ones collecting dust. 9. You get less slop because the agent has real instructions, examples, taste, and process. 10. Your team moves from single-player AI to multiplayer AI. (thanks to AI with Remy | Learn AI for coming onto The Startup Ideas Podcast (SIP) 🧃) Watch full breakdown here (clearly explained): I don't know why I didn't do this before. The more I think about it, the more obvious it feels: your AI workflows should be version controlled company assets. It kinda feels like the difference between “we use AI” and “we actually operate with AI". Enjoy.

GREG ISENBERG

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

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇
0:25

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇

Mr. Buzzoni

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

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.
0:51

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

🐆 Rapid-MLX v0.12 is here. We’ve officially evolved from a simple chat app into a full-fledged, on-device AI studio for Apple Silicon! 🖥️✨ We didn't just push the MLX inference engine to its limits and expand support for a massive lineup of local open-source models—we are alpha-launching the highly anticipated Desktop Version. (A huge shoutout to the IoTeX community for grinding through the closed beta with us. Your feedback was incredible and helped shape this beast.) Here are the game-changing features you can run on your Mac right now, 100% free and 100% offline 👇 🚀 Blazing Fast Local LLMs Run anything from 4B up to Qwen3.5-122B completely offline. No guessing games—we recommend models matched perfectly to your Mac's actual RAM. Rich chat includes syntax highlighting, markdown tables, and honest tok/s metrics. 🎨 Local Image Generation A brand new Images tab to render directly on your machine. Pick a model (FLUX.2-klein, Z-Image-Turbo), prompt, and refine. Everything lands in a visual filmstrip. 👁️ Vision & Live Web Tools Attach an image and chat about it with local vision. Need real-time data? Our built-in web tools (weather, search, page-fetch) run mid-answer with strict, transparent privacy controls. 🤖 Plug-and-Play Coding Agents Wire up Claude Code, Codex, Cline, or Continue in seconds. One copy-paste from the Launch tab spins up a local OpenAI/Anthropic-compatible endpoint. 🔒 Private by Design Everything runs on-device. Signed, notarized, and entirely local. Your data stays yours. Turn your Mac into an AI powerhouse today. ⚡️
0:37

🐆 Rapid-MLX v0.12 is here. We’ve officially evolved from a simple chat app into a full-fledged, on-device AI studio for Apple Silicon! 🖥️✨ We didn't just push the MLX inference engine to its limits and expand support for a massive lineup of local open-source models—we are alpha-launching the highly anticipated Desktop Version. (A huge shoutout to the IoTeX community for grinding through the closed beta with us. Your feedback was incredible and helped shape this beast.) Here are the game-changing features you can run on your Mac right now, 100% free and 100% offline 👇 🚀 Blazing Fast Local LLMs Run anything from 4B up to Qwen3.5-122B completely offline. No guessing games—we recommend models matched perfectly to your Mac's actual RAM. Rich chat includes syntax highlighting, markdown tables, and honest tok/s metrics. 🎨 Local Image Generation A brand new Images tab to render directly on your machine. Pick a model (FLUX.2-klein, Z-Image-Turbo), prompt, and refine. Everything lands in a visual filmstrip. 👁️ Vision & Live Web Tools Attach an image and chat about it with local vision. Need real-time data? Our built-in web tools (weather, search, page-fetch) run mid-answer with strict, transparent privacy controls. 🤖 Plug-and-Play Coding Agents Wire up Claude Code, Codex, Cline, or Continue in seconds. One copy-paste from the Launch tab spins up a local OpenAI/Anthropic-compatible endpoint. 🔒 Private by Design Everything runs on-device. Signed, notarized, and entirely local. Your data stays yours. Turn your Mac into an AI powerhouse today. ⚡️

raullen

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