Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Say hello to agentOS (beta) A portable open-source OS built just for agents. Powered by WASM & V8 isolates. 🔗 Embedded in your backend ⚡ ~6ms coldstarts, 32x cheaper than sbxs 📁 Mount anything as a file system (S3, SQLite, …) 🥧 Use Pi, Claude Code/Codex/Amp/OpenCode soon

rivet_dev's profile picture

Rivet

4,464 subscribers

267,678 görüntüleme • 3 ay önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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!

Superdaddy

43,285 görüntüleme • 4 ay önce

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.
10:52

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

Tal Raviv

57,910 görüntüleme • 6 ay önce

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.
1:54

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

Steve (Builder.io)

25,187 görüntüleme • 21 gün önce

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:
0:54

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

Jerry Liu

21,073 görüntüleme • 5 ay önce

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:
1:48

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:

Andrew Ng

81,696 görüntüleme • 10 ay önce

We analyzed Anthropic’s memory architecture and built something better: a persistent, human-inspectable, and token-efficient memory layer that scales with your projects. Today, it’s OPEN-SOURCE. ByteRover CLI gives agents (like OpenClaw, Claude Code, and Hermes) persistent, structured memory. Built on the exact architecture that became the #1 memory system for OpenClaw (30,000+ downloads in a week), it lets developers curate project knowledge into a file-based hierarchy. This guarantees highly accurate, lightning-fast retrieval, even with lightweight models. 👉Highly Accurate: >92% retrieval accuracy across long-running sessions - the highest proven production accuracy on the market. ⚡Fast: ~1.6s average retrieval time. 💰Economic: Maintains >90% accuracy even with lightweight models, saving 50-70% on token costs. ☁ Portable: Runs locally by default, with cloud-sync to share memory across agents and teammates.
1:19

We analyzed Anthropic’s memory architecture and built something better: a persistent, human-inspectable, and token-efficient memory layer that scales with your projects. Today, it’s OPEN-SOURCE. ByteRover CLI gives agents (like OpenClaw, Claude Code, and Hermes) persistent, structured memory. Built on the exact architecture that became the #1 memory system for OpenClaw (30,000+ downloads in a week), it lets developers curate project knowledge into a file-based hierarchy. This guarantees highly accurate, lightning-fast retrieval, even with lightweight models. 👉Highly Accurate: >92% retrieval accuracy across long-running sessions - the highest proven production accuracy on the market. ⚡Fast: ~1.6s average retrieval time. 💰Economic: Maintains >90% accuracy even with lightweight models, saving 50-70% on token costs. ☁ Portable: Runs locally by default, with cloud-sync to share memory across agents and teammates.

andy nguyen

28,980 görüntüleme • 3 ay önce

Introducing SuperDesign.Dev The first open-source Design Agent that lives inside Cursor, Windsurf, or any IDE: 👉 Instantly spin up 10 different design in parallel 👉 Explore, fork, and iterate 10x faster 👉 Create new or iterate on your existing UI — all fully local JackJack and I shipped this as a quick weekend experiment to validate a hunch: design is the killer use case for parallel agents. Currently at V0.005 — a simple customization of the Claude Code SDK + static HTML generation. (We might be the first product powered by the Anthropic Claude Code SDK!) More coming soon: web app, mobile app, SVG generation, and more. GitHub: Try it out: ----- Upvote on Hacker News ❤️:
0:55

Introducing SuperDesign.Dev The first open-source Design Agent that lives inside Cursor, Windsurf, or any IDE: 👉 Instantly spin up 10 different design in parallel 👉 Explore, fork, and iterate 10x faster 👉 Create new or iterate on your existing UI — all fully local JackJack and I shipped this as a quick weekend experiment to validate a hunch: design is the killer use case for parallel agents. Currently at V0.005 — a simple customization of the Claude Code SDK + static HTML generation. (We might be the first product powered by the Anthropic Claude Code SDK!) More coming soon: web app, mobile app, SVG generation, and more. GitHub: Try it out: ----- Upvote on Hacker News ❤️:

Jason Zhou

49,435 görüntüleme • 1 yıl önce

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

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

Steve (Builder.io)

42,501 görüntüleme • 27 gün önce

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us. Clips is made to be customized. The built-in agent can customize its own code, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the replies.
0:35

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us. Clips is made to be customized. The built-in agent can customize its own code, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the replies.

