正在加载视频...

视频加载失败

返回首页

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted...

Palanikannan_M's profile picture

Palani — oss/acc

1,183 subscribers

13,971 次观看 • 2 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

We can run DeepSeek for free in OpenCode now. Two things I didn't expect from VPR: DeepSeek ran free in OpenCode, Codex, Claude Code and everything else got cheaper without me changing anything. calls it a VPN for AI, which is close enough. You download it, it opens one local address, and you point whatever tool you already use at that address. Claude Code, Codex, OpenCode. They don't need to know anything changed. What's behind that address is an open market of 610+ models across 158+ providers, bidding. So the same model just costs less. MiniMax M3 is running 69% under list right now. Qwen3.7 Plus 64%. Claude Fable 5 at $6 instead of $10. No account. No email. No API key. You install it and start. Links below
1:05

We can run DeepSeek for free in OpenCode now. Two things I didn't expect from VPR: DeepSeek ran free in OpenCode, Codex, Claude Code and everything else got cheaper without me changing anything. calls it a VPN for AI, which is close enough. You download it, it opens one local address, and you point whatever tool you already use at that address. Claude Code, Codex, OpenCode. They don't need to know anything changed. What's behind that address is an open market of 610+ models across 158+ providers, bidding. So the same model just costs less. MiniMax M3 is running 69% under list right now. Qwen3.7 Plus 64%. Claude Fable 5 at $6 instead of $10. No account. No email. No API key. You install it and start. Links below

Ziwen

18,667 次观看 • 1 个月前

I love working in terminal, but I can't design or brainstorm in there. So I built Hatch! One IDE for the full loop: explore ideas → test out designs with SuperDesign.Dev → find right skills for the job → ship with agents. > build: supports Claude code, OpenCode and Cursor agents in parallel with worktrees. > idea maze: use the canvas to sketch out ideas, paste tweets or images. > idea maze: let your agent make connections, critique your ideas or come up with related ones. > design: bring SuperDesign.Dev prompts or exports directly into your workspaces. vibedesign before vibecoding. > skills: ask your agent what skills to get with your workspace context. All open source!
0:24

I love working in terminal, but I can't design or brainstorm in there. So I built Hatch! One IDE for the full loop: explore ideas → test out designs with SuperDesign.Dev → find right skills for the job → ship with agents. > build: supports Claude code, OpenCode and Cursor agents in parallel with worktrees. > idea maze: use the canvas to sketch out ideas, paste tweets or images. > idea maze: let your agent make connections, critique your ideas or come up with related ones. > design: bring SuperDesign.Dev prompts or exports directly into your workspaces. vibedesign before vibecoding. > skills: ask your agent what skills to get with your workspace context. All open source!

Firat Sertgoz

38,578 次观看 • 7 个月前

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

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

Yusuf

220,215 次观看 • 3 个月前

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.
0:29

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.

BuBBliK

15,573 次观看 • 2 个月前

We built Openwork! I found Claude Cowork to be too expensive So i asked Claude Code to build me a better version with Composio tool router It can: - access local files and your terminal via claude code - connect and use 500+ apps like gmail, outlook, slack on demand - chain actions across local files and cloud apps in one flow In the demo we use it to scan through my laptop and find all my unfinished projects and put them in a notion database with completion status. excited to see more usecases link:
1:09

We built Openwork! I found Claude Cowork to be too expensive So i asked Claude Code to build me a better version with Composio tool router It can: - access local files and your terminal via claude code - connect and use 500+ apps like gmail, outlook, slack on demand - chain actions across local files and cloud apps in one flow In the demo we use it to scan through my laptop and find all my unfinished projects and put them in a notion database with completion status. excited to see more usecases link:

Karan Vaidya

241,615 次观看 • 7 个月前

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 次观看 • 5 个月前

