正在加载视频...

视频加载失败

返回首页

Rive Editor 0.8.4941 🎨 Many UI improvements ⭐️ Shape handles to modify parametric properties 📏 Opt/Alt-hover measure tool 🤖 Agent now offers Gemini (also available for BYOK) ⌨️ Add child layout with Shift + Opt/Alt + L 🐛 Various fixes and improvements

rive_app's profile picture

Rive

84,978 subscribers

11,044 次观看 • 2 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update
0:36

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update

am.will

742,230 次观看 • 3 个月前

🎉 Tailkit 4.0 is here, and I couldn't be more excited! 🙌🥳 But first - Giveaway Alert! Want to get a free Tailkit Developer license? Just drop a reply and give a like or repost (totally optional, but super appreciated). The lucky winner will be announced next Tuesday (October 8th) – good luck! Can you believe it’s already been 4 years since Tailkit’s journey started? ❤️ It feels like just yesterday I launched Tailkit 1.0 as an offline standalone web app back on October 1st, 2020. I'm really attached to this project because it was launched just a few days before I became a dad 👶😍 Fast forward to today, and Tailkit has grown into a fully customizable, feature-packed online app that gives you access to: - 550+ Tailwind CSS components (fully responsive + dark mode support) - 1,750+ Code snippets for HTML, React, Vue.js, and Alpine.js - 7 Marketing & Application Templates for HTML, React, Vue.js, and Laravel (fully responsive + dark mode support) - 10 Starter Kits for HTML, HTML with Vite, React, Vue.js, Laravel, Next.js, Nuxt, Astro, Svelte and Angular - 30 Days of Unlimited Design Service with every new Team license - Exclusive deals on third-party tools and projects - Handy helper tools like Button Builder, Color Palette, and Icon Finder - 3,700+ SVG Icons from Bootstrap and Heroicons - Free lifetime updates - Email support whenever you need it And the 4.0 update is packed with even more awesome features and upgrades: - 6 new UI components (Notifications) were added in Application UI package - 20 new UI components (Image/Content Sliders++) were added in Marketing package - React version (uses Vite) is introduced for all Templates - React code snippets were improved in all packages - Astro Starter Kit was added - Remove Dark Classes (from code snippets) option was added in App - Universal Dark Mode (preview pane can default to global dark mode) option was added in App - New preview colors (fuchsia, gray) were added in App - Heroicons v2 icons were updated to v2.1.5 adding 28+ brand new icons in App - 3 new exclusive deals are now available - UI design improvements in App - Various improvements and fixes in App - All dependencies were updated in Starter Kits - All dependencies were updated in Templates - Marketing website redesigned - Color Palette tool was made available to all I’ve put over 200 hours into this update alone, and I’m beyond excited to finally share it with you. Your continued support has made this journey possible, and I’m so grateful to have you along for the ride. 🙏 Wishing you an amazing day – remember, YOU ARE AWESOME! Go build something incredible! 🚀
1:17

🎉 Tailkit 4.0 is here, and I couldn't be more excited! 🙌🥳 But first - Giveaway Alert! Want to get a free Tailkit Developer license? Just drop a reply and give a like or repost (totally optional, but super appreciated). The lucky winner will be announced next Tuesday (October 8th) – good luck! Can you believe it’s already been 4 years since Tailkit’s journey started? ❤️ It feels like just yesterday I launched Tailkit 1.0 as an offline standalone web app back on October 1st, 2020. I'm really attached to this project because it was launched just a few days before I became a dad 👶😍 Fast forward to today, and Tailkit has grown into a fully customizable, feature-packed online app that gives you access to: - 550+ Tailwind CSS components (fully responsive + dark mode support) - 1,750+ Code snippets for HTML, React, Vue.js, and Alpine.js - 7 Marketing & Application Templates for HTML, React, Vue.js, and Laravel (fully responsive + dark mode support) - 10 Starter Kits for HTML, HTML with Vite, React, Vue.js, Laravel, Next.js, Nuxt, Astro, Svelte and Angular - 30 Days of Unlimited Design Service with every new Team license - Exclusive deals on third-party tools and projects - Handy helper tools like Button Builder, Color Palette, and Icon Finder - 3,700+ SVG Icons from Bootstrap and Heroicons - Free lifetime updates - Email support whenever you need it And the 4.0 update is packed with even more awesome features and upgrades: - 6 new UI components (Notifications) were added in Application UI package - 20 new UI components (Image/Content Sliders++) were added in Marketing package - React version (uses Vite) is introduced for all Templates - React code snippets were improved in all packages - Astro Starter Kit was added - Remove Dark Classes (from code snippets) option was added in App - Universal Dark Mode (preview pane can default to global dark mode) option was added in App - New preview colors (fuchsia, gray) were added in App - Heroicons v2 icons were updated to v2.1.5 adding 28+ brand new icons in App - 3 new exclusive deals are now available - UI design improvements in App - Various improvements and fixes in App - All dependencies were updated in Starter Kits - All dependencies were updated in Templates - Marketing website redesigned - Color Palette tool was made available to all I’ve put over 200 hours into this update alone, and I’m beyond excited to finally share it with you. Your continued support has made this journey possible, and I’m so grateful to have you along for the ride. 🙏 Wishing you an amazing day – remember, YOU ARE AWESOME! Go build something incredible! 🚀

John Champ

10,940 次观看 • 1 年前

Beta Blocker 3.6 is here and it introduces a BIG new feature. Here's everything that's new: 🖥️ UI Overhaul. The entire interface has been cleaned up to feel more premium, modern, and less boxed-in. 📐 Better Window Scaling. Wider windows now properly use the available space instead of stretching awkwardly or leaving everything floating in the center. 🎨 Live Preview. The Style tab now includes a real-time preview, so you can see exactly what your block will look like before you enable it. ⚙️ Cleaner Detection Settings. Detection settings have been reorganised and simplified so everything is easier to understand. 🧭 Reworked Help & Settings Layout. Important options are now easier to find with a cleaner settings and help structure. now for the big one… 🔄 REVERSE CENSOR REWORK This is the biggest part of the update. Reverse Censor has been completely rebuilt. Instead of blocking detected areas, it now applies your block across the screen while leaving detected parts visible. This also adds: ✨ New Reverse Censor settings tab 🌀 Blur or mosaic modes 🎚️ Strength controls 🖥️ Full monitor selection support ⚡ Live setting updates while blocking is active BUG FIXES & POLISH 🛠️ Fixed Reverse Censor sizing issues on second monitors, including Windows scaling modes like 125% 🖥️ Improved multi-monitor behaviour for effects and Popup Storm 🧹 Cleaned up the Help tab 🎯 Fixed Auto-Detect changing results after switching tabs 📷 Improved camera handling in virtual camera mode 🎮 Reduced cursor flicker while Beta Blocker is active for a smoother gaming experience 🖤 & lots more smaller QoL improvements throughout the app. sfw
0:20

Beta Blocker 3.6 is here and it introduces a BIG new feature. Here's everything that's new: 🖥️ UI Overhaul. The entire interface has been cleaned up to feel more premium, modern, and less boxed-in. 📐 Better Window Scaling. Wider windows now properly use the available space instead of stretching awkwardly or leaving everything floating in the center. 🎨 Live Preview. The Style tab now includes a real-time preview, so you can see exactly what your block will look like before you enable it. ⚙️ Cleaner Detection Settings. Detection settings have been reorganised and simplified so everything is easier to understand. 🧭 Reworked Help & Settings Layout. Important options are now easier to find with a cleaner settings and help structure. now for the big one… 🔄 REVERSE CENSOR REWORK This is the biggest part of the update. Reverse Censor has been completely rebuilt. Instead of blocking detected areas, it now applies your block across the screen while leaving detected parts visible. This also adds: ✨ New Reverse Censor settings tab 🌀 Blur or mosaic modes 🎚️ Strength controls 🖥️ Full monitor selection support ⚡ Live setting updates while blocking is active BUG FIXES & POLISH 🛠️ Fixed Reverse Censor sizing issues on second monitors, including Windows scaling modes like 125% 🖥️ Improved multi-monitor behaviour for effects and Popup Storm 🧹 Cleaned up the Help tab 🎯 Fixed Auto-Detect changing results after switching tabs 📷 Improved camera handling in virtual camera mode 🎮 Reduced cursor flicker while Beta Blocker is active for a smoother gaming experience 🖤 & lots more smaller QoL improvements throughout the app. sfw

Isla

316,720 次观看 • 2 个月前

Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1 submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at
0:36

Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1 submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at

Thomas Wolf

225,735 次观看 • 1 个月前

Keet Mobile 4.0.0 Changelog 🍐 Features - Keet 4.0.0 introduces a new engine which improves performance, app scalability and sets the ground for a new set of features development. Improvements - Faster room loading with optimised icons and image-preview caching. - Media previews respect maximum image size to save bandwidth. - Added a system-update banner to keep you informed of important upgrades. - Cleaner room creation flow and refined DM request handling. - Down arrow and room avatar colours match desktop application. - Bottom tab bar is now hidden until onboarding is complete. - Clearer username error messages and progress indicators on slow networks. - Better feedback form now includes your username automatically - Call experience tweaks: hangs up cleanly; DM ring logic improved; Android auto-end in background. - Introduced hang-up icon for when call ends in rooms. - Device naming screen now auto focuses the input field. - Updated confirm device screen. - Software version list now shows Hyperdiscovery and lists WebRTC as keet-webrtc. - Refreshed onboarding pages and UI text updates. - Improved audio record UX and many Fixes - Fixed avatar rendering issues. - Removed grey bars at the top of several pages. - Stopped the tooltip from appearing when the username is already set. - Aligned the error-log message-field layout. - Resolved cursor and emoji picker jumps when switching between emoji and keyboard input. - Corrected chat text input width. - Restored fullscreen video previews. - Fixed image loading status indicators. - Adjusted code block spacing for messages sent from mobile. - Prevented locked recordings from following you when leaving a room. - Fixed a crash when opening a room on Android. - Stopped unnecessary FlatList re-renders. - Center aligned preview images. - Resolved chat UI breakage after double tapping the emoji picker icon. - Corrected contentFit on image messages. - Ensured pinned messages remain visible during a call. - Fixed speaker tooltip content overflow. - Calls: fixed orientation breaks, crash when app is killed, call-ring answer now opens the screen. - Resolved unrecoverable error when sharing a file from Google Files. - Eliminated flicker when searching usernames. - Disabled button presses while a tooltip is visible. - Fixed Discover Communities being cut off on small devices. - Disabled bottom tab presses when no identity is set. - Corrected tooltip orientation on tablets. Keet Desktop 4.0.0 Changelog Features - Keet 4.0.0 introduces a new engine which improves performance, app scalability and sets the ground for a new set of features development Improvements - Introduced system-banner UI for updates and notices. - Added a 'Quit' button to uncaught error screens. - Displayed an app loader before the app initialises. - Added a toast notification and an informative banner when sending a DM request. - Consistent avatars between DM rooms and member views. - Added support to medium sized file previews in chat. - Smoother last message rendering in the room list. - Added a chat loader on start up when no cache is available. - Clearer version display in the software section and added hyper db version to the list. - Updated texts for system and migration banners. - Refactored DM request actions and block member logic. Fixes - Prevented image preview blinking while loading. - Fixed crash when removing an avatar file from a deleted message. - Onboarding status is now remembered after a restart. - Eliminated room menu blinking via useDeferredValue. - Prevented Rive animation from disappearing when switching monitors. - Stopped creation of duplicate DM rooms for the same member. - Resolved broken file preview when a file lacked a name. - Restored missing styles on error pages. - Prevented error pages from appearing behind the loader. - Corrected emoji rendering on macOS. - Repaired chat voice message playback. - Fixed useRoomConfig imports. - Corrected file item height in room info. And more
5:57

Keet Mobile 4.0.0 Changelog 🍐 Features - Keet 4.0.0 introduces a new engine which improves performance, app scalability and sets the ground for a new set of features development. Improvements - Faster room loading with optimised icons and image-preview caching. - Media previews respect maximum image size to save bandwidth. - Added a system-update banner to keep you informed of important upgrades. - Cleaner room creation flow and refined DM request handling. - Down arrow and room avatar colours match desktop application. - Bottom tab bar is now hidden until onboarding is complete. - Clearer username error messages and progress indicators on slow networks. - Better feedback form now includes your username automatically - Call experience tweaks: hangs up cleanly; DM ring logic improved; Android auto-end in background. - Introduced hang-up icon for when call ends in rooms. - Device naming screen now auto focuses the input field. - Updated confirm device screen. - Software version list now shows Hyperdiscovery and lists WebRTC as keet-webrtc. - Refreshed onboarding pages and UI text updates. - Improved audio record UX and many Fixes - Fixed avatar rendering issues. - Removed grey bars at the top of several pages. - Stopped the tooltip from appearing when the username is already set. - Aligned the error-log message-field layout. - Resolved cursor and emoji picker jumps when switching between emoji and keyboard input. - Corrected chat text input width. - Restored fullscreen video previews. - Fixed image loading status indicators. - Adjusted code block spacing for messages sent from mobile. - Prevented locked recordings from following you when leaving a room. - Fixed a crash when opening a room on Android. - Stopped unnecessary FlatList re-renders. - Center aligned preview images. - Resolved chat UI breakage after double tapping the emoji picker icon. - Corrected contentFit on image messages. - Ensured pinned messages remain visible during a call. - Fixed speaker tooltip content overflow. - Calls: fixed orientation breaks, crash when app is killed, call-ring answer now opens the screen. - Resolved unrecoverable error when sharing a file from Google Files. - Eliminated flicker when searching usernames. - Disabled button presses while a tooltip is visible. - Fixed Discover Communities being cut off on small devices. - Disabled bottom tab presses when no identity is set. - Corrected tooltip orientation on tablets. Keet Desktop 4.0.0 Changelog Features - Keet 4.0.0 introduces a new engine which improves performance, app scalability and sets the ground for a new set of features development Improvements - Introduced system-banner UI for updates and notices. - Added a 'Quit' button to uncaught error screens. - Displayed an app loader before the app initialises. - Added a toast notification and an informative banner when sending a DM request. - Consistent avatars between DM rooms and member views. - Added support to medium sized file previews in chat. - Smoother last message rendering in the room list. - Added a chat loader on start up when no cache is available. - Clearer version display in the software section and added hyper db version to the list. - Updated texts for system and migration banners. - Refactored DM request actions and block member logic. Fixes - Prevented image preview blinking while loading. - Fixed crash when removing an avatar file from a deleted message. - Onboarding status is now remembered after a restart. - Eliminated room menu blinking via useDeferredValue. - Prevented Rive animation from disappearing when switching monitors. - Stopped creation of duplicate DM rooms for the same member. - Resolved broken file preview when a file lacked a name. - Restored missing styles on error pages. - Prevented error pages from appearing behind the loader. - Corrected emoji rendering on macOS. - Repaired chat voice message playback. - Fixed useRoomConfig imports. - Corrected file item height in room info. And more