Steve (Builder.io)

229,309 görüntüleme • 28 gün önce

💥 The Future Is Now: Pay Your Bills with Pi Using PrimePi Pay 💥 Powered by Pi. Built for the People. In a world racing toward decentralization and digital empowerment, one question still echoes for everyday people: When will crypto solve real problems? That time is now — and the answer is Pi Network. Introducing a revolutionary leap in the Pi ecosystem: a bold new app that finally lets you pay your real-world bills using Pi Coin (𝛑) — securely, instantly, and without relying on banks or middlemen. Welcome to PrimePi Pay — the bridge between blockchain freedom and the real-world responsibilities we all carry. 🔑 Why PrimePi Pay Matters Too many people are still stuck in a financial system that limits access, adds fees, and delays payments. Meanwhile, millions of Pioneers around the world have been quietly building a new financial layer — one mined on trust, time, and vision. Now it’s time to activate that vision. With PrimePi Pay, you’ll be able to: •Pay electricity, phone, internet, rent, and more using Pi •Scan bills and verify payment details with built-in AI tools •Send Pi directly to official businesses or trusted local agents •Track every payment inside your Pi wallet — fully transparent and secure ⚡ Real Utility. Real Adoption. Real Pi. This isn’t about hype. It’s about empowerment. You don’t need to convert to fiat. You don’t need to wait on banks. You don’t need permission. All you need is your Pi — and now, it can take care of your life’s most essential needs. PrimePi Pay is proudly powered by Pi — the people’s digital currency. 🧠 Powered by GenAI. Built by Pioneers. Using GenAI and Pi-native tools like Pi App Studio and Firebase, PrimePi Pay was created by Pioneers, for Pioneers. It’s simple. It’s powerful. And it’s laser-focused on solving real-world financial problems. It’s more than an app — it’s a global movement. You can even participate as a Prime Agent, helping users in your community pay bills while building a reputation inside the Pi economy. 🚀 PrimePi Pay: Just the Beginning As Pi Network continues its Open Mainnet expansion, PrimePi Pay will unlock: •Partnerships with major billers and utility companies •Mobile top-ups and rent payments in emerging markets •Local-to-global remittances, powered by trust and decentralization And guess what? It all starts with you. Your Pi. Your bills. Your power. 💬 Final Word: “One day, you’ll stop asking what Pi is worth. Instead, you’ll ask what you can do with it.” – A Pioneer of the New Economy Let’s make history. Let’s pay bills with PrimePi Pay. Powered by Pi. Designed for a new world. 💜🔌📲 #PrimePiPay #PoweredByPi #PiNetwork #PayWithPi #DecentralizeLife Pi Network Nicolas Kokkalis Chengdiao Fan
1:59

💥 The Future Is Now: Pay Your Bills with Pi Using PrimePi Pay 💥 Powered by Pi. Built for the People. In a world racing toward decentralization and digital empowerment, one question still echoes for everyday people: When will crypto solve real problems? That time is now — and the answer is Pi Network. Introducing a revolutionary leap in the Pi ecosystem: a bold new app that finally lets you pay your real-world bills using Pi Coin (𝛑) — securely, instantly, and without relying on banks or middlemen. Welcome to PrimePi Pay — the bridge between blockchain freedom and the real-world responsibilities we all carry. 🔑 Why PrimePi Pay Matters Too many people are still stuck in a financial system that limits access, adds fees, and delays payments. Meanwhile, millions of Pioneers around the world have been quietly building a new financial layer — one mined on trust, time, and vision. Now it’s time to activate that vision. With PrimePi Pay, you’ll be able to: •Pay electricity, phone, internet, rent, and more using Pi •Scan bills and verify payment details with built-in AI tools •Send Pi directly to official businesses or trusted local agents •Track every payment inside your Pi wallet — fully transparent and secure ⚡ Real Utility. Real Adoption. Real Pi. This isn’t about hype. It’s about empowerment. You don’t need to convert to fiat. You don’t need to wait on banks. You don’t need permission. All you need is your Pi — and now, it can take care of your life’s most essential needs. PrimePi Pay is proudly powered by Pi — the people’s digital currency. 🧠 Powered by GenAI. Built by Pioneers. Using GenAI and Pi-native tools like Pi App Studio and Firebase, PrimePi Pay was created by Pioneers, for Pioneers. It’s simple. It’s powerful. And it’s laser-focused on solving real-world financial problems. It’s more than an app — it’s a global movement. You can even participate as a Prime Agent, helping users in your community pay bills while building a reputation inside the Pi economy. 🚀 PrimePi Pay: Just the Beginning As Pi Network continues its Open Mainnet expansion, PrimePi Pay will unlock: •Partnerships with major billers and utility companies •Mobile top-ups and rent payments in emerging markets •Local-to-global remittances, powered by trust and decentralization And guess what? It all starts with you. Your Pi. Your bills. Your power. 💬 Final Word: “One day, you’ll stop asking what Pi is worth. Instead, you’ll ask what you can do with it.” – A Pioneer of the New Economy Let’s make history. Let’s pay bills with PrimePi Pay. Powered by Pi. Designed for a new world. 💜🔌📲 #PrimePiPay #PoweredByPi #PiNetwork #PayWithPi #DecentralizeLife Pi Network Nicolas Kokkalis Chengdiao Fan