Here it is: AI can now use all of your iPhone and iPad. All of it. Without limitation or exception. Yes, really. You’re watching a GPT-6 Astra OpenClaw agent, spoken to via VoiceClaw Realtime on my iPhone, controlling my iPad by using my soon-to-be-released macOS app for full AI control of your iPhone or iPad. Yes, really. With this forthcoming macOS app from me, it will no longer matter if your iPhone/iPad apps are built for Siri, or have AI capabilities of their own. With this one app, OpenClaw, Codex, Hermes, or Claude Code AI agents can control your iPhone or iPad in every way you can. Without limitation. Everything you can do on your phone, it can do. Everything. No physical proximity, cable, bluetooth or shared-wifi-network connection between the macOS computer and your iPhone/iPad is needed. Translation: you no longer need Siri. Ever. At all. Coming soon. P.S.: I have one question: What would you pay for a one-year license for this app, or for a lifetime license?
1:23

Here it is: AI can now use all of your iPhone and iPad. All of it. Without limitation or exception. Yes, really. You’re watching a GPT-6 Astra OpenClaw agent, spoken to via VoiceClaw Realtime on my iPhone, controlling my iPad by using my soon-to-be-released macOS app for full AI control of your iPhone or iPad. Yes, really. With this forthcoming macOS app from me, it will no longer matter if your iPhone/iPad apps are built for Siri, or have AI capabilities of their own. With this one app, OpenClaw, Codex, Hermes, or Claude Code AI agents can control your iPhone or iPad in every way you can. Without limitation. Everything you can do on your phone, it can do. Everything. No physical proximity, cable, bluetooth or shared-wifi-network connection between the macOS computer and your iPhone/iPad is needed. Translation: you no longer need Siri. Ever. At all. Coming soon. P.S.: I have one question: What would you pay for a one-year license for this app, or for a lifetime license?

Ben Badejo

25,139 次观看 • 2 天前

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.
0:21

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.

BridgeMind

47,243 次观看 • 4 个月前

HERMES AGENT CAN SHARE MEMORY WITH CODEX AND CLAUDE CODE THROUGH HINDSIGHT. ONE MEMORY BANK. ONE AGENT REMEMBERS, EVERY OTHER AGENT KNOWS. the problem: you use Hermes for orchestration. Codex for coding. Claude Code for debugging. each has its own memory. switch between them and you explain the same project three times. Hindsight fixes this. one shared memory bank that every agent reads and writes to. tell Codex: "the test color for this project is purple." switch to Hermes. ask: "what test color did I pick?" Hermes answers: "purple." no copy-paste. no re-explaining. instant recall. HOW IT WORKS: Hindsight runs as a Docker container on your machine. self-hosted. your data stays local. an LLM powers the memory processing (retain, recall, reflect). RETAIN: extracts facts from your conversations. entities, decisions, preferences, project context. saved to the memory bank automatically. RECALL: when you ask a question, Hindsight pulls from semantic search, keywords, graph connections, and temporal data. fused into one answer. REFLECT: deeper reasoning layer. connects memories across sessions. identifies patterns in your work. produces observations that get smarter over time. CONNECT TO HERMES: Desktop app: Settings → Memory and Context → switch provider from Namosin to Hindsight. set API URL to your local Docker container. set bank ID. done. CLI: hermes memory setup → select Hindsight. verify: hermes memory status should show: provider: hindsight, installed, available. CONNECT TO CODEX: npx hindsight-coding-agents install codex \ --self-hosted --server this installs lifecycle hooks: initialize memory on session start. recall context during work. retain the session when done. enable hooks in Codex: Settings → Hooks → trust all three. CONNECT TO CLAUDE CODE (same command): npx hindsight-coding-agents install all "all" connects every detected agent on your machine. Claude Code, Codex, Cursor, and others. one command. every agent shares the same bank. TAGS FOR FILTERING: every memory gets tagged by harness (Hermes, Codex, Claude Code) and optionally by project name. in the Hindsight control plane: filter by harness. see only Hermes memories. or only Codex memories. or search across everything. soft partitions inside one bank. not hard walls. cross-reference when you need to. ONE BANK OR MANY: one global bank: solo dev, related projects. all agents share everything. patterns emerge across projects. per-project banks: unrelated codebases. each project gets its own memory. no cross-contamination. your call. start with one. split when projects diverge. KNOWLEDGE PAGES (v0.9.0): Hindsight auto-generates living summaries from your accumulated memories. components, concepts, conventions, decisions. not static docs. projected from real agent conversations. auto-refresh as new memories land. WHAT TO KNOW: self-hosted via Docker. your data never leaves your machine. backup system built in (admin CLI + scheduled exports). works with any LLM (local Ollama, OpenAI, Codex subscription). memory defense: redact or block sensitive content automatically. 33,000+ memories accumulated in ~10 days of normal use.
34:12