Keet

25,883 次观看 • 1 年前

Just six months ago, DHH (creator of Ruby on Rails and Omarchy) said how he doesn’t really use AI tools to write code, because they are not good enough. Things have changed, a lot. Timestamps: 00:00 Intro 02:11 Omarchy and Ruby on Rails 08:25 37signals overview 10:12 Launching HEY 18:38 Building HEY 22:47 Designers at 37signals 28:08 The craft of design 31:52 Why DHH now embraces AI workflows 39:45 The AI inflection point 44:23 DHH’s agent-first workflow 55:09 AI’s impact on junior developers 1:03:08 Developer experience with AI 1:16:43 What does AI mean for developers? 1:23:33 37signals teams and hiring 1:38:20 Work-life balance with AI 1:41:41 Why DHH keeps building 1:45:24 Closing Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. Stop switching between different tools, and have them all in one place. • WorkOS – Everything you need to make your app enterprise ready. WorkOS gives you APIs to ship enterprise features in days. Check out • Sonar – The makers of SonarQube, the industry standard for automated code review. See how SonarQube Advanced Security is empowering the Agent Centric Development Cycle (AC/DC) with new capabilities. Three interesting observations from this conversation: #1 DHH's philosophy on AI has not changed, but the available tools very much have. Autocomplete-style coding assistants were genuinely annoying for experienced developers six months ago. Things changed with the shift from tab-completion to agent harnesses, plus the emergence of powerful models like Opus 4.5 – when agents started producing code which DHH does want to merge with little to no alteration. #2 Beautiful code and products aren’t matters of vanity; they’re signals of correctness. Dipping into philosophy, DHH says: “When something is beautiful, it’s likely to be correct.” He argues that Steve Jobs wanted the inside of a computer to be beautiful because people who care about circuit board layout are also those who sweat on the details of the UI. #3 DHH’s development workflow, today: He runs tmux to have two models running, and neovim in the center. Specifics: - One fast LLM running (typically Gemini 2.5) in one split terminal - A slow but more powerful model in another terminal (usually Opus) - NeoVim for reviewing diffs via Lazygit
1:47:20

Just six months ago, DHH (creator of Ruby on Rails and Omarchy) said how he doesn’t really use AI tools to write code, because they are not good enough. Things have changed, a lot. Timestamps: 00:00 Intro 02:11 Omarchy and Ruby on Rails 08:25 37signals overview 10:12 Launching HEY 18:38 Building HEY 22:47 Designers at 37signals 28:08 The craft of design 31:52 Why DHH now embraces AI workflows 39:45 The AI inflection point 44:23 DHH’s agent-first workflow 55:09 AI’s impact on junior developers 1:03:08 Developer experience with AI 1:16:43 What does AI mean for developers? 1:23:33 37signals teams and hiring 1:38:20 Work-life balance with AI 1:41:41 Why DHH keeps building 1:45:24 Closing Brought to you by: • Statsig – ⁠ The unified platform for flags, analytics, experiments, and more. Stop switching between different tools, and have them all in one place. • WorkOS – Everything you need to make your app enterprise ready. WorkOS gives you APIs to ship enterprise features in days. Check out • Sonar – The makers of SonarQube, the industry standard for automated code review. See how SonarQube Advanced Security is empowering the Agent Centric Development Cycle (AC/DC) with new capabilities. Three interesting observations from this conversation: #1 DHH's philosophy on AI has not changed, but the available tools very much have. Autocomplete-style coding assistants were genuinely annoying for experienced developers six months ago. Things changed with the shift from tab-completion to agent harnesses, plus the emergence of powerful models like Opus 4.5 – when agents started producing code which DHH does want to merge with little to no alteration. #2 Beautiful code and products aren’t matters of vanity; they’re signals of correctness. Dipping into philosophy, DHH says: “When something is beautiful, it’s likely to be correct.” He argues that Steve Jobs wanted the inside of a computer to be beautiful because people who care about circuit board layout are also those who sweat on the details of the UI. #3 DHH’s development workflow, today: He runs tmux to have two models running, and neovim in the center. Specifics: - One fast LLM running (typically Gemini 2.5) in one split terminal - A slow but more powerful model in another terminal (usually Opus) - NeoVim for reviewing diffs via Lazygit

Gergely Orosz

329,135 次观看 • 3 个月前

We're excited to launch 🚀Airtable AI Assistant 🚀 today, along with AI document analysis and AI web research capabilities! Airtable was founded 12 years ago with the mission of democratizing software creation. Our pioneering innovation was to distill app-building concepts (data, logic, interface) into intuitive visual components, like a no-code lego kit for app building. At the time, we speculated that someday, maybe AI would get good enough to enable conversational app building–talking to an expert AI app builder–and be a huge unlock, making app building even more accessible. We’re now at that point. While surprisingly impressive text generation and manipulation by LLMs was the breakthrough of the 2022 ChatGPT moment, the emergence of surprisingly impressive reasoning capability from LLMs is the breakthrough of 2025. This is unlocking more autonomous agentic experiences, and generating apps and code is the first killer use case (Cursor, @windsurf, Devin, v0, bolt.new, Replit ⠕ Agent to name a few). But for the large class of non-technical builders, a different approach is needed. When AI generates apps with code, rather than no-code building blocks, it requires a developer to fully understand how they work – and to verify them for hidden mistakes that would be tricky/impossible to debug by interface inspection alone (it may look right, but what is the data model business logic is flawed in non-obvious ways?). Airtable Assistant is an agent that can build and modify Airtable apps through conversation, changing schemas, adding automations, and designing interfaces. You can ask it to do things like: –“Research every conference attendee in this base” to have the Assistant immediately spin up an army of researchers that pull in background information for your attendees –“Analyze each contract to identify key risks they pose to my business” to have the Assistant add an AI field that runs an analysis at scale for each contract you’ve signed. Airtable Assistant can also answer questions about the data in your apps, like prompts as advanced as: –“I'm about to meet Jane Smith at Zelos, read all of their recent sales call transcripts and tell me how far along they are in their implementation and if they’re dealing with any issues” –“What are the most common risk factors in our contracts? Are there any changes to our default posture we might consider?” Credit to Mike Krieger for introducing us to the concept of low floor and high ceiling in HCI many years ago, which has become part of our internal lexicon for thinking about product improvements. Assistant dramatically lowers the floor to building apps, including more sophisticated ones, by helping human builders translate their business requirements into the schema design, logic, and interfaces required to deliver on the use case. In addition to launching Airtable Assistant today, we’re also releasing the capability to deploy thousands of AI web researchers, and AI document analysts, to continuously work on the data in Airtable apps. You can do things like: –Pull strategy and value stories from every product requirement doc to draft launch and release messaging –Monitor all brand mentions across digital channels to measure campaign impact –Create an automatically updating competitive intelligence dossier with the latest news and messaging from every competitor in your industry Check it out 👇
1:43

We're excited to launch 🚀Airtable AI Assistant 🚀 today, along with AI document analysis and AI web research capabilities! Airtable was founded 12 years ago with the mission of democratizing software creation. Our pioneering innovation was to distill app-building concepts (data, logic, interface) into intuitive visual components, like a no-code lego kit for app building. At the time, we speculated that someday, maybe AI would get good enough to enable conversational app building–talking to an expert AI app builder–and be a huge unlock, making app building even more accessible. We’re now at that point. While surprisingly impressive text generation and manipulation by LLMs was the breakthrough of the 2022 ChatGPT moment, the emergence of surprisingly impressive reasoning capability from LLMs is the breakthrough of 2025. This is unlocking more autonomous agentic experiences, and generating apps and code is the first killer use case (Cursor, @windsurf, Devin, v0, bolt.new, Replit ⠕ Agent to name a few). But for the large class of non-technical builders, a different approach is needed. When AI generates apps with code, rather than no-code building blocks, it requires a developer to fully understand how they work – and to verify them for hidden mistakes that would be tricky/impossible to debug by interface inspection alone (it may look right, but what is the data model business logic is flawed in non-obvious ways?). Airtable Assistant is an agent that can build and modify Airtable apps through conversation, changing schemas, adding automations, and designing interfaces. You can ask it to do things like: –“Research every conference attendee in this base” to have the Assistant immediately spin up an army of researchers that pull in background information for your attendees –“Analyze each contract to identify key risks they pose to my business” to have the Assistant add an AI field that runs an analysis at scale for each contract you’ve signed. Airtable Assistant can also answer questions about the data in your apps, like prompts as advanced as: –“I'm about to meet Jane Smith at Zelos, read all of their recent sales call transcripts and tell me how far along they are in their implementation and if they’re dealing with any issues” –“What are the most common risk factors in our contracts? Are there any changes to our default posture we might consider?” Credit to Mike Krieger for introducing us to the concept of low floor and high ceiling in HCI many years ago, which has become part of our internal lexicon for thinking about product improvements. Assistant dramatically lowers the floor to building apps, including more sophisticated ones, by helping human builders translate their business requirements into the schema design, logic, and interfaces required to deliver on the use case. In addition to launching Airtable Assistant today, we’re also releasing the capability to deploy thousands of AI web researchers, and AI document analysts, to continuously work on the data in Airtable apps. You can do things like: –Pull strategy and value stories from every product requirement doc to draft launch and release messaging –Monitor all brand mentions across digital channels to measure campaign impact –Create an automatically updating competitive intelligence dossier with the latest news and messaging from every competitor in your industry Check it out 👇

Howie Liu

2,313,248 次观看 • 1 年前

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?
0:57

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?

kmdr

29,430 次观看 • 13 天前

Today, we’re announcing Kosmos, our newest AI Scientist, available to use now. Users estimate Kosmos does 6 months of work in a single day. One run can read 1,500 papers and write 42,000 lines of code. At least 79% of its findings are reproducible. Kosmos has made 7 discoveries so far, which we are releasing today, in areas ranging from neuroscience to material science and clinical genetics, in collaboration with our academic beta testers. Three of these discoveries reproduced unpublished findings; four are net new, validated contributions to the scientific literature. AI-accelerated science is here. Our core innovation in Kosmos is the use of a structured, continuously-updated world model. As described in our technical report, Kosmos’ world model allows it to process orders of magnitude more information than could fit into the context of even the longest-context language models, allowing it to synthesize more information and pursue coherent goals over longer time horizons than Robin or any of our other prior agents. In this respect, we believe Kosmos is the most compute-intensive language agent released so far in any field, and by far the most capable AI Scientist available today. The use of a persistent world model also enables single Kosmos trajectories to produce highly complex outputs that require multiple significant logical leaps. As with all of our systems, Kosmos is designed with transparency and verifiability in mind: every conclusion in a Kosmos report can be traced through our platform to the specific lines of code or the specific passages in the scientific literature that inspired it, ensuring that Kosmos’ findings are fully auditable at all times. We are also using this opportunity to announce the launch of Edison Scientific, a new commercial spinout of FutureHouse, which will be focused on commercializing our agents and applying them to automate scientific research in drug discovery and beyond. Edison will be taking over management of the FutureHouse platform, where you can access Kosmos alongside our Literature, Molecules, and Precedent agents (previously Crow, Phoenix, and Owl). Edison will continue to offer free tier usage for casual users and academics, while also offering higher rate limits and additional features for users who need them. You can read more about this spinout on our blog, below. A few important notes if you’re going to try Kosmos. Firstly, Kosmos is different from many other AI tools you might have played with, including our other agents. It is more similar to a Deep Research tool than it is to a chatbot: it takes some time to figure out how to prompt it effectively, and we have tried to include guidelines on this to help (see below). It costs $200/run right now (200 credits per run, and $1/credit), with some free tier usage for academics. This is heavily discounted; people who sign up for Founding Subscriptions now can lock in the $1/credit price indefinitely, but the price ultimately will probably be higher. Again, this is less chatbot and more research tool, something you run on high-value targets as needed. Some caveats are also warranted. Firstly, we find that 80% of Kosmos findings are reproducible, which also means 20% are not -- some things it says will be wrong. Also, Kosmos certainly does produce outputs that are the equivalent to several months of human labor, but it also often goes down rabbit holes or chases statistically significant yet scientifically irrelevant findings. We often run Kosmos multiple times on the same objective in order to sample the various research avenues it can take. There are still a bunch of rough edges on the UI and such, which we are working on. Finally, we are aware that the 6 month figure is much greater than estimates by other AI labs, like METR, about the length of tasks that AI Agents can currently perform. You can read discussion about this in our blog post. Huge congratulations to our team that put this together, led by Ludovico Mitchener and Michaela Hinks: Angela Yiu, Benjamin Chang, Sid Narayanan, Edwin Melville-Green, Albert Bou, Arvis Sulovari, Oz Wassie, Jon Laurent. A particular shout out to Michael Skarlinski and his team that rebuilt the platform for this launch, especially Andy Cai Andy Cai, Richard Magness, Remo Storni, Tyler Nadolski Tyler Nadolski, Mayk Caldas Mayk Caldas, Sam Cox Sam Cox and more. This work would not have been possible without significant contributions from academic collaborators Mathieu Bourdenx, Eric Landsness, Dániel Barabási, Nicky Evans, Tonio Buonassisi, Bruna Gomes, Shriya Reddy, Martha Foiani, and Randall Bateman. We also want to thank our numerous supporters, especially Eric Schmidt, who has been a tremendous ally. We will have more to say about our supporters soon!
0:44