Mr Spock 𝛑

15,731 görüntüleme • 1 yıl önce

Today we are launching Openwork is now Accomplish, an open-source (MIT-licensed) computer-use agent that’s fast, cheap, and more secure. Openwork is now Accomplish is the result of a short two-day hackathon our team decided to hack, which brings together some of our favorite open source AI modules into one powerful agent, to allow you to: 1. Bring your own model/API key (any provider and model supported by OpenCode is supported by Openwork) 2. ~4x faster than Claude for Chrome/Cowork, and much more token-efficient, powered by dev-browser by Sawyer Hood (legend) 3. More secure - contrary to Claude for Chrom/Cowork, does not leverage the main browser instance where you are logged into all services already. You login only to the services you need. This significantly reduces the risk of data loss in case of prompt injections, to which computer-use agents are highly exposed. 4. Free and 100% open-source! You can download the DMG (macOS only for now) or fork the github repo via the link in bio (Openwork is now Accomplish). Let us know what you think (or better, send a pull request)!
1:23

Today we are launching Openwork is now Accomplish, an open-source (MIT-licensed) computer-use agent that’s fast, cheap, and more secure. Openwork is now Accomplish is the result of a short two-day hackathon our team decided to hack, which brings together some of our favorite open source AI modules into one powerful agent, to allow you to: 1. Bring your own model/API key (any provider and model supported by OpenCode is supported by Openwork) 2. ~4x faster than Claude for Chrome/Cowork, and much more token-efficient, powered by dev-browser by Sawyer Hood (legend) 3. More secure - contrary to Claude for Chrom/Cowork, does not leverage the main browser instance where you are logged into all services already. You login only to the services you need. This significantly reduces the risk of data loss in case of prompt injections, to which computer-use agents are highly exposed. 4. Free and 100% open-source! You can download the DMG (macOS only for now) or fork the github repo via the link in bio (Openwork is now Accomplish). Let us know what you think (or better, send a pull request)!

Or Hiltch

1,002,014 görüntüleme • 6 ay önce

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

55,345 görüntüleme • 1 ay önce

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

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

Yarchi

810,381 görüntüleme • 1 ay önce

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16
41:15

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16

Dan Shipper 📧

25,406 görüntüleme • 19 gün önce

Say hello to text-to-cad, an open source tool for generating 3D models in Codex! Prompt and edit complex 3D models. Export STEP, STL, GLB, DXF and URDF files. Built for CAD newbies. Link to github below. CAD is hard. As a software engineer getting back into robotics, I’ve been humbled by new tools like Onshape. Struggling to kick old habits, I started prompting Codex to generate 3D models and had some limited succes. After a few iterations I found a recipe that actually works: 1. Generate a python script for every STEP file. The agent can easily edit each part’s source without touching the raw STEP file. Use build123d > cadquery. 2. Reference specific faces and edges in prompts for precise edits. I built a basic local ui to inspect / cache STEP B-reps to make this easier. 3. Maintain markdown explaining important part features in plain English so the model can index on project context quickly. 4. Verify results with screenshots and geometry. Models don’t have great spatial awareness, but they can interpret images and verify constraints very well. For the best results I’ve been using GPT 5.4 xhigh / Opus 4.6+. Fair warning, this will burn through tokens, I recommend the Pro/Max plans if you’re planning on building anything serious. PRs welcome!
0:24