HERMES AGENT CAN SHARE MEMORY WITH CODEX AND CLAUDE CODE THROUGH HINDSIGHT. ONE MEMORY BANK. ONE AGENT REMEMBERS, EVERY OTHER AGENT KNOWS. the problem: you use Hermes for orchestration. Codex for coding. Claude Code for debugging. each has its own memory. switch between them and you explain the same project three times. Hindsight fixes this. one shared memory bank that every agent reads and writes to. tell Codex: "the test color for this project is purple." switch to Hermes. ask: "what test color did I pick?" Hermes answers: "purple." no copy-paste. no re-explaining. instant recall. HOW IT WORKS: Hindsight runs as a Docker container on your machine. self-hosted. your data stays local. an LLM powers the memory processing (retain, recall, reflect). RETAIN: extracts facts from your conversations. entities, decisions, preferences, project context. saved to the memory bank automatically. RECALL: when you ask a question, Hindsight pulls from semantic search, keywords, graph connections, and temporal data. fused into one answer. REFLECT: deeper reasoning layer. connects memories across sessions. identifies patterns in your work. produces observations that get smarter over time. CONNECT TO HERMES: Desktop app: Settings → Memory and Context → switch provider from Namosin to Hindsight. set API URL to your local Docker container. set bank ID. done. CLI: hermes memory setup → select Hindsight. verify: hermes memory status should show: provider: hindsight, installed, available. CONNECT TO CODEX: npx hindsight-coding-agents install codex \ --self-hosted --server this installs lifecycle hooks: initialize memory on session start. recall context during work. retain the session when done. enable hooks in Codex: Settings → Hooks → trust all three. CONNECT TO CLAUDE CODE (same command): npx hindsight-coding-agents install all "all" connects every detected agent on your machine. Claude Code, Codex, Cursor, and others. one command. every agent shares the same bank. TAGS FOR FILTERING: every memory gets tagged by harness (Hermes, Codex, Claude Code) and optionally by project name. in the Hindsight control plane: filter by harness. see only Hermes memories. or only Codex memories. or search across everything. soft partitions inside one bank. not hard walls. cross-reference when you need to. ONE BANK OR MANY: one global bank: solo dev, related projects. all agents share everything. patterns emerge across projects. per-project banks: unrelated codebases. each project gets its own memory. no cross-contamination. your call. start with one. split when projects diverge. KNOWLEDGE PAGES (v0.9.0): Hindsight auto-generates living summaries from your accumulated memories. components, concepts, conventions, decisions. not static docs. projected from real agent conversations. auto-refresh as new memories land. WHAT TO KNOW: self-hosted via Docker. your data never leaves your machine. backup system built in (admin CLI + scheduled exports). works with any LLM (local Ollama, OpenAI, Codex subscription). memory defense: redact or block sensitive content automatically. 33,000+ memories accumulated in ~10 days of normal use.

YanXbt

29,200 次观看 • 21 天前

Tired of managing 5 different AI API keys? 😩 I just switched to CometAPI and now I use GPT-4o, Claude, Gemini, Grok + image models with ONE single key. All I did was change the base_url and api_key in my code. Done in 15 seconds. No new libraries. No extra logins. No mess. Now I can test any model instantly and everything stays in one dashboard. Super clean for side projects or real apps. If you build with AI at all, this makes life way easier. Check it:
0:48