Today, we’re announcing Kosmos, our newest AI Scientist, available to use now. Users estimate Kosmos does 6 months of work in a single day. One run can read 1,500 papers and write 42,000 lines of code. At least 79% of its findings are reproducible. Kosmos has made 7 discoveries so far, which we are releasing today, in areas ranging from neuroscience to material science and clinical genetics, in collaboration with our academic beta testers. Three of these discoveries reproduced unpublished findings; four are net new, validated contributions to the scientific literature. AI-accelerated science is here. Our core innovation in Kosmos is the use of a structured, continuously-updated world model. As described in our technical report, Kosmos’ world model allows it to process orders of magnitude more information than could fit into the context of even the longest-context language models, allowing it to synthesize more information and pursue coherent goals over longer time horizons than Robin or any of our other prior agents. In this respect, we believe Kosmos is the most compute-intensive language agent released so far in any field, and by far the most capable AI Scientist available today. The use of a persistent world model also enables single Kosmos trajectories to produce highly complex outputs that require multiple significant logical leaps. As with all of our systems, Kosmos is designed with transparency and verifiability in mind: every conclusion in a Kosmos report can be traced through our platform to the specific lines of code or the specific passages in the scientific literature that inspired it, ensuring that Kosmos’ findings are fully auditable at all times. We are also using this opportunity to announce the launch of Edison Scientific, a new commercial spinout of FutureHouse, which will be focused on commercializing our agents and applying them to automate scientific research in drug discovery and beyond. Edison will be taking over management of the FutureHouse platform, where you can access Kosmos alongside our Literature, Molecules, and Precedent agents (previously Crow, Phoenix, and Owl). Edison will continue to offer free tier usage for casual users and academics, while also offering higher rate limits and additional features for users who need them. You can read more about this spinout on our blog, below. A few important notes if you’re going to try Kosmos. Firstly, Kosmos is different from many other AI tools you might have played with, including our other agents. It is more similar to a Deep Research tool than it is to a chatbot: it takes some time to figure out how to prompt it effectively, and we have tried to include guidelines on this to help (see below). It costs $200/run right now (200 credits per run, and $1/credit), with some free tier usage for academics. This is heavily discounted; people who sign up for Founding Subscriptions now can lock in the $1/credit price indefinitely, but the price ultimately will probably be higher. Again, this is less chatbot and more research tool, something you run on high-value targets as needed. Some caveats are also warranted. Firstly, we find that 80% of Kosmos findings are reproducible, which also means 20% are not -- some things it says will be wrong. Also, Kosmos certainly does produce outputs that are the equivalent to several months of human labor, but it also often goes down rabbit holes or chases statistically significant yet scientifically irrelevant findings. We often run Kosmos multiple times on the same objective in order to sample the various research avenues it can take. There are still a bunch of rough edges on the UI and such, which we are working on. Finally, we are aware that the 6 month figure is much greater than estimates by other AI labs, like METR, about the length of tasks that AI Agents can currently perform. You can read discussion about this in our blog post. Huge congratulations to our team that put this together, led by Ludovico Mitchener and Michaela Hinks: Angela Yiu, Benjamin Chang, Sid Narayanan, Edwin Melville-Green, Albert Bou, Arvis Sulovari, Oz Wassie, Jon Laurent. A particular shout out to Michael Skarlinski and his team that rebuilt the platform for this launch, especially Andy Cai Andy Cai, Richard Magness, Remo Storni, Tyler Nadolski Tyler Nadolski, Mayk Caldas Mayk Caldas, Sam Cox Sam Cox and more. This work would not have been possible without significant contributions from academic collaborators Mathieu Bourdenx, Eric Landsness, Dániel Barabási, Nicky Evans, Tonio Buonassisi, Bruna Gomes, Shriya Reddy, Martha Foiani, and Randall Bateman. We also want to thank our numerous supporters, especially Eric Schmidt, who has been a tremendous ally. We will have more to say about our supporters soon!

Sam Rodriques

732,206 次观看 • 9 个月前

Big Update: Critters Quest Website Steps Into Production State with an Exciting New Design! Hey Critters, we're thrilled to share some major news, our website has officially migrated from mint state to production state, and we're taking our platform to the next level right here at After three weeks of dedicated work, we've transformed Critters Quest into a more organized, stable, and feature-rich experience, setting the stage for everything we've planned for the future. This isn't just an upgrade—it's the first step before the real journey begins! Key Updates to the Homepage and Beyond Fresh Categories and Pages: We've added exciting new sections to help you dive deeper into the Critters Quest world: - Play $QUEST (Explorer Page for Staking $QUEST): Dive into our new $QUEST explorer page, where you can find games to stake your $QUEST tokens to earn rewards, track your staking progress, and engage in strategic gameplay challenges that grow your Critters' value. - Play Spins (Explorer Page for Spins): Spins are now front and center with a dedicated spins explorer page, designed to highlight Multipliers Spins, Terron Spins, Quest Tablet Spins(coming soon👀), and more. Organized as daily free spins, limited events, and partner spin opportunities for special loot, offering new ways to boost your rewards. - Breakdown Informational Page: We've introduced a comprehensive guide for new users (and a refresher for veterans) to explore how key features work. This page currently focuses exclusively on the mechanics and info for Master Edition NFTs, Cloned Editions, and Multipliers. It explains how Master Editions serve as the foundation for your Critters' value, how Master Editions allow Cloned Editions to be minted out for others, and how Multipliers enhance your rewards throughout critters ecosystem. Redesigned Homepage: Our homepage has been completely transformed into an intuitive experience that gives you a complete overview of the Critters Quest ecosystem at a glance. It features: - Feature Carousel: Highlighting new additions and important updates - Ecosystem Activities: Real-time data showing active games, spins, or other ongoing activities. - Mini-Leaderboards: Quick snapshots of top performers - PFP Activity Feed: See the latest community PFPs minted - Quick-Access CTAs: Every section includes direct links to the full experience, letting you dive deeper with just one click - Streamlined Introduction: New visitors get a concise overview of Critters Quest right away This overview approach makes navigation intuitive for both newcomers and veterans, ensuring you never miss important information or opportunities. Elevated Designs Across the Board: - Dynamic Castle Layout in the Banner: Our homepage now features a dynamic castle layout in the banner, with castles positioned in the order they appear on the leaderboard. The top leaders are showcased at the top, adding a visual representation of community rankings and bringing our competitive spirit to life. - Critters Terminal (Formerly $QUEST Terminal): Our terminal has been upgraded with a sleek new look and enhanced functionality, now known as the Critters Terminal. It's your go-to hub for finding the most powerful cards and looking for new Critters—it tracks $QUEST allocation on available Critters for sale, their power, equipment, and more, helping you build the ultimate team. - Equipment Viewing: Viewing Critters and their equipment has been elevated with detailed rankings, power levels, and stats, giving you a clearer picture of your team's strength and hinting at game mechanics like power-based strategies. - Spins Pages Redesign: The spins experience has been completely revamped with a fresh, user-friendly design, making it easier to spin for rewards and track your progress, with a focus on multipliers and special loot opportunities. - Partnership Sign-Up Page Update: On our main page, you'll see mentions of our legendary partners—GM Capital, Mintify, Sniper, and more—highlighting our growing ecosystem. We've also updated our partnership sign-up page for those looking to partner with us. This page now includes a detailed breakdown of partnership options and new form fields to streamline the collaboration process. We're excited to expand our network in the future! - Animated Banners: Across all pages, you'll notice new animated banners that bring our world to life, adding visual excitement and guiding you through the platform. - Archived Pages: To streamline the site and focus on the future, we've archived older pages like the Master Edition Mint and Referral pages. These will remain available for reference. Coming Soon: We're already working on exciting additions, including: - SHOP Page: A new experience for purchasing items and gear to enhance your Critters Quest adventures, where you can equip your Critters with power-boosting equipment. - Tokenomics/Liquidty Section (Addition to the INFO Page): We're working on a detailed tokenomics section to add to our INFO page, launching alongside updates to our plans for DEX integration. These changes will add more value to Master Editions, give participants greater confidence, and enhance the overall ecosystem. - Cloned Edition Minting: This innovative feature will launch when Master Editions begin to mint out their Clones, allowing people to mint these unique variations. Cloned Editions will inherit traits and offer new gameplay opportunities, expanding your Critters' potential and rewards. Backend Tweaks: While many of these improvements are visible, we've also made numerous backend tweaks that aren't immediately seen. These optimizations ensure better performance, stability, and scalability for the platform moving forward. Continuous Elevation: This migration marks our first massive overhaul, but it's just the beginning. We're committed to elevating Critters Quest on a continuous basis, refining and expanding the platform with each rollout to keep delivering the best possible experience for our community. Foundation for the Future These updates aren't just cosmetic—they're foundational. After three weeks of hard work, we've created a more organized and structured platform that's ready to support the future rollouts we've been teasing, like Edition Minting, Items Shop, and Quest Games. This migration streamlines our process, allowing us to deliver updates faster and more efficiently for both new users and our longtime adventurers. This is truly the first step before the real journey begins. Our production state sets us up to expand Critters Quest into an even bigger, more engaging GameFi ecosystem, where your Critters can thrive through quests, spins, and community challenges. Whether you're a newcomer or a seasoned player, these changes make it easier to explore, compete, and grow your collection. Your Next Expedition We're just getting started! This production-ready overhaul is the launchpad for all the exciting features and expansions we have planned. Keep an eye on for more updates, and dive into the new pages to see how you can level up your Critters Quest experience. We want to hear from you! Share your feedback, suggestions, and experiences with our new production site in our Discord or commenting below. Your input directly shapes our future updates and helps us create the best possible experience. Thank you for your patience and support during this transition. Together, we're building something truly special!
0:35

Big Update: Critters Quest Website Steps Into Production State with an Exciting New Design! Hey Critters, we're thrilled to share some major news, our website has officially migrated from mint state to production state, and we're taking our platform to the next level right here at After three weeks of dedicated work, we've transformed Critters Quest into a more organized, stable, and feature-rich experience, setting the stage for everything we've planned for the future. This isn't just an upgrade—it's the first step before the real journey begins! Key Updates to the Homepage and Beyond Fresh Categories and Pages: We've added exciting new sections to help you dive deeper into the Critters Quest world: - Play $QUEST (Explorer Page for Staking $QUEST): Dive into our new $QUEST explorer page, where you can find games to stake your $QUEST tokens to earn rewards, track your staking progress, and engage in strategic gameplay challenges that grow your Critters' value. - Play Spins (Explorer Page for Spins): Spins are now front and center with a dedicated spins explorer page, designed to highlight Multipliers Spins, Terron Spins, Quest Tablet Spins(coming soon👀), and more. Organized as daily free spins, limited events, and partner spin opportunities for special loot, offering new ways to boost your rewards. - Breakdown Informational Page: We've introduced a comprehensive guide for new users (and a refresher for veterans) to explore how key features work. This page currently focuses exclusively on the mechanics and info for Master Edition NFTs, Cloned Editions, and Multipliers. It explains how Master Editions serve as the foundation for your Critters' value, how Master Editions allow Cloned Editions to be minted out for others, and how Multipliers enhance your rewards throughout critters ecosystem. Redesigned Homepage: Our homepage has been completely transformed into an intuitive experience that gives you a complete overview of the Critters Quest ecosystem at a glance. It features: - Feature Carousel: Highlighting new additions and important updates - Ecosystem Activities: Real-time data showing active games, spins, or other ongoing activities. - Mini-Leaderboards: Quick snapshots of top performers - PFP Activity Feed: See the latest community PFPs minted - Quick-Access CTAs: Every section includes direct links to the full experience, letting you dive deeper with just one click - Streamlined Introduction: New visitors get a concise overview of Critters Quest right away This overview approach makes navigation intuitive for both newcomers and veterans, ensuring you never miss important information or opportunities. Elevated Designs Across the Board: - Dynamic Castle Layout in the Banner: Our homepage now features a dynamic castle layout in the banner, with castles positioned in the order they appear on the leaderboard. The top leaders are showcased at the top, adding a visual representation of community rankings and bringing our competitive spirit to life. - Critters Terminal (Formerly $QUEST Terminal): Our terminal has been upgraded with a sleek new look and enhanced functionality, now known as the Critters Terminal. It's your go-to hub for finding the most powerful cards and looking for new Critters—it tracks $QUEST allocation on available Critters for sale, their power, equipment, and more, helping you build the ultimate team. - Equipment Viewing: Viewing Critters and their equipment has been elevated with detailed rankings, power levels, and stats, giving you a clearer picture of your team's strength and hinting at game mechanics like power-based strategies. - Spins Pages Redesign: The spins experience has been completely revamped with a fresh, user-friendly design, making it easier to spin for rewards and track your progress, with a focus on multipliers and special loot opportunities. - Partnership Sign-Up Page Update: On our main page, you'll see mentions of our legendary partners—GM Capital, Mintify, Sniper, and more—highlighting our growing ecosystem. We've also updated our partnership sign-up page for those looking to partner with us. This page now includes a detailed breakdown of partnership options and new form fields to streamline the collaboration process. We're excited to expand our network in the future! - Animated Banners: Across all pages, you'll notice new animated banners that bring our world to life, adding visual excitement and guiding you through the platform. - Archived Pages: To streamline the site and focus on the future, we've archived older pages like the Master Edition Mint and Referral pages. These will remain available for reference. Coming Soon: We're already working on exciting additions, including: - SHOP Page: A new experience for purchasing items and gear to enhance your Critters Quest adventures, where you can equip your Critters with power-boosting equipment. - Tokenomics/Liquidty Section (Addition to the INFO Page): We're working on a detailed tokenomics section to add to our INFO page, launching alongside updates to our plans for DEX integration. These changes will add more value to Master Editions, give participants greater confidence, and enhance the overall ecosystem. - Cloned Edition Minting: This innovative feature will launch when Master Editions begin to mint out their Clones, allowing people to mint these unique variations. Cloned Editions will inherit traits and offer new gameplay opportunities, expanding your Critters' potential and rewards. Backend Tweaks: While many of these improvements are visible, we've also made numerous backend tweaks that aren't immediately seen. These optimizations ensure better performance, stability, and scalability for the platform moving forward. Continuous Elevation: This migration marks our first massive overhaul, but it's just the beginning. We're committed to elevating Critters Quest on a continuous basis, refining and expanding the platform with each rollout to keep delivering the best possible experience for our community. Foundation for the Future These updates aren't just cosmetic—they're foundational. After three weeks of hard work, we've created a more organized and structured platform that's ready to support the future rollouts we've been teasing, like Edition Minting, Items Shop, and Quest Games. This migration streamlines our process, allowing us to deliver updates faster and more efficiently for both new users and our longtime adventurers. This is truly the first step before the real journey begins. Our production state sets us up to expand Critters Quest into an even bigger, more engaging GameFi ecosystem, where your Critters can thrive through quests, spins, and community challenges. Whether you're a newcomer or a seasoned player, these changes make it easier to explore, compete, and grow your collection. Your Next Expedition We're just getting started! This production-ready overhaul is the launchpad for all the exciting features and expansions we have planned. Keep an eye on for more updates, and dive into the new pages to see how you can level up your Critters Quest experience. We want to hear from you! Share your feedback, suggestions, and experiences with our new production site in our Discord or commenting below. Your input directly shapes our future updates and helps us create the best possible experience. Thank you for your patience and support during this transition. Together, we're building something truly special!