Say hello to text-to-cad, an open source tool for generating 3D models in Codex! Prompt and edit complex 3D models. Export STEP, STL, GLB, DXF and URDF files. Built for CAD newbies. Link to github below. CAD is hard. As a software engineer getting back into robotics, I’ve been humbled by new tools like Onshape. Struggling to kick old habits, I started prompting Codex to generate 3D models and had some limited succes. After a few iterations I found a recipe that actually works: 1. Generate a python script for every STEP file. The agent can easily edit each part’s source without touching the raw STEP file. Use build123d > cadquery. 2. Reference specific faces and edges in prompts for precise edits. I built a basic local ui to inspect / cache STEP B-reps to make this easier. 3. Maintain markdown explaining important part features in plain English so the model can index on project context quickly. 4. Verify results with screenshots and geometry. Models don’t have great spatial awareness, but they can interpret images and verify constraints very well. For the best results I’ve been using GPT 5.4 xhigh / Opus 4.6+. Fair warning, this will burn through tokens, I recommend the Pro/Max plans if you’re planning on building anything serious. PRs welcome!

Jake Fitzgerald

52,444 görüntüleme • 2 ay önce

🚨BREAKING: Someone just built the open source Loom killer that turns your screen recordings into AI agents. It's called Bloom and it does something Loom never could. Your recordings don't just sit as files. They become queryable, searchable, agent-ready data the moment you stop recording. Here's what actually happens: You hit record. Bloom captures your screen, mic, and system audio locally. While you're still recording, it uploads chunks to the cloud in real time. The second you stop, it auto-generates a full transcript, creates visual embeddings, and indexes every spoken word. Then the wild part kicks in. You can query your recordings through APIs. You can hook Claude Code directly into your video library and ask it questions. Your screen recording just became a knowledge base. → Local-first, your files never get locked in → Cmd+Shift+R starts and stops from anywhere on your system → One-click shareable link for any recording → Chat directly with your video content through VideoDB Chat → Works with Claude Code and other agent frameworks out of the box Recordings are no longer files. They're inputs for AI. MIT License. 100% Opensource. Link in comments.
1:13

🚨BREAKING: Someone just built the open source Loom killer that turns your screen recordings into AI agents. It's called Bloom and it does something Loom never could. Your recordings don't just sit as files. They become queryable, searchable, agent-ready data the moment you stop recording. Here's what actually happens: You hit record. Bloom captures your screen, mic, and system audio locally. While you're still recording, it uploads chunks to the cloud in real time. The second you stop, it auto-generates a full transcript, creates visual embeddings, and indexes every spoken word. Then the wild part kicks in. You can query your recordings through APIs. You can hook Claude Code directly into your video library and ask it questions. Your screen recording just became a knowledge base. → Local-first, your files never get locked in → Cmd+Shift+R starts and stops from anywhere on your system → One-click shareable link for any recording → Chat directly with your video content through VideoDB Chat → Works with Claude Code and other agent frameworks out of the box Recordings are no longer files. They're inputs for AI. MIT License. 100% Opensource. Link in comments.

Rimsha Bhardwaj

128,583 görüntüleme • 3 ay önce

Here's a fresh demo I made for Zo Computer - Zo is OpenClaw, without the setup - But it's more than that: it's a Personal Cloud - You can chat with any kind of file in your Zo - You can scheduled tasks for your AI - I made a task that checks what I'm playing on Spotify every minute, finds the corresponding YouTube video, and adds the track to a SQLite database on my Zo - My personal website (hosted on my Zo) displays those tracks - You can text or email Zo. I made this website just by texting Zo! - Tons of built-in integrations, or you can just ask Zo to integrate anything - There's a built-in browser, which Zo can use - We snapshot your computer all the time, so you can rollback to any point in the past - The hardware is elastic, so you can scale up as needed Thank you 金子晋輔 Shinsuke Kaneko 🐘 + Yusuke Endo for inspiring the video after our conversation today. Excited to bring Zo to Japan! 🗾
5:27