Tired of managing 5 different AI API keys? 😩 I just switched to CometAPI and now I use GPT-4o, Claude, Gemini, Grok + image models with ONE single key. All I did was change the base_url and api_key in my code. Done in 15 seconds. No new libraries. No extra logins. No mess. Now I can test any model instantly and everything stays in one dashboard. Super clean for side projects or real apps. If you build with AI at all, this makes life way easier. Check it:

Wesley

71,489 次观看 • 2 个月前

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)
5:02

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

15,295 次观看 • 2 个月前

WeWeb MCP is here. Your favorite AI agents can now build directly inside WeWeb. Bring Claude Code, Cursor, ChatGPT, Codex, Antigravity, or any agent you choose. Your agent can help build secure web apps using WeWeb’s pages, components, workflows, API requests, databases, integrations, auth, storage, and more. You decide what it can work on: the full app, or only specific parts of your project. Everything stays visible and editable in WeWeb, so you can review what was built, make changes visually, and keep maintaining the app with your team. No black box. Open beta starts today.
8:36

WeWeb MCP is here. Your favorite AI agents can now build directly inside WeWeb. Bring Claude Code, Cursor, ChatGPT, Codex, Antigravity, or any agent you choose. Your agent can help build secure web apps using WeWeb’s pages, components, workflows, API requests, databases, integrations, auth, storage, and more. You decide what it can work on: the full app, or only specific parts of your project. Everything stays visible and editable in WeWeb, so you can review what was built, make changes visually, and keep maintaining the app with your team. No black box. Open beta starts today.

weweb.io

1,386,670 次观看 • 2 个月前

i was tired of running my one woman BD team for the past 2.5 years so I built my own in use /bd-intern in claude to initiate > intern sets up a quick interview to understand you better > all other agents get full context and are ready to roll > setup takes less than 5 min, runs via a Claude Plugin stop doing and start prompting
0:54

i was tired of running my one woman BD team for the past 2.5 years so I built my own in use /bd-intern in claude to initiate > intern sets up a quick interview to understand you better > all other agents get full context and are ready to roll > setup takes less than 5 min, runs via a Claude Plugin stop doing and start prompting

Mashiat

16,472 次观看 • 6 个月前

OKKKK Ive fully automated Codex + Claude Code it take any app idea and runs a fleet of parallel agents in iterative loops nonstop for 24hr+ it can research, design, plan and execute for DAYS zero back and forth it also costs $0 because it’s powered by AI subs we all already pay for so I could have 100s of complex, polished iOS apps built in 30 days if i really wanted to - for the SAME price as anyone else on the same subscription this is CLONK
0:32

OKKKK Ive fully automated Codex + Claude Code it take any app idea and runs a fleet of parallel agents in iterative loops nonstop for 24hr+ it can research, design, plan and execute for DAYS zero back and forth it also costs $0 because it’s powered by AI subs we all already pay for so I could have 100s of complex, polished iOS apps built in 30 days if i really wanted to - for the SAME price as anyone else on the same subscription this is CLONK

Paulius 🏴‍☠️

44,882 次观看 • 2 个月前

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,473 次观看 • 2 个月前

Bolt 2.0 is here - and it changes everything about building apps with Bolt. No external Supabase connections. No RLS headaches. No auth setup. No separate analytics or hosting. Plus, you can use Claude code directly inside Bolt. Now everything happens inside bolt.new. Here’s how I built a full app in 10 minutes - DB, auth, analytics, and hosting - all with just a few prompts. Everything you need to know about 2.0 🧵
0:20

Bolt 2.0 is here - and it changes everything about building apps with Bolt. No external Supabase connections. No RLS headaches. No auth setup. No separate analytics or hosting. Plus, you can use Claude code directly inside Bolt. Now everything happens inside bolt.new. Here’s how I built a full app in 10 minutes - DB, auth, analytics, and hosting - all with just a few prompts. Everything you need to know about 2.0 🧵

Dhruval

69,311 次观看 • 11 个月前

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source
0:40

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source

Om Patel

153,788 次观看 • 5 个月前

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access
2:15

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 次观看 • 28 天前

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

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

JJ Englert

29,809 次观看 • 5 个月前