Critters Quest

26,167 次观看 • 1 年前

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.
0:38

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.

Jeffrey Emanuel

116,929 次观看 • 5 个月前

🛠️ Patch Notes - Early Access Patch 2 We are incredibly excited to be releasing our largest patch yet, marking the One Month Anniversary of our Steam Early Access Launch! Patch 2 is chock full of highly requested features such as Weapon Tryout, the ability to Respec, DLSS / FSR Upscaling and Controller Remapping. Lots of Balancing and Quality of Life improvements, Audio, Animation, and Visual Effect polish as well as a multitude of bug fixes are also included! Between DLSS and FSR, numerous CPU, GPU performance improvements, and memory optimization we are confident that your experience of playing No Rest For The Wicked will be significantly smoother across a wide range of hardware. For NVIDIA users, we are excited to mention that there’s a new Game Ready Driver for No Rest for the Wicked! Be sure to check out our Patch 2 Highlight Video and the full patch notes below. ⚔️ Performance: • Performance Mode now lowers texture resolution, reducing crashes on lower-end machines • Numerous Significant CPU optimizations • Fixed performance degradation that might occur on some gamepads • Fixed numerous memory leaks • Reduced instantiation spikes for numerous objects • Disabled detail meshes on generic humanoids faces when not needed • Reduced latency, overhead and improved stability of GPU Culling • Optimized texture resolution and memory budgets for Steam Deck • Optimized Art content in Ship Prologue and its cinematics • Removed unused weapon assets to free up memory • Removed leftover developer tools to free up memory • Optimized CPU spikes of a variety of common content loading operations • Added texture streaming for character portraits during dialogue interactions to save memory • Fixed some persistent log spam being generated by potatoes in Nameless Pass • Cleaned up numerous NPC prefabs, reducing memory footprint and instantiation costs • Optimized Ambient Occlusion Rendering • Extended GPU culling usage for more cases • Configured and optimized pooling for more prefab instantiations reducing CPU spikes ⚔️ Gameplay Systems: • Added new Respec System! ⚬ Players can now Respec by examining the statue in the Cerim Crucible Atrium ⚬ Respec allows players to take back Attribute Points that have been allocated at the cost of 1 Fallen Ember per Attribute Point returned ⚬ Players can then allocate returned Attribute Points for no cost at the Respec screen or in the existing Stats screen ⚔️ Quality of Life: • All weapons can now be equipped regardless of their Attribute Requirements to allow players to try out weapons they acquire ⚬ Weapons that the player does not meet the requirements for will deal less damage through negative scaling on the Attributes that are below the weapon’s Attribute Requirements • Inventory Items can now be docked to compare them ⚬ Press F (Keyboard) or Y (Controller) to dock items and hover other items to compare • Brought back the Misc category to the Inventory ⚬ Housing items, Runes, Fallen Embers and other miscellaneous items will now be sorted into this category and free up space from other categories • Vendor screens are now sorted by item type so that items are more organized for purchase • Improved Stamina player HUD brightness for better visibility, and readability of stamina debt • Added side notifications for when Danos Sacrament Upgrades are completed • Added Floor Indicators under the Clock HUD to show the Cerim Crucible floors • Improved visibility of LB/RB button icons for Equipment HUD on Steam Deck ⚔️ Settings: • Added support for Upscaling with DLSS 3.7 and FSR 2.2 • Added custom key rebinding options for Controller • Added support for Mouse Buttons 4,5 and F1-F12 Keys for custom Keyboard bindings • Default Keyboard layout set to Mouse+WASD • Added support for worldspace Player HUD (Stamina wheel, NPC name tags, etc) brightness to UI Brightness setting ⚔️ Content Additions: • Added a new set of enchantments • All Throw runes can now be added to Spears ⚔️ Loot: • Added Pig Sticker Blueprint to Fillmore's Level 1 Shop • Added Assegai Blueprint to Whittacker's Level 1 Shop ⚔️ Balance: • Nerfed Throw runes ⚬ Reduced Poise Damage on all Throw runes ⚬ Reduced Damage on Ice Throw Rune • Nerfed Focus Regeneration enchant curve so that it no longer generates too much Focus too quickly • Focus Regeneration enchantment no longer drops with Gloves and now only drops with Helmets • This includes enchanting items at Eleanor • Falling Sky and Woodland Protector’s initial item levels were set too high and have been lowered to the intended levels ⚔️ Weapons: • Updated animation for backstabbing with Staves, Spears, Greatswords and Great Hammers • Updated visual effects for Piercing type weapon attacks (such as Spear or Rapier) ⚔️ Enemies and Bosses: • Polished Darak boss fight ⚬ Improved behavior to prevent him standing idle after attacking ⚬ Improved behavior when fighting ranged builds • Added Bite Attack to Plague Rat • Added Back Attack to Risen Axe Bruiser • Added escape logic to Risen Fire Bomber • Added Elemental Affix visual effects to Nith Brute, Nith Screamer and Shackled Brute • Adding cloth simulation to Boarskin Bruiser • Polished rigging on Plagued Boomer • Reduced camera shake intensity on Risen Hammer Bruiser, Boarskin Bruiser and Riven Twins • Smaller enemies can now smash breakable objects (barrels, crates, etc.) ⚔️ NPCs: • Changed the name of the worried woman in the Sacrament Town Square to Nell • Polishing dialog for Druo, Lucian and Everwyn • Updated the dialog for NPCs at the Cerim Gate in Nameless Pass • Added eavesdrop to Sleeping Guard Gerard in Sacrament ⚔️ Areas: • Improved collision, faders and set dressing in Prologue Ship, Orban Glades, Mariner’s Keep, Nameless Pass, Sacrament, Multiple Sacrament Interiors, Cerim Crucible, Cerim Cave, Riven Twins Boss Arena and Potion Seller Cave • Polished lighting for the ship in Prologue, Sacrament and Cerim Crucible • Updated foliage in various locations • Added physics and wind simulation to Spruce trees ⚔️ Cinematics: • Polished animations for characters in the Inquisition Arrival cinematic • Improved lighting, character rim lighting and volumetrics for the Prologue Ship Crash Outro and Inquisition Arrival cinematics • Removed a background character who was blocking part of the view in the Inquisition Arrival cinematic • Fixed cloth and camera pops in the Inquisition Arrival cinematic ⚔️ Audio: • Environment update for Sacrament: ⚬ Added Ambience Emitters for certain Residential and Vendor buildings like the Cook, Tavern, Woodcrafter and Enchantress ⚬ Updated zone beds and oneshots for unique parts of town (Cemetery, Poor Area,Training Grounds, Dasha Sanctuary) ⚬ The church near the cemetery now has bells ringing to service playing at certain times of day, followed by churchgoers praying and chanting from behind the doors. ⚬ Updated ambience for Sacrament Town Square to feel busier during the day ⚬ Updated environment audio for the Cerim Gate zone in Mountain Pass • Increased audio buffer to help alleviate audio crackle artifacts • Increased available audio resources to help prevent sounds from dropping out during long play sessions • Updated audio for Cerim Vision cinematic • Updated audio mix for Barrel and Crate destruction • Saluting Guards in Sacrament now have sound • Added Weapon-specific Impacts on parrying and blocking actions • Added ladder sliding sound effects for Kickdown Ladders • Added sound effects for going down Ladders • Added new sound effects for Plague-Enchanted weapons • Polished audio for Bounties enemies • Fixed missing sounds for Plagued Mutant Soldier • Fixed rain sounds appearing in Sacrament Interiors • Fixed enchantment-specific weapon whooshes cutting a bit too early • Fixed NPCs not making footstep sounds when walking around • Fixed environment states sometimes not resetting when returning to the main menu ⚔️ VFX: • Blood effects are now juicier and used more often! • Improved blood visual effects attachment to characters bodies from attacking and getting hit • Increased intensity of shiny item drop VFX ⚔️ Bounties and Challenges: • Updated Crustacean Conundrum bounty to spawn 14 Crabs while still only requiring 8 Crabs be killed to complete ⚔️ Localization: • Added and updated localized text in many places across multiple languages • Added localization support for new Controller Remapping screen and for various missing localized elements • Fixed incorrect font on the Activities screen ⚔️ Bug Fixes: • Fixed various enchantments on unique weapons and rings that weren’t working properly • Fixed Rested Bonuses for sleeping in beds • Fixed Key Items respawning after pick up • Fixed navigation in Nameless Pass which was preventing certain enemies and the Riven Twins boss from patrolling and moving to the player • Fixed Echo Knight falling off the arena and blocking progress • Fixed Cerim Armor missing upgrades at Filmore • Fixed Risen Pavise, Eye of the Beholder and Wooden Howler Shields not showing their proper models • Fixed SHIFT key not being recognized in the Main Menu • Fixed certain environment textures overriding certain armor textures • Fixed certain armor having missing or incorrect cloth simulation • Fixed rigging on certain armor • Fixed The Wallow boss attacks not having sound effects • Fixed Falling Sky Blueprint not giving the Unique version of the weapon when crafting • Fixed an issue where completed but not yet turned in bounty/challenge rewards were being automatically given to the player at reset • Fixed wall cannons not firing in Cerim Crucible • Fixed XP UI not showing “Max Level” after reaching the level cap • Fixed Level and XP UI being present without a Character selected in the Main Menu • Fixed “Long Area Name” appearing on the map where map is unavailable (such as Cerim Crucible) • Fixed being able to skip through locked doors in The Shallows • Fixed players getting stuck at the end of the entrance corridor in the Echo Knight Arena • Fixed Enchant Item Challenge counting enchanted items that are picked up • Fixed mortuary guard popping in on screen during Spoken and Unspoken quest • Fixed extra Elsa map marker during the Spoken and Unspoken quest • Fixed Giles and Petra standing instead of sitting on the chairs in Caroline’s Inn • Fixed Arrows not hitting Plagued Wolf • Fixed Wolf and Plagued Wolf target point • Fixed Tanth Knight getting stuck during patrolling in Mariner’s Keep at Endgame state • Fixed Darak leaving his shield in Orban Glades when he escapes • Fixed chest opening VFX in Performance and Balanced quality presets • Fixed Wolf having a dance party after death • Fixed Chest floating in the air in Mariner’s Keep • Fixed incorrect texture on the Crafting Table • Fixed 4096x2160 resolution appearing as 256x135 aspect ratio, instead displays as 1.9:1 • Fixed overblown bonfire lighting at The Shallows • Removed rogue rim light at The Shallows • Removed lighting debug shortcut See the full patch notes here -
1:30