Here's a fresh demo I made for Zo Computer - Zo is OpenClaw, without the setup - But it's more than that: it's a Personal Cloud - You can chat with any kind of file in your Zo - You can scheduled tasks for your AI - I made a task that checks what I'm playing on Spotify every minute, finds the corresponding YouTube video, and adds the track to a SQLite database on my Zo - My personal website (hosted on my Zo) displays those tracks - You can text or email Zo. I made this website just by texting Zo! - Tons of built-in integrations, or you can just ask Zo to integrate anything - There's a built-in browser, which Zo can use - We snapshot your computer all the time, so you can rollback to any point in the past - The hardware is elastic, so you can scale up as needed Thank you 金子晋輔 Shinsuke Kaneko 🐘 + Yusuke Endo for inspiring the video after our conversation today. Excited to bring Zo to Japan! 🗾

ben guo 🏇

297,476 görüntüleme • 3 ay önce

ClawTeam v0.2.0 is here. One CLI to coordinate any coding agent — Claude Code, Codex, OpenClaw, nanobot, and more — into a self‑organizing swarm that plans, builds, and ships together. What's new in v0.2.0: 1) - Gource Visualization — Watch your agent swarm’s Git activity in real time. Clear. Visual. Instant. Run: clawteam board gource --live See every commit, branch, and merge as it happens. Track what each agent is doing. 2) - Runtime Profiles — A provider‑aware configuration system. Switch between Claude, Kimi, and Gemini anytime. No need to edit environment variables. Run clawteam profile wizard. Follow the interactive setup. Done in minutes. 3) - Git-Based Context — Full worktree isolation with built‑in conflict detection and change tracking. Each agent works on its own branch, and the leader can see everything clearly in one place. 4) - Stability & Hardening — Spawn/workspace conflict fixes, improved tmux integration, message normalization, P2P liveness with lease-based detection. This release is about making the foundation rock-solid. --------------------------------------------------------- To show what a coordinated agent swarm can actually do, we ran 1 Claude Code orchestrating 8 Claude Code agents to build a robotics simulation system optimized for Apple Silicon — from scratch. 8 hours. 300+ PRs. One running simulator. Check the result: --------------------------------------------------------- Huge thanks to the open-source community for the feedback, issues, and PRs that shaped this release. ClawTeam is built in the open because we believe multi-agent coordination should be a shared primitive, not a proprietary moat. Try it: pip install clawteam Docs: GitHub: #ClawTeam #nanobot #AIAgents #openclaw #ClaudeCode #Cursor
1:23

ClawTeam v0.2.0 is here. One CLI to coordinate any coding agent — Claude Code, Codex, OpenClaw, nanobot, and more — into a self‑organizing swarm that plans, builds, and ships together. What's new in v0.2.0: 1) - Gource Visualization — Watch your agent swarm’s Git activity in real time. Clear. Visual. Instant. Run: clawteam board gource --live See every commit, branch, and merge as it happens. Track what each agent is doing. 2) - Runtime Profiles — A provider‑aware configuration system. Switch between Claude, Kimi, and Gemini anytime. No need to edit environment variables. Run clawteam profile wizard. Follow the interactive setup. Done in minutes. 3) - Git-Based Context — Full worktree isolation with built‑in conflict detection and change tracking. Each agent works on its own branch, and the leader can see everything clearly in one place. 4) - Stability & Hardening — Spawn/workspace conflict fixes, improved tmux integration, message normalization, P2P liveness with lease-based detection. This release is about making the foundation rock-solid. --------------------------------------------------------- To show what a coordinated agent swarm can actually do, we ran 1 Claude Code orchestrating 8 Claude Code agents to build a robotics simulation system optimized for Apple Silicon — from scratch. 8 hours. 300+ PRs. One running simulator. Check the result: --------------------------------------------------------- Huge thanks to the open-source community for the feedback, issues, and PRs that shaped this release. ClawTeam is built in the open because we believe multi-agent coordination should be a shared primitive, not a proprietary moat. Try it: pip install clawteam Docs: GitHub: #ClawTeam #nanobot #AIAgents #openclaw #ClaudeCode #Cursor

Chao Huang

25,101 görüntüleme • 3 ay önce