🛠️ Patch Notes - Early Access Patch 2 We are incredibly excited to be releasing our largest patch yet, marking the One Month Anniversary of our Steam Early Access Launch! Patch 2 is chock full of highly requested features such as Weapon Tryout, the ability to Respec, DLSS / FSR Upscaling and Controller Remapping. Lots of Balancing and Quality of Life improvements, Audio, Animation, and Visual Effect polish as well as a multitude of bug fixes are also included! Between DLSS and FSR, numerous CPU, GPU performance improvements, and memory optimization we are confident that your experience of playing No Rest For The Wicked will be significantly smoother across a wide range of hardware. For NVIDIA users, we are excited to mention that there’s a new Game Ready Driver for No Rest for the Wicked! Be sure to check out our Patch 2 Highlight Video and the full patch notes below. ⚔️ Performance: • Performance Mode now lowers texture resolution, reducing crashes on lower-end machines • Numerous Significant CPU optimizations • Fixed performance degradation that might occur on some gamepads • Fixed numerous memory leaks • Reduced instantiation spikes for numerous objects • Disabled detail meshes on generic humanoids faces when not needed • Reduced latency, overhead and improved stability of GPU Culling • Optimized texture resolution and memory budgets for Steam Deck • Optimized Art content in Ship Prologue and its cinematics • Removed unused weapon assets to free up memory • Removed leftover developer tools to free up memory • Optimized CPU spikes of a variety of common content loading operations • Added texture streaming for character portraits during dialogue interactions to save memory • Fixed some persistent log spam being generated by potatoes in Nameless Pass • Cleaned up numerous NPC prefabs, reducing memory footprint and instantiation costs • Optimized Ambient Occlusion Rendering • Extended GPU culling usage for more cases • Configured and optimized pooling for more prefab instantiations reducing CPU spikes ⚔️ Gameplay Systems: • Added new Respec System! ⚬ Players can now Respec by examining the statue in the Cerim Crucible Atrium ⚬ Respec allows players to take back Attribute Points that have been allocated at the cost of 1 Fallen Ember per Attribute Point returned ⚬ Players can then allocate returned Attribute Points for no cost at the Respec screen or in the existing Stats screen ⚔️ Quality of Life: • All weapons can now be equipped regardless of their Attribute Requirements to allow players to try out weapons they acquire ⚬ Weapons that the player does not meet the requirements for will deal less damage through negative scaling on the Attributes that are below the weapon’s Attribute Requirements • Inventory Items can now be docked to compare them ⚬ Press F (Keyboard) or Y (Controller) to dock items and hover other items to compare • Brought back the Misc category to the Inventory ⚬ Housing items, Runes, Fallen Embers and other miscellaneous items will now be sorted into this category and free up space from other categories • Vendor screens are now sorted by item type so that items are more organized for purchase • Improved Stamina player HUD brightness for better visibility, and readability of stamina debt • Added side notifications for when Danos Sacrament Upgrades are completed • Added Floor Indicators under the Clock HUD to show the Cerim Crucible floors • Improved visibility of LB/RB button icons for Equipment HUD on Steam Deck ⚔️ Settings: • Added support for Upscaling with DLSS 3.7 and FSR 2.2 • Added custom key rebinding options for Controller • Added support for Mouse Buttons 4,5 and F1-F12 Keys for custom Keyboard bindings • Default Keyboard layout set to Mouse+WASD • Added support for worldspace Player HUD (Stamina wheel, NPC name tags, etc) brightness to UI Brightness setting ⚔️ Content Additions: • Added a new set of enchantments • All Throw runes can now be added to Spears ⚔️ Loot: • Added Pig Sticker Blueprint to Fillmore's Level 1 Shop • Added Assegai Blueprint to Whittacker's Level 1 Shop ⚔️ Balance: • Nerfed Throw runes ⚬ Reduced Poise Damage on all Throw runes ⚬ Reduced Damage on Ice Throw Rune • Nerfed Focus Regeneration enchant curve so that it no longer generates too much Focus too quickly • Focus Regeneration enchantment no longer drops with Gloves and now only drops with Helmets • This includes enchanting items at Eleanor • Falling Sky and Woodland Protector’s initial item levels were set too high and have been lowered to the intended levels ⚔️ Weapons: • Updated animation for backstabbing with Staves, Spears, Greatswords and Great Hammers • Updated visual effects for Piercing type weapon attacks (such as Spear or Rapier) ⚔️ Enemies and Bosses: • Polished Darak boss fight ⚬ Improved behavior to prevent him standing idle after attacking ⚬ Improved behavior when fighting ranged builds • Added Bite Attack to Plague Rat • Added Back Attack to Risen Axe Bruiser • Added escape logic to Risen Fire Bomber • Added Elemental Affix visual effects to Nith Brute, Nith Screamer and Shackled Brute • Adding cloth simulation to Boarskin Bruiser • Polished rigging on Plagued Boomer • Reduced camera shake intensity on Risen Hammer Bruiser, Boarskin Bruiser and Riven Twins • Smaller enemies can now smash breakable objects (barrels, crates, etc.) ⚔️ NPCs: • Changed the name of the worried woman in the Sacrament Town Square to Nell • Polishing dialog for Druo, Lucian and Everwyn • Updated the dialog for NPCs at the Cerim Gate in Nameless Pass • Added eavesdrop to Sleeping Guard Gerard in Sacrament ⚔️ Areas: • Improved collision, faders and set dressing in Prologue Ship, Orban Glades, Mariner’s Keep, Nameless Pass, Sacrament, Multiple Sacrament Interiors, Cerim Crucible, Cerim Cave, Riven Twins Boss Arena and Potion Seller Cave • Polished lighting for the ship in Prologue, Sacrament and Cerim Crucible • Updated foliage in various locations • Added physics and wind simulation to Spruce trees ⚔️ Cinematics: • Polished animations for characters in the Inquisition Arrival cinematic • Improved lighting, character rim lighting and volumetrics for the Prologue Ship Crash Outro and Inquisition Arrival cinematics • Removed a background character who was blocking part of the view in the Inquisition Arrival cinematic • Fixed cloth and camera pops in the Inquisition Arrival cinematic ⚔️ Audio: • Environment update for Sacrament: ⚬ Added Ambience Emitters for certain Residential and Vendor buildings like the Cook, Tavern, Woodcrafter and Enchantress ⚬ Updated zone beds and oneshots for unique parts of town (Cemetery, Poor Area,Training Grounds, Dasha Sanctuary) ⚬ The church near the cemetery now has bells ringing to service playing at certain times of day, followed by churchgoers praying and chanting from behind the doors. ⚬ Updated ambience for Sacrament Town Square to feel busier during the day ⚬ Updated environment audio for the Cerim Gate zone in Mountain Pass • Increased audio buffer to help alleviate audio crackle artifacts • Increased available audio resources to help prevent sounds from dropping out during long play sessions • Updated audio for Cerim Vision cinematic • Updated audio mix for Barrel and Crate destruction • Saluting Guards in Sacrament now have sound • Added Weapon-specific Impacts on parrying and blocking actions • Added ladder sliding sound effects for Kickdown Ladders • Added sound effects for going down Ladders • Added new sound effects for Plague-Enchanted weapons • Polished audio for Bounties enemies • Fixed missing sounds for Plagued Mutant Soldier • Fixed rain sounds appearing in Sacrament Interiors • Fixed enchantment-specific weapon whooshes cutting a bit too early • Fixed NPCs not making footstep sounds when walking around • Fixed environment states sometimes not resetting when returning to the main menu ⚔️ VFX: • Blood effects are now juicier and used more often! • Improved blood visual effects attachment to characters bodies from attacking and getting hit • Increased intensity of shiny item drop VFX ⚔️ Bounties and Challenges: • Updated Crustacean Conundrum bounty to spawn 14 Crabs while still only requiring 8 Crabs be killed to complete ⚔️ Localization: • Added and updated localized text in many places across multiple languages • Added localization support for new Controller Remapping screen and for various missing localized elements • Fixed incorrect font on the Activities screen ⚔️ Bug Fixes: • Fixed various enchantments on unique weapons and rings that weren’t working properly • Fixed Rested Bonuses for sleeping in beds • Fixed Key Items respawning after pick up • Fixed navigation in Nameless Pass which was preventing certain enemies and the Riven Twins boss from patrolling and moving to the player • Fixed Echo Knight falling off the arena and blocking progress • Fixed Cerim Armor missing upgrades at Filmore • Fixed Risen Pavise, Eye of the Beholder and Wooden Howler Shields not showing their proper models • Fixed SHIFT key not being recognized in the Main Menu • Fixed certain environment textures overriding certain armor textures • Fixed certain armor having missing or incorrect cloth simulation • Fixed rigging on certain armor • Fixed The Wallow boss attacks not having sound effects • Fixed Falling Sky Blueprint not giving the Unique version of the weapon when crafting • Fixed an issue where completed but not yet turned in bounty/challenge rewards were being automatically given to the player at reset • Fixed wall cannons not firing in Cerim Crucible • Fixed XP UI not showing “Max Level” after reaching the level cap • Fixed Level and XP UI being present without a Character selected in the Main Menu • Fixed “Long Area Name” appearing on the map where map is unavailable (such as Cerim Crucible) • Fixed being able to skip through locked doors in The Shallows • Fixed players getting stuck at the end of the entrance corridor in the Echo Knight Arena • Fixed Enchant Item Challenge counting enchanted items that are picked up • Fixed mortuary guard popping in on screen during Spoken and Unspoken quest • Fixed extra Elsa map marker during the Spoken and Unspoken quest • Fixed Giles and Petra standing instead of sitting on the chairs in Caroline’s Inn • Fixed Arrows not hitting Plagued Wolf • Fixed Wolf and Plagued Wolf target point • Fixed Tanth Knight getting stuck during patrolling in Mariner’s Keep at Endgame state • Fixed Darak leaving his shield in Orban Glades when he escapes • Fixed chest opening VFX in Performance and Balanced quality presets • Fixed Wolf having a dance party after death • Fixed Chest floating in the air in Mariner’s Keep • Fixed incorrect texture on the Crafting Table • Fixed 4096x2160 resolution appearing as 256x135 aspect ratio, instead displays as 1.9:1 • Fixed overblown bonfire lighting at The Shallows • Removed rogue rim light at The Shallows • Removed lighting debug shortcut See the full patch notes here -

No Rest for the Wicked

184,300 次观看 • 2 年前

12 hours ago I made the decision to fly out to El Salvador to be the first ever to make an AI generated short film for a country. I’m now 4 hours away from arriving there. (Talk about executing fast) I will take my time writing this message because the reason why has layers. A few months ago I founded ARQ and bootstrapped a platform that lets anyone create high-quality AI productions from start to finish. the best models a multi-agent creative assistant a built-in video editor All in one place. Alongside the product, I’ve built a strong community where I livestream daily, teaching creators how to use AI to tell better stories and get paid for their work. Shortly after we got dozens of offers to make commercials for companies. This was fun, until we came to the conclusion that we were wasting a lot of potential by focussing on companies, while we could also tell the story of nations, movements, communities and narratives that the world needs to hear. So we’re starting with El Salvador. Why? Because Nayib Bukele is one of the most inspiring leaders in the world, not only embracing, but embodying change, turning the country from one of the most dangerous places on earth, to one of the safest and innovation friendly nations. Humanity is experiencing a shift. New technology, new philosophies, new artists, new story tellers, new builders. A new world. So the argument is not AI vs. Non AI. The argument is: Soul Vs. Soulless Pro Human vs. Anti Human Building Vs. Gambling Effort Vs. Effortless This is what ARQ stands for. Not just a SaaS but a safe haven for the soul. It feels like my moral responsibility to speak not only for the AI community but for every human creator. So I decided to do something that requires so much effort and human involvement; no one can deny that AI serves only as a tool in the process. Instead of making 100 commercials for companies, I want to prove what 2 young humans can do with balls and the tools available today. “You can just do things” Yesterday evening me and Ya-Sirr D left our comfortable office in Dubai and are now on our way to El Salvador. The goal: to create a 3-5 Minute AI powered short film telling THEIR story. We will spend every day live streaming, showcasing the process of creating the video while pushing the boundaries of every tool available on the market. Think Google DeepMind , Hailuo AI (MiniMax), Kling AI, Reve, Midjourney, xAI All through ARQ. Who knows who we inspire? Who knows who we meet? We might as well end up meeting the president himself. We want to get to know the country, its people and imagine its future. We want to visit innovative projects in El Salvador, hear the stories of it’s citizens and include them in the video: MURPHSLIFE Stacy Herbert 🇸🇻🚀 @BuildSalvador The Bitcoin Office Bitcoin Beach Anyone who can help us tell the story. Not just any story, one of the most inspiring stories of the past 10 years. Like I said. You can just do things. We have to stop thinking in steps. I know where I will be in 30 days if I stay in the office. More followers. More beta testers. More live streams. More revenue. But by taking this leap of faith. We can be a case study. An inspiration. An ARQ. I remove expectations and increase chances of special things happening. If anyone in El Salvador has any recommendations on who and what places I should visit, send me a DM. We will post updates on X and create an entire “vlog/documentary” for youtube. Join the discord for daily live streams and lessons on how to improve your creation skills. We expect that it will take 7-9 days to finish the entire short film. It will be posted on all social platforms. ARQ. A safe haven for the soul.
2:33

12 hours ago I made the decision to fly out to El Salvador to be the first ever to make an AI generated short film for a country. I’m now 4 hours away from arriving there. (Talk about executing fast) I will take my time writing this message because the reason why has layers. A few months ago I founded ARQ and bootstrapped a platform that lets anyone create high-quality AI productions from start to finish. the best models a multi-agent creative assistant a built-in video editor All in one place. Alongside the product, I’ve built a strong community where I livestream daily, teaching creators how to use AI to tell better stories and get paid for their work. Shortly after we got dozens of offers to make commercials for companies. This was fun, until we came to the conclusion that we were wasting a lot of potential by focussing on companies, while we could also tell the story of nations, movements, communities and narratives that the world needs to hear. So we’re starting with El Salvador. Why? Because Nayib Bukele is one of the most inspiring leaders in the world, not only embracing, but embodying change, turning the country from one of the most dangerous places on earth, to one of the safest and innovation friendly nations. Humanity is experiencing a shift. New technology, new philosophies, new artists, new story tellers, new builders. A new world. So the argument is not AI vs. Non AI. The argument is: Soul Vs. Soulless Pro Human vs. Anti Human Building Vs. Gambling Effort Vs. Effortless This is what ARQ stands for. Not just a SaaS but a safe haven for the soul. It feels like my moral responsibility to speak not only for the AI community but for every human creator. So I decided to do something that requires so much effort and human involvement; no one can deny that AI serves only as a tool in the process. Instead of making 100 commercials for companies, I want to prove what 2 young humans can do with balls and the tools available today. “You can just do things” Yesterday evening me and Ya-Sirr D left our comfortable office in Dubai and are now on our way to El Salvador. The goal: to create a 3-5 Minute AI powered short film telling THEIR story. We will spend every day live streaming, showcasing the process of creating the video while pushing the boundaries of every tool available on the market. Think Google DeepMind , Hailuo AI (MiniMax), Kling AI, Reve, Midjourney, xAI All through ARQ. Who knows who we inspire? Who knows who we meet? We might as well end up meeting the president himself. We want to get to know the country, its people and imagine its future. We want to visit innovative projects in El Salvador, hear the stories of it’s citizens and include them in the video: MURPHSLIFE Stacy Herbert 🇸🇻🚀 @BuildSalvador The Bitcoin Office Bitcoin Beach Anyone who can help us tell the story. Not just any story, one of the most inspiring stories of the past 10 years. Like I said. You can just do things. We have to stop thinking in steps. I know where I will be in 30 days if I stay in the office. More followers. More beta testers. More live streams. More revenue. But by taking this leap of faith. We can be a case study. An inspiration. An ARQ. I remove expectations and increase chances of special things happening. If anyone in El Salvador has any recommendations on who and what places I should visit, send me a DM. We will post updates on X and create an entire “vlog/documentary” for youtube. Join the discord for daily live streams and lessons on how to improve your creation skills. We expect that it will take 7-9 days to finish the entire short film. It will be posted on all social platforms. ARQ. A safe haven for the soul.

Amir D

54,566 次观看 • 8 个月前

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,579 次观看 • 4 个月前

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 次观看 • 3 个月前

77 Reasons Why I’ve Invested Over $8,000,000+ in MultiversX (EGLD) and Why EGLD Will Crush It in 2025 (My Investment Thesis). I publicly shared my portfolio on X. EGLD is A) Better than BTC B) Everything that ETH wants to be C) The GameStop of Crypto 1. EGLD is verifiably the most scalable (theoretically unlimited) L1 chain in the world, theoretically capable of over 10 million TPS (thanks to adaptive state sharding). 2. e-Gold is digital gold. It has the best tokenomics among all L1s, similarly scarce to BTC, with a maximum supply of 31.4 million coins. Currently, 27.68 million coins are in circulation. 3. EGLD will be the most decentralized cryptocurrency in the world thanks to sharding and minimal hardware requirements for running nodes. It’s already second only to Ethereum with 3,618 validator nodes. 4. EGLD has extremely low fees, around ~$0.002 per transaction. 5. EGLD is extremely secure. No wallet drains like on ETH/SOL; assets are owned natively (not via a smart contract). There is no MEV risk (front-running bots). 6. EGLD is the only chain in the world with an on-chain Guardian (two-phase verification), making it impossible for a hacker to steal your funds—even if they have your private keys (seed phrase). 7. EGLD is carbon-neutral and eco-friendly, not wasting energy like BTC and other PoW chains. It’s exceptionally efficient, scalable, global, and sustainable. 8. EGLD has the best UX in crypto. Download the xPortal wallet—it’s like discovering Apple in Web3. The interface is simple, flawless, and you barely realize you’re using crypto. Instead of addresses, you use HeroTags. The app features all dApps, everything runs smoothly, and the visuals are beautifully designed. The explorer, web wallet, etc. follow the same high-quality user experience. 9. EGLD supports native assets, unlike Ethereum, for example. 10. EGLD is the first chain to fully implement horizontal (theoretically unlimited) sharding without compromising on decentralization—unlike Solana and others that attempt vertical scaling, leading to multiple network downtimes (11+ times) and huge hardware demands for validators, ultimately harming decentralization. 11. EGLD makes setting up a validator agency extremely easy. Even complete IT beginners can do it. The UX and documentation are superb. I personally set up the “EGLDSqueeze” agency in about 30 minutes. Managing it is straightforward via the web wallet, which feels like managing a Facebook page. This simplifies decentralization enormously. 12. EGLD allows literally anyone (even your grandma) to participate in decentralization, since nodes can run on a Raspberry Pi or a relatively affordable phone. Imagine millions of people worldwide securing the network, validating transactions without even knowing it. This can’t be done with BTC, where setting up profitable mining operations is prohibitively expensive. 13. WASM-Based Virtual Machine: You can write smart contracts in your favorite language, compile them, and run them via the fastest VM in the world. 14. EGLD has been tested at an incredible 263,000 TPS using its sharding mechanism and low hardware requirements. Allegedly, by mid-next year (April), they’ll demonstrate 1,000,000 TPS. (For context: Mastercard handles around 5,000 TPS; BTC handles 5–7 TPS.) 15. EGLD is currently the most advanced L1 in terms of scalability, security, decentralization, UX, eco-friendliness, and tokenomics. It’s the only chain that has genuinely solved the Blockchain Trilemma and is ready to onboard 1 billion people into crypto—users who won’t even realize they’re interacting with crypto. 16. EGLD is perfectly positioned for AI projects—AI agents, AI tools, or a so-called “Truth Machine” that monitors other AIs on-chain, documenting what’s true and comparing different AI outputs (some of which may be censored or biased), ensuring people don’t get confused or scammed in an AI-driven world. 17. The EGLD team is the hardest-working team I’ve ever encountered. I had the honor of meeting many of them personally, and can attest that their pace—even during a bear market—is extraordinary. 18. EGLD’s development team is exceptionally active on GitHub, continually improving their network and actively committing code. 19. EGLD plans to introduce an update reducing block time to 600ms (down from ~6 seconds), which would make the chain essentially unrivaled. 20. EGLD is effectively the only usable L1 in Europe, and the team has direct connections within the EU government—extremely bullish for the project. 21. EGLD provides top-tier on-chain governance not only for the MultiversX (EGLD) protocol but also for DeFi projects (e.g., xExchange, MEX). 22. EGLD plans to expand to the US, likely opening offices in Austin, Texas. This could put them in direct contact with Elon Musk (if it hasn’t happened already), as he’s involved with If he’s done his research, he’d discover there’s simply no better L1 worldwide. 23. EGLD solved fully implemented sharding, perfect tokenomics, and top-tier architecture with just $5M, whereas other chains failed to do so even with $100M+. The second-best sharding network, NEAR, needed $100M, has worse tokenomics, and its sharding isn’t fully implemented yet. Its UX also doesn’t compare. Owning NEAR was like comparing a VW Golf R to a Porsche GT3—EGLD is the Porsche GT3. 24. According to Similarweb, EGLD has significantly high traffic relative to other chains with market caps 100x larger. The market cap vs. web traffic discrepancy is huge, which is a strong indicator of EGLD’s potential. 25. EGLD has the most active and dedicated community relative to its user base, with users who believe in the technology, have full faith in the team, and remain loyal despite price volatility—because they use the chain and know there’s nothing better. 26. Check other chains’ active user counts on X (Twitter) and compare it with the followers of EGLD’s founders and main network accounts, versus those with 30x, 50x, or 100x larger market caps. 27. Visit the MultiversX website to observe the futuristic design and presentation, then compare it to other chains that appear nearly a decade behind in design and branding. 28. EGLD hosts the xDay Global event, showcasing updates, new builders, projects in the ecosystem, and major announcements—similar to Apple’s Keynotes—delivered in a highly professional, goosebump-inducing atmosphere. The next event is in Korea, the second-biggest crypto market after the US. Check out their previous xDay after-movie to see why this is extremely bullish. 29. EGLD is moving forward with plans for the first regulated, audited EU stablecoin under MiCa regulation, made possible by acquiring xMoney, which I view as a “Stripe” for crypto/fiat, offering everything from user solutions to merchant services—potentially the future of payments. 30. Greg Siourouni recently joined EGLD, having been an executive director at SUI Foundation. He’s now co-founder of xMoney Global. xMoney (formerly UTrust, with token UTK) is owned and founded by the MultiversX Labs team. A stablecoin might be introduced soon, which would be massively bullish given xMoney’s roadmap. They recently announced integrations with Binance Pay—both ways. 31. EGLD prioritizes user safety, believing it’s the only feasible approach once the network scales to serve a billion people—many of whom are retail users with little to no security awareness. 32. EGLD offers “Sovereign Chains,” letting you effectively clone their chain without heavy development, set up your own validators, and leverage their unlimited scalability. Any blockchain (ETH, BTC, SOL) struggling with scalability, decentralization, or security could run an ultra-fast, scalable, and secure L2 on EGLD’s Sovereign Chain, meeting top enterprise requirements. No one else has really done this. The Sovereign Chain demo achieved astonishing TPS and has an SDK. 33. No downtime since inception. 34. No shard takeover attacks have occurred. 35. Extremely fast—soon 600ms block time will be in place. 36. ESDTs – The best token standard available: fungible, non-fungible, semi-fungible, DeFi assets—everything is native and highly customizable. 37. Top-tier composability of assets and smart contracts. 38. Integrated DNS at protocol level with HeroTags (nicknames) instead of long addresses. 39. Asynchronous calls are supported. 40. Cross-shard transfers, execution, reverts, and calls are seamlessly integrated. 41. The best staking system in the space. Secure Proof of Stake (SPoS) is far more efficient than Proof of Work (PoW). 42. Built-in Delegation and Staking Provider system, with over 125K delegators. 43. Complete support for liquid staked assets, fostering decentralization rather than centralization. 44. TransferRoles for ESDT and other advanced operations. 45. Composable tasks on-chain for more sophisticated DeFi workflows. 46. MultiTransfer and asset execution within one transaction. 47. Re-entrancy protection is built-in by design. 48. Storage for ESDT assets goes beyond a linear approach, optimizing performance. 49. No integer overflows thanks to integrated safeMath operations. 50. Integrated crypto opcodes in the VM, enhancing security and performance. 51. Support for BigFloats, BigInts, and BigDecimals, enabling advanced financial calculations on-chain. 52. No sandwich attacks, plus front-running and MEV protection. 53. Relayed Transactions, simplifying user interactions and fees. 54. Smart Accounts featuring data tries and multiple built-in functions. 55. Generalized Paymaster solutions, enabling flexible fee models. 56. Subscriptions for recurring or automated on-chain payments. 57. Web2-like usability with Web3 functionality, bridging mainstream adoption. 58. StakingV4 for improved decentralization. 59. Enhanced MEV protection rolling out to safeguard users. 60. Parallel execution is coming soon, boosting throughput. 61. 1 million TPS is on the roadmap, targeted for demonstration. 62. 600ms block time is also coming soon. 63. Reduced cross-shard processing is planned to improve efficiency. 64. ZK everywhere (PI²): “prove everything” approach is coming. 65. AsyncV3 is in development for more complex cross-contract interactions. 66. Scalability enhancements for Merkle Tries or a new data model are being explored. 67. Linear storage on the VM is forthcoming. 68. A dynamic language interpreter at the VM is also planned. 69. Rumors suggest that MultiversX (EGLD) is building a “Truth Machine” on their L1—an essential, game-changing tool for AI verification and societal impact. 70. The entire team features individuals with PhDs in mathematics and physics, and many are former engineers at Google, IBM, and similar companies. 71. Over 56% of the network’s supply is staked, showcasing strong community involvement. 72. More than 6,772,347 accounts have been created on the network. 73. A total of 476,627,710 transactions have been processed on-chain without any outages or hacks. 74. EGLD has built a massive ecosystem over time. While not as numerous in project count as Solana, its market cap is ~100x smaller, yet it has far superior tokenomics and technology. The projects that do exist, like Hatom Protocol, are top-tier in UX, security, and advanced features. Hatom will soon introduce USH, a truly high-quality, decentralized stablecoin. 75. On competing chains, automated transactions aren’t easily or cheaply executed, whereas on MultiversX, tools like let you do this for free (with near-zero fees). 76. No other chain combines such a strong team and long-term vision where every product meets extreme security and UX standards like MultiversX does. This is why I see it as the “next Apple” in Web3. 77. MultiversX has a new CMO – Adam Bates, a former CMO at the Cardano Foundation. He was behind the success of Cardano’s huge marketing campaign and has a very good relationship with Charles Hoskinson. Thanks to him, Beniamin Mincu (the founder of MultiversX) was likely introduced, and now they will probably discuss how both blockchains can help each other, as well as any other potential collaborations we don’t yet know about. This is also extremely bullish. #EGLD is undeniably the most Scalable, Advanced, Secure, and User-friendly L1 supercomputer ever created. It’s built to SHAPE THE FUTURE. 1) 2) 3) 4) 5) 27/6/2024 - EGLDSqueeze - SUMMARY: HERE IS NO 2ND BEST. EGLD IS ONLY ONE BLOCKCHAIN THAT CAN RULE THEM ALL. ✅ UNLIMITED SCALING ✅ SCARCE AS BTC ✅ PROGRAMMABLE AS ETH ✅ NO DOWNTIME AS SOL ✅ UI/UX OF Apple ✅ SHARDING DONE BEFORE NEAR & TON ✅ BEST WALLET xPortal WITH GUARDIAN Price prediction (NFA|DYOR): My reasoning is that the real market cap as of December 23, 2024...if we take into account the value of other cryptocurrencies such as BTC, SOL, ETH, AVAX, NEAR, TON, Cardano, BNB, XRP, and so forth, plus the existence of meme coins with valuations above 20 billion USD, or even games nobody plays anymore that still have valuations above 800 million shows that EGLD’s current market cap of approximately 942 million USD is incredibly low. From a technological standpoint, user experience, and other relevant aspects, compared to SOL, NEAR, TON, AVAX, and other L1 protocols, EGLD’s market cap should realistically be around 100 billion USD. Therefore, my prediction and investment thesis is a minimum of a 100x increase from its current price (+-SOL marketcap). MultiversX is ready to onboard 1 billion people to the blockchain. From a long-term perspective, it could even reach a market cap of 1 trillion USD, which is roughly half of where BTC is right now. That would be approximately a 1060x gain from the current market cap. 1 EGLD (MultiversX) is for $34 (only 31.4M max supply) think about this. Not financial advice. Again. There is no 2nd best L1. Position yourself where the puck is going, then wait at the goal until the goal gets there Apes together, strong. Ape alone, weak. We Don't Worry. We Just Win. Shape The Future
5:34