I just built an AI-powered creative search engine with Gemini Embedding 2 + Claude Code 🤯 Drop in your UGC clips, product shots, and ad variations — then search through everything in plain English. "Show me all the unboxing clips." "Find product shots with natural lighting." "Which creator talked about sensitive skin?" All inside Claude Code. Perfect for DTC brands and agencies sitting on hundreds of creative files they can never find when they actually need them. If you're digging through a folder of random file names, scrubbing through raw footage to find that one clip, and relying on memory to track down what's already been shot... This system eliminates the entire loop: → Drop your videos, images, and docs into a project folder → One prompt to Claude Code — it builds the entire search app for you → Google's new Gemini Embedding 2 model actually watches your videos and looks at your images → It understands what's inside each file — not just the file name → Search in plain English and get back the actual assets with confidence scores No scrolling through folders. No relying on file names to find anything. No re-shooting footage you already have. What you get: → A searchable library of every creative asset your brand has ever produced → Natural language search across video, images, and documents at the same time → Results that show the actual files inline — play videos, view images, read docs → A system that gets smarter every time you add richer descriptions to your assets One free API key. No monthly subscriptions. Runs on your machine. I put together a full playbook with the exact build prompt, the setup process, and DTC/agency use cases to get this running in under 30 minutes. Want the full playbook? > Like this post > Comment "SEARCH" And I'll send it over (must be following so I can DM)
0:22

I just built an AI-powered creative search engine with Gemini Embedding 2 + Claude Code 🤯 Drop in your UGC clips, product shots, and ad variations — then search through everything in plain English. "Show me all the unboxing clips." "Find product shots with natural lighting." "Which creator talked about sensitive skin?" All inside Claude Code. Perfect for DTC brands and agencies sitting on hundreds of creative files they can never find when they actually need them. If you're digging through a folder of random file names, scrubbing through raw footage to find that one clip, and relying on memory to track down what's already been shot... This system eliminates the entire loop: → Drop your videos, images, and docs into a project folder → One prompt to Claude Code — it builds the entire search app for you → Google's new Gemini Embedding 2 model actually watches your videos and looks at your images → It understands what's inside each file — not just the file name → Search in plain English and get back the actual assets with confidence scores No scrolling through folders. No relying on file names to find anything. No re-shooting footage you already have. What you get: → A searchable library of every creative asset your brand has ever produced → Natural language search across video, images, and documents at the same time → Results that show the actual files inline — play videos, view images, read docs → A system that gets smarter every time you add richer descriptions to your assets One free API key. No monthly subscriptions. Runs on your machine. I put together a full playbook with the exact build prompt, the setup process, and DTC/agency use cases to get this running in under 30 minutes. Want the full playbook? > Like this post > Comment "SEARCH" And I'll send it over (must be following so I can DM)

Mike Futia

12,239 görüntüleme • 4 ay önce

SOMEONE JUST BUILT AN OPERATING SYSTEM FOR ROBOTS not a framework... not a library an actual OS dimos is an open-source platform that lets you build, run, and deploy software on any robot humanoids, quadrupeds, drones, wheeled bots you write python modules .... they talk to each other via typed streams...just like microservices, but for physical hardware the wild part..? you can give your AI editor (cursor, claude code) MCP access to send real physical commands "move forward 1 meter" → robot moves. it ships with a full navigation stack SLAM, collision avoidance, route planning. plus a dashboard to debug, visualize, and control your robot in real-time via waypoints, VR, or keyboard. supported hardware already includes unitree G1 humanoids, dji drones, and multiple robot arms. programming physical robots is finally as simple as programming software
3:35

SOMEONE JUST BUILT AN OPERATING SYSTEM FOR ROBOTS not a framework... not a library an actual OS dimos is an open-source platform that lets you build, run, and deploy software on any robot humanoids, quadrupeds, drones, wheeled bots you write python modules .... they talk to each other via typed streams...just like microservices, but for physical hardware the wild part..? you can give your AI editor (cursor, claude code) MCP access to send real physical commands "move forward 1 meter" → robot moves. it ships with a full navigation stack SLAM, collision avoidance, route planning. plus a dashboard to debug, visualize, and control your robot in real-time via waypoints, VR, or keyboard. supported hardware already includes unitree G1 humanoids, dji drones, and multiple robot arms. programming physical robots is finally as simple as programming software

Vaishnavi

19,745 görüntüleme • 3 ay önce