77 Reasons Why I’ve Invested Over $8,000,000+ in MultiversX (EGLD) and Why EGLD Will Crush It in 2025 (My Investment Thesis). I publicly shared my portfolio on X. EGLD is A) Better than BTC B) Everything that ETH wants to be C) The GameStop of Crypto 1. EGLD is verifiably the most scalable (theoretically unlimited) L1 chain in the world, theoretically capable of over 10 million TPS (thanks to adaptive state sharding). 2. e-Gold is digital gold. It has the best tokenomics among all L1s, similarly scarce to BTC, with a maximum supply of 31.4 million coins. Currently, 27.68 million coins are in circulation. 3. EGLD will be the most decentralized cryptocurrency in the world thanks to sharding and minimal hardware requirements for running nodes. It’s already second only to Ethereum with 3,618 validator nodes. 4. EGLD has extremely low fees, around ~$0.002 per transaction. 5. EGLD is extremely secure. No wallet drains like on ETH/SOL; assets are owned natively (not via a smart contract). There is no MEV risk (front-running bots). 6. EGLD is the only chain in the world with an on-chain Guardian (two-phase verification), making it impossible for a hacker to steal your funds—even if they have your private keys (seed phrase). 7. EGLD is carbon-neutral and eco-friendly, not wasting energy like BTC and other PoW chains. It’s exceptionally efficient, scalable, global, and sustainable. 8. EGLD has the best UX in crypto. Download the xPortal wallet—it’s like discovering Apple in Web3. The interface is simple, flawless, and you barely realize you’re using crypto. Instead of addresses, you use HeroTags. The app features all dApps, everything runs smoothly, and the visuals are beautifully designed. The explorer, web wallet, etc. follow the same high-quality user experience. 9. EGLD supports native assets, unlike Ethereum, for example. 10. EGLD is the first chain to fully implement horizontal (theoretically unlimited) sharding without compromising on decentralization—unlike Solana and others that attempt vertical scaling, leading to multiple network downtimes (11+ times) and huge hardware demands for validators, ultimately harming decentralization. 11. EGLD makes setting up a validator agency extremely easy. Even complete IT beginners can do it. The UX and documentation are superb. I personally set up the “EGLDSqueeze” agency in about 30 minutes. Managing it is straightforward via the web wallet, which feels like managing a Facebook page. This simplifies decentralization enormously. 12. EGLD allows literally anyone (even your grandma) to participate in decentralization, since nodes can run on a Raspberry Pi or a relatively affordable phone. Imagine millions of people worldwide securing the network, validating transactions without even knowing it. This can’t be done with BTC, where setting up profitable mining operations is prohibitively expensive. 13. WASM-Based Virtual Machine: You can write smart contracts in your favorite language, compile them, and run them via the fastest VM in the world. 14. EGLD has been tested at an incredible 263,000 TPS using its sharding mechanism and low hardware requirements. Allegedly, by mid-next year (April), they’ll demonstrate 1,000,000 TPS. (For context: Mastercard handles around 5,000 TPS; BTC handles 5–7 TPS.) 15. EGLD is currently the most advanced L1 in terms of scalability, security, decentralization, UX, eco-friendliness, and tokenomics. It’s the only chain that has genuinely solved the Blockchain Trilemma and is ready to onboard 1 billion people into crypto—users who won’t even realize they’re interacting with crypto. 16. EGLD is perfectly positioned for AI projects—AI agents, AI tools, or a so-called “Truth Machine” that monitors other AIs on-chain, documenting what’s true and comparing different AI outputs (some of which may be censored or biased), ensuring people don’t get confused or scammed in an AI-driven world. 17. The EGLD team is the hardest-working team I’ve ever encountered. I had the honor of meeting many of them personally, and can attest that their pace—even during a bear market—is extraordinary. 18. EGLD’s development team is exceptionally active on GitHub, continually improving their network and actively committing code. 19. EGLD plans to introduce an update reducing block time to 600ms (down from ~6 seconds), which would make the chain essentially unrivaled. 20. EGLD is effectively the only usable L1 in Europe, and the team has direct connections within the EU government—extremely bullish for the project. 21. EGLD provides top-tier on-chain governance not only for the MultiversX (EGLD) protocol but also for DeFi projects (e.g., xExchange, MEX). 22. EGLD plans to expand to the US, likely opening offices in Austin, Texas. This could put them in direct contact with Elon Musk (if it hasn’t happened already), as he’s involved with If he’s done his research, he’d discover there’s simply no better L1 worldwide. 23. EGLD solved fully implemented sharding, perfect tokenomics, and top-tier architecture with just $5M, whereas other chains failed to do so even with $100M+. The second-best sharding network, NEAR, needed $100M, has worse tokenomics, and its sharding isn’t fully implemented yet. Its UX also doesn’t compare. Owning NEAR was like comparing a VW Golf R to a Porsche GT3—EGLD is the Porsche GT3. 24. According to Similarweb, EGLD has significantly high traffic relative to other chains with market caps 100x larger. The market cap vs. web traffic discrepancy is huge, which is a strong indicator of EGLD’s potential. 25. EGLD has the most active and dedicated community relative to its user base, with users who believe in the technology, have full faith in the team, and remain loyal despite price volatility—because they use the chain and know there’s nothing better. 26. Check other chains’ active user counts on X (Twitter) and compare it with the followers of EGLD’s founders and main network accounts, versus those with 30x, 50x, or 100x larger market caps. 27. Visit the MultiversX website to observe the futuristic design and presentation, then compare it to other chains that appear nearly a decade behind in design and branding. 28. EGLD hosts the xDay Global event, showcasing updates, new builders, projects in the ecosystem, and major announcements—similar to Apple’s Keynotes—delivered in a highly professional, goosebump-inducing atmosphere. The next event is in Korea, the second-biggest crypto market after the US. Check out their previous xDay after-movie to see why this is extremely bullish. 29. EGLD is moving forward with plans for the first regulated, audited EU stablecoin under MiCa regulation, made possible by acquiring xMoney, which I view as a “Stripe” for crypto/fiat, offering everything from user solutions to merchant services—potentially the future of payments. 30. Greg Siourouni recently joined EGLD, having been an executive director at SUI Foundation. He’s now co-founder of xMoney Global. xMoney (formerly UTrust, with token UTK) is owned and founded by the MultiversX Labs team. A stablecoin might be introduced soon, which would be massively bullish given xMoney’s roadmap. They recently announced integrations with Binance Pay—both ways. 31. EGLD prioritizes user safety, believing it’s the only feasible approach once the network scales to serve a billion people—many of whom are retail users with little to no security awareness. 32. EGLD offers “Sovereign Chains,” letting you effectively clone their chain without heavy development, set up your own validators, and leverage their unlimited scalability. Any blockchain (ETH, BTC, SOL) struggling with scalability, decentralization, or security could run an ultra-fast, scalable, and secure L2 on EGLD’s Sovereign Chain, meeting top enterprise requirements. No one else has really done this. The Sovereign Chain demo achieved astonishing TPS and has an SDK. 33. No downtime since inception. 34. No shard takeover attacks have occurred. 35. Extremely fast—soon 600ms block time will be in place. 36. ESDTs – The best token standard available: fungible, non-fungible, semi-fungible, DeFi assets—everything is native and highly customizable. 37. Top-tier composability of assets and smart contracts. 38. Integrated DNS at protocol level with HeroTags (nicknames) instead of long addresses. 39. Asynchronous calls are supported. 40. Cross-shard transfers, execution, reverts, and calls are seamlessly integrated. 41. The best staking system in the space. Secure Proof of Stake (SPoS) is far more efficient than Proof of Work (PoW). 42. Built-in Delegation and Staking Provider system, with over 125K delegators. 43. Complete support for liquid staked assets, fostering decentralization rather than centralization. 44. TransferRoles for ESDT and other advanced operations. 45. Composable tasks on-chain for more sophisticated DeFi workflows. 46. MultiTransfer and asset execution within one transaction. 47. Re-entrancy protection is built-in by design. 48. Storage for ESDT assets goes beyond a linear approach, optimizing performance. 49. No integer overflows thanks to integrated safeMath operations. 50. Integrated crypto opcodes in the VM, enhancing security and performance. 51. Support for BigFloats, BigInts, and BigDecimals, enabling advanced financial calculations on-chain. 52. No sandwich attacks, plus front-running and MEV protection. 53. Relayed Transactions, simplifying user interactions and fees. 54. Smart Accounts featuring data tries and multiple built-in functions. 55. Generalized Paymaster solutions, enabling flexible fee models. 56. Subscriptions for recurring or automated on-chain payments. 57. Web2-like usability with Web3 functionality, bridging mainstream adoption. 58. StakingV4 for improved decentralization. 59. Enhanced MEV protection rolling out to safeguard users. 60. Parallel execution is coming soon, boosting throughput. 61. 1 million TPS is on the roadmap, targeted for demonstration. 62. 600ms block time is also coming soon. 63. Reduced cross-shard processing is planned to improve efficiency. 64. ZK everywhere (PI²): “prove everything” approach is coming. 65. AsyncV3 is in development for more complex cross-contract interactions. 66. Scalability enhancements for Merkle Tries or a new data model are being explored. 67. Linear storage on the VM is forthcoming. 68. A dynamic language interpreter at the VM is also planned. 69. Rumors suggest that MultiversX (EGLD) is building a “Truth Machine” on their L1—an essential, game-changing tool for AI verification and societal impact. 70. The entire team features individuals with PhDs in mathematics and physics, and many are former engineers at Google, IBM, and similar companies. 71. Over 56% of the network’s supply is staked, showcasing strong community involvement. 72. More than 6,772,347 accounts have been created on the network. 73. A total of 476,627,710 transactions have been processed on-chain without any outages or hacks. 74. EGLD has built a massive ecosystem over time. While not as numerous in project count as Solana, its market cap is ~100x smaller, yet it has far superior tokenomics and technology. The projects that do exist, like Hatom Protocol, are top-tier in UX, security, and advanced features. Hatom will soon introduce USH, a truly high-quality, decentralized stablecoin. 75. On competing chains, automated transactions aren’t easily or cheaply executed, whereas on MultiversX, tools like let you do this for free (with near-zero fees). 76. No other chain combines such a strong team and long-term vision where every product meets extreme security and UX standards like MultiversX does. This is why I see it as the “next Apple” in Web3. 77. MultiversX has a new CMO – Adam Bates, a former CMO at the Cardano Foundation. He was behind the success of Cardano’s huge marketing campaign and has a very good relationship with Charles Hoskinson. Thanks to him, Beniamin Mincu (the founder of MultiversX) was likely introduced, and now they will probably discuss how both blockchains can help each other, as well as any other potential collaborations we don’t yet know about. This is also extremely bullish. #EGLD is undeniably the most Scalable, Advanced, Secure, and User-friendly L1 supercomputer ever created. It’s built to SHAPE THE FUTURE. 1) 2) 3) 4) 5) 27/6/2024 - EGLDSqueeze - SUMMARY: HERE IS NO 2ND BEST. EGLD IS ONLY ONE BLOCKCHAIN THAT CAN RULE THEM ALL. ✅ UNLIMITED SCALING ✅ SCARCE AS BTC ✅ PROGRAMMABLE AS ETH ✅ NO DOWNTIME AS SOL ✅ UI/UX OF Apple ✅ SHARDING DONE BEFORE NEAR & TON ✅ BEST WALLET xPortal WITH GUARDIAN Price prediction (NFA|DYOR): My reasoning is that the real market cap as of December 23, 2024...if we take into account the value of other cryptocurrencies such as BTC, SOL, ETH, AVAX, NEAR, TON, Cardano, BNB, XRP, and so forth, plus the existence of meme coins with valuations above 20 billion USD, or even games nobody plays anymore that still have valuations above 800 million shows that EGLD’s current market cap of approximately 942 million USD is incredibly low. From a technological standpoint, user experience, and other relevant aspects, compared to SOL, NEAR, TON, AVAX, and other L1 protocols, EGLD’s market cap should realistically be around 100 billion USD. Therefore, my prediction and investment thesis is a minimum of a 100x increase from its current price (+-SOL marketcap). MultiversX is ready to onboard 1 billion people to the blockchain. From a long-term perspective, it could even reach a market cap of 1 trillion USD, which is roughly half of where BTC is right now. That would be approximately a 1060x gain from the current market cap. 1 EGLD (MultiversX) is for $34 (only 31.4M max supply) think about this. Not financial advice. Again. There is no 2nd best L1. Position yourself where the puck is going, then wait at the goal until the goal gets there Apes together, strong. Ape alone, weak. We Don't Worry. We Just Win. Shape The Future

Daniel Veroc

50,133 次观看 • 1 年前

$AMD is easily a $1,200 stock IMO| CPUs TAM 🧵 Not Financial Advice! DYOR! In this thread, I want to discuss the actual TAM for CPUs data center for just 2026, where many are giving different ranges, where I don't agree with. I will explain in detail why I disagree with these research firms and financial analysts using Math. And this thread should not be treated as Financial Advice. I'm just explaining my research and thought process so we can have a discussion. In 2024/2025, I gave out $620 PT for FY2026 was too conservative for AMD potential. At the time, It was early and many were just laughing, that PT was unrealistic and the AI world is run on GPUs only. Today, most of these folks are laughing with me. That is ok, I dont offer financial advice, and I do not need everyone to agree with me. I respect other opinions. If you enjoy this kind of thread, slap the like/repost/bookmark. If you want to support my work further and gain more in-depth analysis, consider subscribe! In early 2026, hyperscalers, enterprises, and OEMs are scrambling as Intel and AMD server CPUs are largely sold out for the year, with prices jumping 10–20% and lead times stretching from weeks to months (or longer for certain SKUs). What was once a GPU dominated story has flipped: the shift to explosive Agentic AI with its multi-step reasoning loops, tool calling, multi-agent orchestration, real-time data movement, and reinforcement learning, is dramatically tightening CPU:GPU ratios from the old training-era 1:4–8 all the way to 1:1 to 5:1 or even CPU-heavy configurations. CEOs across NVIDIA, AMD, Intel, Google, Meta, Microsoft, and public companies have been sounding the alarm on CNBC, Bloomberg, and earnings calls. CPUs are “cool again,” and in many agentic deployments they are becoming the new bottleneck alongside (or even ahead of) GPUs and custom ASICs. In 2025, roughly 12-15m AI GPUs + AI ASICs GPUs shipped, and is expect to be 15-20m units by 2026, where it suggesting Training demand is not going away. The actual TAM is structural, multiplicative demand that has already forced AMD to double its long-term server CPU TAM forecast to >$120 billion by 2030 (>35% CAGR), with Dr. Lisa Su noting Q2 2026 server CPU sales expected to surge 70%+ year-over-year and demand “far exceeding expectations.” At the same time, AMD’s secured 30–40% share of TSMC’s initial 2nm capacity (behind only Apple’s >50%) positions it to ramp Zen 6-based EPYC Venice exactly when this agentic wave hits hardest but even that aggressive five-fab 2nm expansion (with plans scaling toward 11 total advanced facilities) cannot instantly close the gap in the near-term. Supply constraints on wafers, advanced packaging, and power are compounding the squeeze, just as hyperscalers forward-buy and lock in long-term deals. 1. The actual potential TAM Various sources and institutions are giving $50-$160-$200B CPUs TAM toward 2030, and i disagree, where supply is severely behind vs Demand by at least 2-3 years or even longer by some estimates. The actual TAM will probably be 15-20m for FY2026. The typical average selling price from low to high end is $5,000 to $15,000, but due to rising memory, and different inflationary pressures on Semi, it would be more logical to think between $7,000-17,000. A. CPU:GPU Ratio at 1:1 A basic calucation at mid range =12,000 x 15-20m CPUs= $180-$240B TAM B. CPU:GPU Ratio at 5:1 = $12,000 x 75m-100m CPUs= $900B-$1.2T TAM Of course TSMC cannot even supply 20% of this massive inflection TAM in 2026. But do we think of Demand for TAM or Supply for TAM? Hence we are seeing massive 2nm Ramp from TSMC for $AMD. IMO, conservatively, I would take down 15-20% on 1:1 or $135-$192B TAM for just 2026. Im not even talking about 2030. We are just months into this, it is impossible to estimate Cagr atm, but this is 1-5 agents running tasks, I wrote a thread on 24/7 autonomous agents thread, where companies could use 50-250 agents to run tasks for them 24/7. It would require a different structural CPU:GPU to bring down the cost of token as well as handling the Orchestration bottleneck. GPUs would be useless and sit idle waiting for CPU due to highly CPU-intensive nature. The cost per Million tokens must come down more rapidly for this 50-250 autonomous agents to work, otherwise the token cost would be too enormous. Helios Rack is estimated to bring inference cost down to $0.0003-$0.0005/M tokens with 18 EPYC Venices along with 72 MI455x and other chips+ Components. A heavier or CPUs dense rack would bring down inference cost further. EPYC Verano(2027 gen 7 AI-optimized) is expected to drive inference costs meaningfully lower than the Venice baseline likely to the $0.00002–$0.00025 per million tokens range (or even sub-$0.00015 in highly optimized agentic/batch workloads). Verano have higher core counts than Venice, LPDDR5X SOCAMM2 memory support, more AI optimized and Next-Gen rack density & efficiency. 2. $AMD secured at least 30-40% of TSMC 2nm capacity and Memory from Samsung through 2028-2030. 2 2nm fabs are entering ramping phase toward 60-65k wafers per months and 5 dedicated 2nm fabs entering mass production/ramp in 2026. Will link sub threads below if you are interest for full detail. Apple is reported to secure 50%+ 2nm capacity for Iphone 18 and Mac chips and AMD secured at least 30-40% capacity while $NVDA $AVGO $ARM $AMZN $GOOGL and others are on 3nm. This broader aggressive ramp from TSMC to target up to 11 fabs is to address $AMD massive growth ahead. Where $ARM is facing massive CPUs supply constraints as they have to compete with other Mega Cap players on 3nm allocation. And $INTC is also facing supply constraints for data center CPUs and PC per management with lead times extrended to longer than 12 weeks. Dr. Su is aiming for higher than 50%+ Market share, and I believe it is achievable in 2026 or 2027 as AMD has the strongest CPUs offerings. Dr. Su did not want to take advantage of the shortage and she said during the Q1 earning call, AMD is prioritizing Units shipped while guiding margin to be inching 60%. If Jensen were in charge, I'm sure margin would be 70-75% in this kind of severe CPUs shortage condition. But that is not how Dr. Su operates for more than a decade. She wants most market share. So we will see it in revenue growth, but as TSMC ramps faster and faster, AMD Operating and FCF margin will massively improve vs prior decade. A significantly higher margin profile than before. 3. How I came up with $1,200 withint 12-18 months? At $1,200/ share, that would be around $2 Trillion MC. I expect FY2027 revenue to be $124-$144B where data center revenue dominates overall revenue. AI GPUs: I will stick to the lowest end so show u that I'm conservative at $18B for each GW vs $NVDA Rubin is $30B+ (most likely Helios Rack in the $20B+ due to memory price rising). We know deals with OpenAI and Meta are around 12GW and additional multi-customers at multi-GW scale were hinted and will be revealed as we get to July 22-23 2026 Advancing AI event. For now I will conservatively add a bit more to this model. (3-6GW Helios Rack Range) EPYC Venice is reported to be in $15,000-$20,000. However large customers will likely to enjoy $10-$12k discount. I expect AMD to be able to ramp 7m EPYC Venice for entire 2026 and 3-4m of EPYC Verano(higher price than Venice). If we take an average selling price of $10,000 to be on the conservative side. Take down another 30% to be even more conservative on projection. I like to be conservative. That would be ~ 7m EPYC CPUs(Venice + Verano) for FY2027 or 583,000 units per month or 15,000 additional 2nm wafers per month which is completely reasonable for current TSMC Ramp, and I may be too conservative here. EPYC Verano and MI500 series will also be on 2nm. AI GPUs: 3GW x $18B= $54B EPYC CPUs: $10k x 7m CPUs= $70B = Data center revenue alone is $124B Other segments= probably in the $20-$25B FY 2027. FY2027 revenue = $124-$149B At 7m EPYC CPUs for entire 2027, that would be more than 50% market share when we comp it to availability from supply side, not from total Demand. It is possible that TSMC could significantly ramp even more capacity in 2027, so we will see. Metric Q1 2026 FY2027 Gross Margin 55-56% 60-62% Operating Margin 25-26% 32-35% Net Income Margin ~22% 26-30% FCF Margin 25% 28-30% At $124-$149B Revenue FY 2027 Net Income would be $32-$44B EPS would be $20-$27 (GAAP) Non-GAAP would be $25-$31 At $1,200 a share or $2T valuation that would be: 13.4-16x Price to Sales (P/S) 38-48 P/E At this kind of growth of AI SuperCycle, I think it is very reasonable valuation. If we use today at $406/share or $661B MC: 2027 P/S = 4.4x-5.3x 2027 P/E = 13x-16x Is AMD today expensive or cheap to you? Above is already a very conservative where I trimmed 20-30% of doable units. Meaning, there could be upside if TSMC is able to ramp meaningfully like they are planning. Conclusion: A $1,200 per share valuation IMO for AMD in FY2027 is not expensive at all; it is, in fact, conservative when viewed against the structural explosion in agentic AI demand we have mapped out. With server CPU TAM potentially scaling into the $100–$200B+ range in just CPU:GPU 1:1 Ratio for just 2026. AMD positioned to capture 50%+ share thanks to its 2nm TSMC allocation advantage and full-stack leadership, the company could realistically deliver $124–149B in total revenue and $25–$31+ non-GAAP EPS. At those levels, $1,200 implies a 2027 P/E = 13x-16x. Entirely reasonable for a company that will have become the clear Inference Queen (and in many workloads the preferred) AI infrastructure provider, with operating margins expanding above 30% and tens of billions in high-margin rack-scale AI revenue. Dr. Lisa Su was right presciently so about the Agentic AI inflection all the way back to her early 2022–2023 commentary on the coming shift from pure training to inference and orchestration-heavy workloads. While the broader market only fully woke up to this in 2026 when she doubled AMD’s long-term server CPU TAM forecast to >$120B by 2030 (with >35% CAGR), Dr. Su and her team have consistently positioned the company at the center of the CPU renaissance. The explosive demand we are seeing today, sold-out lines, rising ASPs, and hyperscalers forward-buying entire gigawatts of Helios-class systems is exactly the outcome she forecasted years ago. Not Financial Advice! DYOR!
13:03

$AMD is easily a $1,200 stock IMO| CPUs TAM 🧵 Not Financial Advice! DYOR! In this thread, I want to discuss the actual TAM for CPUs data center for just 2026, where many are giving different ranges, where I don't agree with. I will explain in detail why I disagree with these research firms and financial analysts using Math. And this thread should not be treated as Financial Advice. I'm just explaining my research and thought process so we can have a discussion. In 2024/2025, I gave out $620 PT for FY2026 was too conservative for AMD potential. At the time, It was early and many were just laughing, that PT was unrealistic and the AI world is run on GPUs only. Today, most of these folks are laughing with me. That is ok, I dont offer financial advice, and I do not need everyone to agree with me. I respect other opinions. If you enjoy this kind of thread, slap the like/repost/bookmark. If you want to support my work further and gain more in-depth analysis, consider subscribe! In early 2026, hyperscalers, enterprises, and OEMs are scrambling as Intel and AMD server CPUs are largely sold out for the year, with prices jumping 10–20% and lead times stretching from weeks to months (or longer for certain SKUs). What was once a GPU dominated story has flipped: the shift to explosive Agentic AI with its multi-step reasoning loops, tool calling, multi-agent orchestration, real-time data movement, and reinforcement learning, is dramatically tightening CPU:GPU ratios from the old training-era 1:4–8 all the way to 1:1 to 5:1 or even CPU-heavy configurations. CEOs across NVIDIA, AMD, Intel, Google, Meta, Microsoft, and public companies have been sounding the alarm on CNBC, Bloomberg, and earnings calls. CPUs are “cool again,” and in many agentic deployments they are becoming the new bottleneck alongside (or even ahead of) GPUs and custom ASICs. In 2025, roughly 12-15m AI GPUs + AI ASICs GPUs shipped, and is expect to be 15-20m units by 2026, where it suggesting Training demand is not going away. The actual TAM is structural, multiplicative demand that has already forced AMD to double its long-term server CPU TAM forecast to >$120 billion by 2030 (>35% CAGR), with Dr. Lisa Su noting Q2 2026 server CPU sales expected to surge 70%+ year-over-year and demand “far exceeding expectations.” At the same time, AMD’s secured 30–40% share of TSMC’s initial 2nm capacity (behind only Apple’s >50%) positions it to ramp Zen 6-based EPYC Venice exactly when this agentic wave hits hardest but even that aggressive five-fab 2nm expansion (with plans scaling toward 11 total advanced facilities) cannot instantly close the gap in the near-term. Supply constraints on wafers, advanced packaging, and power are compounding the squeeze, just as hyperscalers forward-buy and lock in long-term deals. 1. The actual potential TAM Various sources and institutions are giving $50-$160-$200B CPUs TAM toward 2030, and i disagree, where supply is severely behind vs Demand by at least 2-3 years or even longer by some estimates. The actual TAM will probably be 15-20m for FY2026. The typical average selling price from low to high end is $5,000 to $15,000, but due to rising memory, and different inflationary pressures on Semi, it would be more logical to think between $7,000-17,000. A. CPU:GPU Ratio at 1:1 A basic calucation at mid range =12,000 x 15-20m CPUs= $180-$240B TAM B. CPU:GPU Ratio at 5:1 = $12,000 x 75m-100m CPUs= $900B-$1.2T TAM Of course TSMC cannot even supply 20% of this massive inflection TAM in 2026. But do we think of Demand for TAM or Supply for TAM? Hence we are seeing massive 2nm Ramp from TSMC for $AMD. IMO, conservatively, I would take down 15-20% on 1:1 or $135-$192B TAM for just 2026. Im not even talking about 2030. We are just months into this, it is impossible to estimate Cagr atm, but this is 1-5 agents running tasks, I wrote a thread on 24/7 autonomous agents thread, where companies could use 50-250 agents to run tasks for them 24/7. It would require a different structural CPU:GPU to bring down the cost of token as well as handling the Orchestration bottleneck. GPUs would be useless and sit idle waiting for CPU due to highly CPU-intensive nature. The cost per Million tokens must come down more rapidly for this 50-250 autonomous agents to work, otherwise the token cost would be too enormous. Helios Rack is estimated to bring inference cost down to $0.0003-$0.0005/M tokens with 18 EPYC Venices along with 72 MI455x and other chips+ Components. A heavier or CPUs dense rack would bring down inference cost further. EPYC Verano(2027 gen 7 AI-optimized) is expected to drive inference costs meaningfully lower than the Venice baseline likely to the $0.00002–$0.00025 per million tokens range (or even sub-$0.00015 in highly optimized agentic/batch workloads). Verano have higher core counts than Venice, LPDDR5X SOCAMM2 memory support, more AI optimized and Next-Gen rack density & efficiency. 2. $AMD secured at least 30-40% of TSMC 2nm capacity and Memory from Samsung through 2028-2030. 2 2nm fabs are entering ramping phase toward 60-65k wafers per months and 5 dedicated 2nm fabs entering mass production/ramp in 2026. Will link sub threads below if you are interest for full detail. Apple is reported to secure 50%+ 2nm capacity for Iphone 18 and Mac chips and AMD secured at least 30-40% capacity while $NVDA $AVGO $ARM $AMZN $GOOGL and others are on 3nm. This broader aggressive ramp from TSMC to target up to 11 fabs is to address $AMD massive growth ahead. Where $ARM is facing massive CPUs supply constraints as they have to compete with other Mega Cap players on 3nm allocation. And $INTC is also facing supply constraints for data center CPUs and PC per management with lead times extrended to longer than 12 weeks. Dr. Su is aiming for higher than 50%+ Market share, and I believe it is achievable in 2026 or 2027 as AMD has the strongest CPUs offerings. Dr. Su did not want to take advantage of the shortage and she said during the Q1 earning call, AMD is prioritizing Units shipped while guiding margin to be inching 60%. If Jensen were in charge, I'm sure margin would be 70-75% in this kind of severe CPUs shortage condition. But that is not how Dr. Su operates for more than a decade. She wants most market share. So we will see it in revenue growth, but as TSMC ramps faster and faster, AMD Operating and FCF margin will massively improve vs prior decade. A significantly higher margin profile than before. 3. How I came up with $1,200 withint 12-18 months? At $1,200/ share, that would be around $2 Trillion MC. I expect FY2027 revenue to be $124-$144B where data center revenue dominates overall revenue. AI GPUs: I will stick to the lowest end so show u that I'm conservative at $18B for each GW vs $NVDA Rubin is $30B+ (most likely Helios Rack in the $20B+ due to memory price rising). We know deals with OpenAI and Meta are around 12GW and additional multi-customers at multi-GW scale were hinted and will be revealed as we get to July 22-23 2026 Advancing AI event. For now I will conservatively add a bit more to this model. (3-6GW Helios Rack Range) EPYC Venice is reported to be in $15,000-$20,000. However large customers will likely to enjoy $10-$12k discount. I expect AMD to be able to ramp 7m EPYC Venice for entire 2026 and 3-4m of EPYC Verano(higher price than Venice). If we take an average selling price of $10,000 to be on the conservative side. Take down another 30% to be even more conservative on projection. I like to be conservative. That would be ~ 7m EPYC CPUs(Venice + Verano) for FY2027 or 583,000 units per month or 15,000 additional 2nm wafers per month which is completely reasonable for current TSMC Ramp, and I may be too conservative here. EPYC Verano and MI500 series will also be on 2nm. AI GPUs: 3GW x $18B= $54B EPYC CPUs: $10k x 7m CPUs= $70B = Data center revenue alone is $124B Other segments= probably in the $20-$25B FY 2027. FY2027 revenue = $124-$149B At 7m EPYC CPUs for entire 2027, that would be more than 50% market share when we comp it to availability from supply side, not from total Demand. It is possible that TSMC could significantly ramp even more capacity in 2027, so we will see. Metric Q1 2026 FY2027 Gross Margin 55-56% 60-62% Operating Margin 25-26% 32-35% Net Income Margin ~22% 26-30% FCF Margin 25% 28-30% At $124-$149B Revenue FY 2027 Net Income would be $32-$44B EPS would be $20-$27 (GAAP) Non-GAAP would be $25-$31 At $1,200 a share or $2T valuation that would be: 13.4-16x Price to Sales (P/S) 38-48 P/E At this kind of growth of AI SuperCycle, I think it is very reasonable valuation. If we use today at $406/share or $661B MC: 2027 P/S = 4.4x-5.3x 2027 P/E = 13x-16x Is AMD today expensive or cheap to you? Above is already a very conservative where I trimmed 20-30% of doable units. Meaning, there could be upside if TSMC is able to ramp meaningfully like they are planning. Conclusion: A $1,200 per share valuation IMO for AMD in FY2027 is not expensive at all; it is, in fact, conservative when viewed against the structural explosion in agentic AI demand we have mapped out. With server CPU TAM potentially scaling into the $100–$200B+ range in just CPU:GPU 1:1 Ratio for just 2026. AMD positioned to capture 50%+ share thanks to its 2nm TSMC allocation advantage and full-stack leadership, the company could realistically deliver $124–149B in total revenue and $25–$31+ non-GAAP EPS. At those levels, $1,200 implies a 2027 P/E = 13x-16x. Entirely reasonable for a company that will have become the clear Inference Queen (and in many workloads the preferred) AI infrastructure provider, with operating margins expanding above 30% and tens of billions in high-margin rack-scale AI revenue. Dr. Lisa Su was right presciently so about the Agentic AI inflection all the way back to her early 2022–2023 commentary on the coming shift from pure training to inference and orchestration-heavy workloads. While the broader market only fully woke up to this in 2026 when she doubled AMD’s long-term server CPU TAM forecast to >$120B by 2030 (with >35% CAGR), Dr. Su and her team have consistently positioned the company at the center of the CPU renaissance. The explosive demand we are seeing today, sold-out lines, rising ASPs, and hyperscalers forward-buying entire gigawatts of Helios-class systems is exactly the outcome she forecasted years ago. Not Financial Advice! DYOR!

Mike

301,322 次观看 • 2 个月前