Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Qwen-Code weekly release (v0.0.8) : ✨ Deep VS Code Integration: Get context-aware suggestions & inline diffs directly in your editor! Initialize with /ide and supercharge your workflow. 🔌 Enhanced MCP Support: Add, remove, list MCP servers via CLI (qwen mcp add|remove|list), plus support for MCP roots & multimodal tool...

Alibaba_Qwen's profile picture

Qwen

225,183 subscribers

127,499 Aufrufe • vor 11 Monaten •via X (Twitter)

Wissenschaft & TechnologieBildungKunst
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

🚀 Exciting updates in Qwen Code v0.0.12–v0.0.14! ✨ What’s new? • Plan Mode: AI proposes a full implementation plan—you approve before a single line changes. • Vision Intelligence: Auto-switch to vision models (Qwen3-VL-Plus with 256K input / 32K output!) when images appear—even in YOLO mode. • Zed Integration: Now supports both OpenAI & Qwen OAuth auth. • More control: Toggle loop detection, confirm overwrites, and fine-tune your workflow. 🔧 Under the hood: • Fixed multi-line paste on Windows • Resolved Zed auth hang with Qwen OAuth • Corrected malformed tool calls & output token limits • Improved subagent performance & UI • Fixed Markdown list rendering on Windows • Removed buggy editCorrector injecting escape chars • Enabled high-res image support for Qwen3-VL-Plus • Fixed ripgrep loading & TaskTool sync issues 💻Qwen Code:
0:24

🚀 Exciting updates in Qwen Code v0.0.12–v0.0.14! ✨ What’s new? • Plan Mode: AI proposes a full implementation plan—you approve before a single line changes. • Vision Intelligence: Auto-switch to vision models (Qwen3-VL-Plus with 256K input / 32K output!) when images appear—even in YOLO mode. • Zed Integration: Now supports both OpenAI & Qwen OAuth auth. • More control: Toggle loop detection, confirm overwrites, and fine-tune your workflow. 🔧 Under the hood: • Fixed multi-line paste on Windows • Resolved Zed auth hang with Qwen OAuth • Corrected malformed tool calls & output token limits • Improved subagent performance & UI • Fixed Markdown list rendering on Windows • Removed buggy editCorrector injecting escape chars • Enabled high-res image support for Qwen3-VL-Plus • Fixed ripgrep loading & TaskTool sync issues 💻Qwen Code:

Qwen

156,614 Aufrufe • vor 9 Monaten

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,134 Aufrufe • vor 3 Monaten

Introducing the new Box Agent. The Box Agent works across your entire Box file system, maintaining all your security and access controls, and is hyper tuned for working with enterprise content. This means you can now ask questions from all your enterprise content, search for files that were impossible to find before, deploy an agent on specific tasks on subsets of documents, analyze complex data sets, and generate or edit documents and spreadsheets via the agent. You can have the Box Agent search across your Box account to prepare for a sales meeting, analyze customer sentiment reports, process a large set of contracts for legal risk, provide insights into product development, leverage existing knowledge to answer RFPs, and thousands of other use-cases. 90% of enterprise data is unstructured data. This means most enterprise knowledge is sitting in inside of research reports, marketing assets, presentations, roadmap files, contracts, HR documents, and more. This is the critical context that agents need to be able to answer questions about a business, automate workflows, or serve up to other agents. We’ve been grinding on this for a quite a bit, and due to recent AI model advancements we’re now ready to release it to customers. Previous model generations had a difficult time knowing when to give up or keep going on a search, when to browse for files vs. use queries, how to rank files appropriately to know which version of content to use, how to handle large amounts of context to comb through, and more. Due to recent breakthroughs from models like GPT-5.4, Opus 4.6, and Gemini 3, we’ve seen major gains in tool calling, code execution, advanced reasoning, and more. Combined with an agent harness tuned to Box context, now it’s finally possible to have an agent that can work across your file system on long running tasks and actually deliver high quality results. Best of all, because the Box Agent works with any leading AI model, you’ll quickly get the gains coming out of the major labs as major new models are released. Further, openness at Box is key, so you’ll be able to call up the Box Agent from Box’s APIs and MCP server, so you can interact with Box intelligently from any other AI system. We know work happens everywhere, and we want to ensure you can access to the content you need from those places. The new Box Agent is available starting today, rolling out now for Enterprise Plus and Enterprise Advanced customers.
0:58

Introducing the new Box Agent. The Box Agent works across your entire Box file system, maintaining all your security and access controls, and is hyper tuned for working with enterprise content. This means you can now ask questions from all your enterprise content, search for files that were impossible to find before, deploy an agent on specific tasks on subsets of documents, analyze complex data sets, and generate or edit documents and spreadsheets via the agent. You can have the Box Agent search across your Box account to prepare for a sales meeting, analyze customer sentiment reports, process a large set of contracts for legal risk, provide insights into product development, leverage existing knowledge to answer RFPs, and thousands of other use-cases. 90% of enterprise data is unstructured data. This means most enterprise knowledge is sitting in inside of research reports, marketing assets, presentations, roadmap files, contracts, HR documents, and more. This is the critical context that agents need to be able to answer questions about a business, automate workflows, or serve up to other agents. We’ve been grinding on this for a quite a bit, and due to recent AI model advancements we’re now ready to release it to customers. Previous model generations had a difficult time knowing when to give up or keep going on a search, when to browse for files vs. use queries, how to rank files appropriately to know which version of content to use, how to handle large amounts of context to comb through, and more. Due to recent breakthroughs from models like GPT-5.4, Opus 4.6, and Gemini 3, we’ve seen major gains in tool calling, code execution, advanced reasoning, and more. Combined with an agent harness tuned to Box context, now it’s finally possible to have an agent that can work across your file system on long running tasks and actually deliver high quality results. Best of all, because the Box Agent works with any leading AI model, you’ll quickly get the gains coming out of the major labs as major new models are released. Further, openness at Box is key, so you’ll be able to call up the Box Agent from Box’s APIs and MCP server, so you can interact with Box intelligently from any other AI system. We know work happens everywhere, and we want to ensure you can access to the content you need from those places. The new Box Agent is available starting today, rolling out now for Enterprise Plus and Enterprise Advanced customers.

Aaron Levie

44,515 Aufrufe • vor 3 Monaten

Claude Code cannot read 300 files at once. So someone built a system that lets it control NotebookLM from the terminal instead. The results are wild. Here is the full workflow nobody is talking about: The Setup → Claude Code connects to NotebookLM via a command line interface → Claude searches YouTube, finds relevant videos, uploads them as sources automatically → NotebookLM processes up to 300 sources simultaneously and returns cited, grounded answers → Everything syncs back into your Obsidian vault with passage-level citations you can click to verify Why This Changes Research Forever → No more 20 browser tabs you never close → No more copy-pasting outputs into random notes → No more hallucinated answers with no sources to back them up → 60% of citations verified as strong matches in accuracy audits - answers are grounded in real data What Claude Can Do From the Terminal → Search YouTube for relevant videos on any topic and rank by relevance → Create a new NotebookLM notebook and add 20 sources in parallel automatically → Ask questions and export cited answers directly into Obsidian with wikilinks → Set custom personas per notebook - concise, no filler, no preamble → Generate audio overviews and save them as MP3 files into your vault → Build mind maps, flashcard decks, and research dashboards from your sources → Search arXiv for academic papers and feed them directly into NotebookLM → Upload competitor blog posts, podcast episodes, PDFs, and your own vault notes The Obsidian Output → Every answer arrives with clickable citations that link to the exact passage in the source video or article → Graph view shows connections between all 20 sources and the topics they share → Q&A log tracks every question asked and the grounded response received → Source dashboard shows citation frequency, topics extracted, and which questions each source answered Use Cases Worth Building Today → Academic research with arXiv papers, full citation traceability → Competitor analysis from their YouTube channels and blog posts → Company knowledge base for onboarding, new employees ask NotebookLM instead of interrupting teammates → Podcast research, feed 4-hour Lex Fridman episodes and ask what's new in AI this week → Personal second brain, 300 daily notes uploaded and queryable in one notebook Before this system existed you needed 20 tabs, hours of manual reading, and no guarantee the answers were real. Now you type one prompt in the terminal and Claude does all of it for you. The research stack of 2026 is not a browser. It is a terminal connected to everything
32:50

Claude Code cannot read 300 files at once. So someone built a system that lets it control NotebookLM from the terminal instead. The results are wild. Here is the full workflow nobody is talking about: The Setup → Claude Code connects to NotebookLM via a command line interface → Claude searches YouTube, finds relevant videos, uploads them as sources automatically → NotebookLM processes up to 300 sources simultaneously and returns cited, grounded answers → Everything syncs back into your Obsidian vault with passage-level citations you can click to verify Why This Changes Research Forever → No more 20 browser tabs you never close → No more copy-pasting outputs into random notes → No more hallucinated answers with no sources to back them up → 60% of citations verified as strong matches in accuracy audits - answers are grounded in real data What Claude Can Do From the Terminal → Search YouTube for relevant videos on any topic and rank by relevance → Create a new NotebookLM notebook and add 20 sources in parallel automatically → Ask questions and export cited answers directly into Obsidian with wikilinks → Set custom personas per notebook - concise, no filler, no preamble → Generate audio overviews and save them as MP3 files into your vault → Build mind maps, flashcard decks, and research dashboards from your sources → Search arXiv for academic papers and feed them directly into NotebookLM → Upload competitor blog posts, podcast episodes, PDFs, and your own vault notes The Obsidian Output → Every answer arrives with clickable citations that link to the exact passage in the source video or article → Graph view shows connections between all 20 sources and the topics they share → Q&A log tracks every question asked and the grounded response received → Source dashboard shows citation frequency, topics extracted, and which questions each source answered Use Cases Worth Building Today → Academic research with arXiv papers, full citation traceability → Competitor analysis from their YouTube channels and blog posts → Company knowledge base for onboarding, new employees ask NotebookLM instead of interrupting teammates → Podcast research, feed 4-hour Lex Fridman episodes and ask what's new in AI this week → Personal second brain, 300 daily notes uploaded and queryable in one notebook Before this system existed you needed 20 tabs, hours of manual reading, and no guarantee the answers were real. Now you type one prompt in the terminal and Claude does all of it for you. The research stack of 2026 is not a browser. It is a terminal connected to everything

Dami-Defi

252,693 Aufrufe • vor 1 Monat

😱 How to Build & Launch Your Base Mini App in 10Mins. ■ Investment: 0$ ( Free of Cost ) ■ Potential: $BASE ■ Exprience: No coding experience needed ( anyone can build ) 👀 Just watch full video & follow my simple 9 steps & Boom : Tools : 1.) Create V0 account :- 2.) Create Farcaster Account :- 3.) Create Baseapp Account :- •• Must link your farcaster account in base app Step 1 : Create the Calculator Application - Built a functional calculator with add, subtract, multiply, and divide operations - - Creat `/components/calculator.tsx` with full calculator logic and UI - - Creat `/app/page.tsx` as the main entry point - - Use React hooks (useState) for state management - - Designe with a modern dark theme using Tailwind CSS - Step 2 : Deploy the project & copy the url & save it . Step 3 : Create the Farcaster Manifest File - Created `/public/.well-known/farcaster.json` - This file tells Base about our app - Configured app metadata: My project name : My url link : { "accountAssociation": { "header": "", "payload": "", "signature": "" }, "miniapp": { "version": "1", "name": "My project name", "subtitle": "Fast & Easy Math", "description": "A simple calculator for basic arithmetic operations", "homeUrl": " "iconUrl": " "splashImageUrl": " "splashBackgroundColor": "#1a1a1a", "screenshotUrls": [ " " ], "primaryCategory": "utility", "tags": ["calculator", "math", "utility"], "tagline": "Calculate Instantly", "heroImageUrl": " "ogTitle": "Calculator", "ogDescription": "A simple calculator for basic math", "ogImageUrl": " "noindex": false } } Step 4 : Added Required Images - i attach a image , so convert that image as required ratio and attach the same image in our mini app for all 3 forms . `● icon.png` (300×300px) - A small icon of your app ● splash.png (200×200px) - A splash screen image ● screenshot.png (1284×2778px) - A screenshot showing how the app looks Step 5 Added Embed Metadata - Add `fc:miniapp` meta tag to layout.tsx metadata - Configure embed preview with: - Image URL for the 3:2 aspect ratio preview - Button configuration ("Open Calculator") - Launch frame settings - Splash image and background color Step 6: Added Farcaster Miniapp SDK Integration - Install `@farcaster/miniapp-sdk` package (automatically included) - Update `/app/page.tsx` to import and use the SDK - Call `sdk.actions.ready()` when the app loads - This is the **critical step** that tells Base to hide the splash screen and display your calculator Step 7: Update Next.js Configuration - Update `/next.config.mjs` to work with Next.js 16's Turbopack - Add `turbopack: {}` config to ensure clean builds - Remove webpack-specific configurations Step8 : •• Now for one time , click on deploy & deploy again •• Then Open Farcaster in Pc/Laptop •• Enable Developer Mode •• go to Developer section then & click on Mini app manifest tools •• then paste url ( check vidoe ) •• then click on fetch & then click on Genrate account association •• scan qr code and verify your farcaster account •• Now copy everything and paste in V0 ( add prompt ) Add this as account association •• then Reverify and Submit . Step9 : ● Download Base App : •• Create Account with email •• then connect same farcaster account ● Then Visit : •• signin with same base app email . •• and follow video process 📌📌 Join Our TG for More Alpha:-
26:00

😱 How to Build & Launch Your Base Mini App in 10Mins. ■ Investment: 0$ ( Free of Cost ) ■ Potential: $BASE ■ Exprience: No coding experience needed ( anyone can build ) 👀 Just watch full video & follow my simple 9 steps & Boom : Tools : 1.) Create V0 account :- 2.) Create Farcaster Account :- 3.) Create Baseapp Account :- •• Must link your farcaster account in base app Step 1 : Create the Calculator Application - Built a functional calculator with add, subtract, multiply, and divide operations - - Creat `/components/calculator.tsx` with full calculator logic and UI - - Creat `/app/page.tsx` as the main entry point - - Use React hooks (useState) for state management - - Designe with a modern dark theme using Tailwind CSS - Step 2 : Deploy the project & copy the url & save it . Step 3 : Create the Farcaster Manifest File - Created `/public/.well-known/farcaster.json` - This file tells Base about our app - Configured app metadata: My project name : My url link : { "accountAssociation": { "header": "", "payload": "", "signature": "" }, "miniapp": { "version": "1", "name": "My project name", "subtitle": "Fast & Easy Math", "description": "A simple calculator for basic arithmetic operations", "homeUrl": " "iconUrl": " "splashImageUrl": " "splashBackgroundColor": "#1a1a1a", "screenshotUrls": [ " " ], "primaryCategory": "utility", "tags": ["calculator", "math", "utility"], "tagline": "Calculate Instantly", "heroImageUrl": " "ogTitle": "Calculator", "ogDescription": "A simple calculator for basic math", "ogImageUrl": " "noindex": false } } Step 4 : Added Required Images - i attach a image , so convert that image as required ratio and attach the same image in our mini app for all 3 forms . `● icon.png` (300×300px) - A small icon of your app ● splash.png (200×200px) - A splash screen image ● screenshot.png (1284×2778px) - A screenshot showing how the app looks Step 5 Added Embed Metadata - Add `fc:miniapp` meta tag to layout.tsx metadata - Configure embed preview with: - Image URL for the 3:2 aspect ratio preview - Button configuration ("Open Calculator") - Launch frame settings - Splash image and background color Step 6: Added Farcaster Miniapp SDK Integration - Install `@farcaster/miniapp-sdk` package (automatically included) - Update `/app/page.tsx` to import and use the SDK - Call `sdk.actions.ready()` when the app loads - This is the **critical step** that tells Base to hide the splash screen and display your calculator Step 7: Update Next.js Configuration - Update `/next.config.mjs` to work with Next.js 16's Turbopack - Add `turbopack: {}` config to ensure clean builds - Remove webpack-specific configurations Step8 : •• Now for one time , click on deploy & deploy again •• Then Open Farcaster in Pc/Laptop •• Enable Developer Mode •• go to Developer section then & click on Mini app manifest tools •• then paste url ( check vidoe ) •• then click on fetch & then click on Genrate account association •• scan qr code and verify your farcaster account •• Now copy everything and paste in V0 ( add prompt ) Add this as account association •• then Reverify and Submit . Step9 : ● Download Base App : •• Create Account with email •• then connect same farcaster account ● Then Visit : •• signin with same base app email . •• and follow video process 📌📌 Join Our TG for More Alpha:-

Sanu Gupta

40,411 Aufrufe • vor 5 Monaten

10 free Google AI tools nobody talks about. while everyone's burning $20/mo on chatgpt and claude, google quietly shipped a stack worth $200+/mo. all free. all yours. — 1️⃣ NotebookLM — your second brain upload sources (PDFs, websites, audio, YouTube). it summarizes, builds mind maps, generates quizzes, drafts slide decks, even turns your notes into a podcast you can listen to on a walk. free tier: 100 notebooks, 50 sources each, 50 chats/day, 3 audio overviews/day. replaces: notion AI + perplexity + readwise — 2️⃣ Google AI Studio — the free gemini playground web playground for gemini 3 pro and flash with a free API key. generous limits. paste a 1M-token context window and watch it actually use it. faster than the openai playground and free where openai charges per token. replaces: openai playground + paid API credits — 3️⃣ Gemini CLI — google's open-source terminal agent apache 2.0 licensed. one command (npx @google/gemini-cli) and you've got an agent in your terminal that reads your codebase, runs shell commands, and ships PRs. drop-in claude code alternative. replaces: claude code ($20/mo by default) — 4️⃣ Jules — async coding agent assign jules a github issue. it spins up a cloud VM, clones your repo, writes the plan, makes the changes, opens a PR. free tier: 15 tasks/day, 3 concurrent, runs on gemini flash. replaces: devin ($20/mo+) + cursor agent 5️⃣ Stitch — text → UI → code google's free figma killer. describe an interface, get production-ready HTML/CSS/Tailwind + figma export. march 2026 update added voice canvas, infinite canvas, and MCP integration with cursor. 350 standard + 200 experimental generations/month free. replaces: galileo AI + early-stage figma work — 6️⃣ Gemma 4 — open-weight LLM google's flagship open model. apache 2.0. 2B, 4B, 26B-MoE, and 31B variants. 256K context. runs on ollama with one command. quantized versions run on a 4090 or beefy laptop. replaces: paying for hosted LLM inference — 7️⃣ Illuminate — papers → podcasts paste an arxiv preprint link. illuminate turns dense research papers into a 6-8 min conversation between two AI hosts breaking it down. perfect for commute reading you can't do at a desk. note: still in waitlist for some regions. replaces: snipd + manual research reading — 8️⃣ Learn About (LearnLM) — adaptive AI tutor drop in any topic you're stuck on. highlight a word, click "go deeper," and the interface adapts in real time to your comprehension level. visual explanations, follow-up questions, the works. replaces: paid tutoring on niche topics — 9️⃣ Google Labs FX (ImageFX + Flow + MusicFX) — free imagen, veo, musicLM google labs creative suite. text-to-image (imagen 4), text-to-video (veo via Flow), text-to-music (musicLM). free tier: limited daily generations. the heavy veo 3.1 features are paid (AI Pro $19.99/mo). still worth using for image and music — those stay free. replaces: midjourney + suno (free tier only — runway-level video gen is paid) — 🔟 Google Colab — free GPU notebooks free T4 GPU + 12GB RAM in a browser tab. enough to fine-tune small models, run stable diffusion, prototype agents. the launching pad for half the ML projects on github. replaces: paid cloud GPU rentals — a quick honest note: these tools aren't 1:1 better than the paid versions they replace. but they're decent enough to get most things done — especially if you're not a heavy user or you've got little funds to play with. i've put all 10 in a public github repo (link in comments). follow + turn on post notifications for more useful posts like this 🔔
0:34

10 free Google AI tools nobody talks about. while everyone's burning $20/mo on chatgpt and claude, google quietly shipped a stack worth $200+/mo. all free. all yours. — 1️⃣ NotebookLM — your second brain upload sources (PDFs, websites, audio, YouTube). it summarizes, builds mind maps, generates quizzes, drafts slide decks, even turns your notes into a podcast you can listen to on a walk. free tier: 100 notebooks, 50 sources each, 50 chats/day, 3 audio overviews/day. replaces: notion AI + perplexity + readwise — 2️⃣ Google AI Studio — the free gemini playground web playground for gemini 3 pro and flash with a free API key. generous limits. paste a 1M-token context window and watch it actually use it. faster than the openai playground and free where openai charges per token. replaces: openai playground + paid API credits — 3️⃣ Gemini CLI — google's open-source terminal agent apache 2.0 licensed. one command (npx @google/gemini-cli) and you've got an agent in your terminal that reads your codebase, runs shell commands, and ships PRs. drop-in claude code alternative. replaces: claude code ($20/mo by default) — 4️⃣ Jules — async coding agent assign jules a github issue. it spins up a cloud VM, clones your repo, writes the plan, makes the changes, opens a PR. free tier: 15 tasks/day, 3 concurrent, runs on gemini flash. replaces: devin ($20/mo+) + cursor agent 5️⃣ Stitch — text → UI → code google's free figma killer. describe an interface, get production-ready HTML/CSS/Tailwind + figma export. march 2026 update added voice canvas, infinite canvas, and MCP integration with cursor. 350 standard + 200 experimental generations/month free. replaces: galileo AI + early-stage figma work — 6️⃣ Gemma 4 — open-weight LLM google's flagship open model. apache 2.0. 2B, 4B, 26B-MoE, and 31B variants. 256K context. runs on ollama with one command. quantized versions run on a 4090 or beefy laptop. replaces: paying for hosted LLM inference — 7️⃣ Illuminate — papers → podcasts paste an arxiv preprint link. illuminate turns dense research papers into a 6-8 min conversation between two AI hosts breaking it down. perfect for commute reading you can't do at a desk. note: still in waitlist for some regions. replaces: snipd + manual research reading — 8️⃣ Learn About (LearnLM) — adaptive AI tutor drop in any topic you're stuck on. highlight a word, click "go deeper," and the interface adapts in real time to your comprehension level. visual explanations, follow-up questions, the works. replaces: paid tutoring on niche topics — 9️⃣ Google Labs FX (ImageFX + Flow + MusicFX) — free imagen, veo, musicLM google labs creative suite. text-to-image (imagen 4), text-to-video (veo via Flow), text-to-music (musicLM). free tier: limited daily generations. the heavy veo 3.1 features are paid (AI Pro $19.99/mo). still worth using for image and music — those stay free. replaces: midjourney + suno (free tier only — runway-level video gen is paid) — 🔟 Google Colab — free GPU notebooks free T4 GPU + 12GB RAM in a browser tab. enough to fine-tune small models, run stable diffusion, prototype agents. the launching pad for half the ML projects on github. replaces: paid cloud GPU rentals — a quick honest note: these tools aren't 1:1 better than the paid versions they replace. but they're decent enough to get most things done — especially if you're not a heavy user or you've got little funds to play with. i've put all 10 in a public github repo (link in comments). follow + turn on post notifications for more useful posts like this 🔔

m0h

11,673 Aufrufe • vor 1 Monat

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,376 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 2 Monaten

HERMES AGENT v0.17.0 JUST SHIPPED. "THE REACH RELEASE." 1,475 COMMITS. 800 PRs. 245 CONTRIBUTORS. HERMES NOW REACHES IMESSAGE, RAFT NETWORK, AND CURSOR'S COMPOSER MODEL. the highlights: Nous Research iMESSAGE WITHOUT A MAC RELAY Photon Spectrum integration ships native iMessage support. no Mac in a closet. no BlueBubbles bridge. hermes photon login → device code auth → done. Hermes lives in the blue bubbles now. ASYNC SUBAGENTS NO LONGER BLOCK YOUR CHAT delegate_task(background=true) dispatches a subagent that runs in the background. returns a handle immediately. you keep working. result re-enters as a new turn when it finishes. long research dives stop blocking your main session. IMAGE EDITING, NOT JUST GENERATION image_generate now edits source images. "make this logo blue." "remove the background." "turn this sketch into a render." works across every supported image provider. same tool, new mode. CURSOR'S COMPOSER MODEL VIA GROK OAUTH grok-composer-2.5-fast is in the xAI model picker. 200k context window. fast coding model behind Cursor. your Grok subscription. Hermes's agent loop. no separate API key needed. AUTOMATION BLUEPRINTS schedule tasks without learning cron syntax. "daily news briefing at 8am" becomes a form. one blueprint definition renders everywhere: dashboard form, CLI slash command, Telegram chat, docs catalog entry. answer questions, not memorize 0 8 * * *. FULL PROFILE BUILDER IN DASHBOARD build a complete Hermes profile from the browser. pick model. choose skills. attach MCPs. no config.yaml editing. plus unified multi-profile view with global switcher. SKILLS HUB BROWSER REHAUL connected hubs (OpenAI, Anthropic, HuggingFace, NVIDIA). Featured section. full skill previews before install. security scan on each skill. browsing skills is a real browsing experience now. ATOMIC MEMORY OPERATIONS memory tool gained an operations array. batch add/replace/remove edits applied atomically. the model can free space and add entries in ONE call even when individual adds would overflow the budget. memory updates no longer fail mid-edit. CURATOR STOPPED SPENDING TOKENS BY DEFAULT deterministic skill pruning still runs free. LLM-powered consolidation now opt-in only: curator.consolidate: true to enable. routine background curation costs you zero tokens. WHATSAPP BUSINESS CLOUD API official Meta adapter alongside existing Baileys bridge. no QR-scanning bridge process to keep alive. hosted, first-party WhatsApp channel. TELEGRAM RICH MESSAGES (BOT API 10.1) proper rich formatting. cleaner long-message handling. native markup instead of flattened text. on by default. opt-out available. DESKTOP APP IS NOW A DAILY DRIVER rebindable keyboard shortcuts. native OS notifications. live subagent watch-windows streaming activity. composer model selector with per-model presets. automatic RTL/bidi text. resizable VS Code terminal pane. per-thread composer drafts. install ANY VS Code Marketplace theme. RAFT AGENT NETWORK new bundled adapter connects Hermes to raft. build as an external agent. wake-channel bridge. privacy by contract: wake payloads carry metadata only, never message bodies. SECURE DASHBOARD LOGIN every token-required endpoint returns 401 behind OAuth gate. websocket auth uses served dashboard token. public_url override warnings. exposing your dashboard to the network is safer by default. upgrade: hermes update 300+ issues closed. security round included. hermes-agent ecosystem now at 198K GitHub stars.
2:06

HERMES AGENT v0.17.0 JUST SHIPPED. "THE REACH RELEASE." 1,475 COMMITS. 800 PRs. 245 CONTRIBUTORS. HERMES NOW REACHES IMESSAGE, RAFT NETWORK, AND CURSOR'S COMPOSER MODEL. the highlights: Nous Research iMESSAGE WITHOUT A MAC RELAY Photon Spectrum integration ships native iMessage support. no Mac in a closet. no BlueBubbles bridge. hermes photon login → device code auth → done. Hermes lives in the blue bubbles now. ASYNC SUBAGENTS NO LONGER BLOCK YOUR CHAT delegate_task(background=true) dispatches a subagent that runs in the background. returns a handle immediately. you keep working. result re-enters as a new turn when it finishes. long research dives stop blocking your main session. IMAGE EDITING, NOT JUST GENERATION image_generate now edits source images. "make this logo blue." "remove the background." "turn this sketch into a render." works across every supported image provider. same tool, new mode. CURSOR'S COMPOSER MODEL VIA GROK OAUTH grok-composer-2.5-fast is in the xAI model picker. 200k context window. fast coding model behind Cursor. your Grok subscription. Hermes's agent loop. no separate API key needed. AUTOMATION BLUEPRINTS schedule tasks without learning cron syntax. "daily news briefing at 8am" becomes a form. one blueprint definition renders everywhere: dashboard form, CLI slash command, Telegram chat, docs catalog entry. answer questions, not memorize 0 8 * * *. FULL PROFILE BUILDER IN DASHBOARD build a complete Hermes profile from the browser. pick model. choose skills. attach MCPs. no config.yaml editing. plus unified multi-profile view with global switcher. SKILLS HUB BROWSER REHAUL connected hubs (OpenAI, Anthropic, HuggingFace, NVIDIA). Featured section. full skill previews before install. security scan on each skill. browsing skills is a real browsing experience now. ATOMIC MEMORY OPERATIONS memory tool gained an operations array. batch add/replace/remove edits applied atomically. the model can free space and add entries in ONE call even when individual adds would overflow the budget. memory updates no longer fail mid-edit. CURATOR STOPPED SPENDING TOKENS BY DEFAULT deterministic skill pruning still runs free. LLM-powered consolidation now opt-in only: curator.consolidate: true to enable. routine background curation costs you zero tokens. WHATSAPP BUSINESS CLOUD API official Meta adapter alongside existing Baileys bridge. no QR-scanning bridge process to keep alive. hosted, first-party WhatsApp channel. TELEGRAM RICH MESSAGES (BOT API 10.1) proper rich formatting. cleaner long-message handling. native markup instead of flattened text. on by default. opt-out available. DESKTOP APP IS NOW A DAILY DRIVER rebindable keyboard shortcuts. native OS notifications. live subagent watch-windows streaming activity. composer model selector with per-model presets. automatic RTL/bidi text. resizable VS Code terminal pane. per-thread composer drafts. install ANY VS Code Marketplace theme. RAFT AGENT NETWORK new bundled adapter connects Hermes to raft. build as an external agent. wake-channel bridge. privacy by contract: wake payloads carry metadata only, never message bodies. SECURE DASHBOARD LOGIN every token-required endpoint returns 401 behind OAuth gate. websocket auth uses served dashboard token. public_url override warnings. exposing your dashboard to the network is safer by default. upgrade: hermes update 300+ issues closed. security round included. hermes-agent ecosystem now at 198K GitHub stars.

YanXbt

34,197 Aufrufe • vor 1 Monat

Goodnight, 𝕏..·˚ ༘ ☾ ⋆｡˚ ☄︎ Here's a fun project you can start with Grok 4. Use Grok-Code-Fast-1 to build your own OS. Below is a prompt that you can give to Grok-Code, and it will set up a solid foundation for a Linux-based Operating system that you can build from the ground up with Grok4. >>> Grok 4 Prompt You are a fully capable AI developer agent with expert-level experience as an embedded Linux systems engineer. You have deep expertise in using automated build systems like Buildroot and Yocto to create custom operating systems from source. You have access to a sandboxed Linux shell environment that allows you to write, execute, and debug code. Your mission is to generate a complete project skeleton for a minimal, custom Linux OS, and then you will execute the build scripts yourself to verify their correctness, automatically fixing any issues that arise. This is NOT a request to follow the Linux From Scratch (LFS) book. You will use the Buildroot build system to automate the entire process. You will follow a two-phase process: Phase 1: Generation and Phase 2: Execution and Iterative Debugging. ------------------------------------------------------------- Phase 1: Code and Script Generation First, you will generate all the necessary files for the project skeleton. All generated shell scripts must be robust and path-aware, executing correctly from any directory [Previous conversation]. Detailed Implementation Steps (using Context-Aware Decomposition): 1. Generate the Project Directory Structure via setup. sh Create a setup. sh script that establishes the following directory structure: • buildroot/ - Where the Buildroot source code will be cloned. • configs/ - To store our custom Buildroot configuration (defconfig). • board/ - For custom board support, including a readme.txt explaining its purpose for filesystem overlays. • output/ - Where all build artifacts will be placed. • scripts/ - A home for our build. sh and test. sh scripts. Crucially, this setup. sh script (and all others) must begin with a preamble to define the project's root directory, making all subsequent paths absolute and robust: #!/bin/bash # Preamble to ensure path robustness and stop on error set -e PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE}")" && pwd)" The script must then clone the latest stable branch of Buildroot into $ PROJECT_ROOT/buildroot/. 2. Create the Minimal and Correct Buildroot defconfig Create a file named configs/tiny_linux_defconfig. This configuration must be the absolute bare minimum required to boot to a shell and must contain the exact configuration options listed below to avoid ambiguity and known errors: • Target Architecture: x86_64. • Toolchain: Use the default Buildroot toolchain. • Init System: Use BusyBox init. • System Utilities (BusyBox): ◦ To ensure BusyBox is statically linked without errors, you must include the following line directly in the defconfig file: BR2_PACKAGE_BUSYBOX_STATIC_LINK=y [Previous conversation, 298, 753]. ◦ To prevent the ROJECT_ROOT error, explicitly do NOT use a configuration fragment for BusyBox. Do not generate any lines containing BR2_BUSYBOX_CONFIG_FRAGMENT_FILES [Previous conversation]. • Kernel: ◦ Build the latest stable Linux kernel. ◦ Use tinyconfig as a base. ◦ Ensure the following options are explicitly enabled (=y) to make it bootable in QEMU: CONFIG_64BIT=y, CONFIG_DEVTMPFS=y, CONFIG_DEVTMPFS_MOUNT=y, CONFIG_BINFMT_ELF=y, CONFIG_BLK_DEV_INITRD=y (for initramfs support), CONFIG_TTY=y, CONFIG_PRINTK=y, CONFIG_DRM_FBDEV_EMULATION=y (for UEFI framebuffer console). • Filesystem Image: Configure it to produce a compressed cpio initial ramdisk (initramfs) image. • Bootloader: Do not include GRUB or other bootloaders. We will boot the kernel directly with QEMU. 3. Generate the scripts/build.sh and scripts/test.sh Scripts Generate path-aware build and test scripts, placing them in the scripts/ directory. • scripts/build.sh: This script must use absolute paths derived from a preamble. It must use make -C "$PROJECT_ROOT/buildroot" O="$PROJECT_ROOT/output" ... for a clean, out-of-tree build. It must include the -j$(nproc) flag to maximize build speed on multi-core systems [111, 967, Previous conversation]. • scripts/test.sh: This script must also be path-aware and launch QEMU using absolute paths to the kernel (bzImage) and initramfs (rootfs.cpio.gz) images. 4. Generate a Detailed README. md File Generate a comprehensive README. md file. It must explain prerequisites, "How to Customize Your Linux System" first, and finally, the "Quick Start" instructions for user clarity [Previous conversation]. ------------------------------------------------------------- Phase 2: Execution and Iterative Debugging Now, you will use your sandboxed Linux shell to verify and validate the scripts you just generated. This is a critical self-correction step based on the Recursive Criticism and Improvement (RCI) pattern. You will perform a full build cycle. 1. Execute setup. sh: • Run the setup. sh script you generated. • Capture the standard output and standard error. • If the script fails: Analyze the error, diagnose the root cause, generate the corrected setup. sh code, and then execute the corrected script to confirm it succeeds. 2. Execute build. sh: • After setup. sh completes successfully, run the scripts/build.sh script. This will trigger a full compilation of the Linux system. • Capture all output. • If the build fails: ◦ Analyze: Analyze the compiler error output. ◦ Diagnose: Identify the root cause (e.g., missing dependencies, incorrect configuration flags, pathing errors). ◦ Correct: Based on your analysis, identify which file is responsible for the failure (e.g., configs/tiny_linux_defconfig, scripts/build.sh) and generate the corrected code for that file. ◦ Repeat: Repeat the execution of scripts/build.sh until the build completes successfully without any errors. 3. Final Output: Once you have successfully executed both setup. sh and scripts/build.sh, you will present your final output. • First, provide the final, validated versions of all generated files (setup. sh, configs/tiny_linux_defconfig, scripts/build.sh, scripts/test.sh, and README. md) in separate, clearly labeled markdown code blocks. • Second, follow the code with a brief execution log. This log should summarize your actions, including any errors you encountered and fixed during the iterative debugging phase, demonstrating the self-correction process.
1:05

Goodnight, 𝕏..·˚ ༘ ☾ ⋆｡˚ ☄︎ Here's a fun project you can start with Grok 4. Use Grok-Code-Fast-1 to build your own OS. Below is a prompt that you can give to Grok-Code, and it will set up a solid foundation for a Linux-based Operating system that you can build from the ground up with Grok4. >>> Grok 4 Prompt You are a fully capable AI developer agent with expert-level experience as an embedded Linux systems engineer. You have deep expertise in using automated build systems like Buildroot and Yocto to create custom operating systems from source. You have access to a sandboxed Linux shell environment that allows you to write, execute, and debug code. Your mission is to generate a complete project skeleton for a minimal, custom Linux OS, and then you will execute the build scripts yourself to verify their correctness, automatically fixing any issues that arise. This is NOT a request to follow the Linux From Scratch (LFS) book. You will use the Buildroot build system to automate the entire process. You will follow a two-phase process: Phase 1: Generation and Phase 2: Execution and Iterative Debugging. ------------------------------------------------------------- Phase 1: Code and Script Generation First, you will generate all the necessary files for the project skeleton. All generated shell scripts must be robust and path-aware, executing correctly from any directory [Previous conversation]. Detailed Implementation Steps (using Context-Aware Decomposition): 1. Generate the Project Directory Structure via setup. sh Create a setup. sh script that establishes the following directory structure: • buildroot/ - Where the Buildroot source code will be cloned. • configs/ - To store our custom Buildroot configuration (defconfig). • board/ - For custom board support, including a readme.txt explaining its purpose for filesystem overlays. • output/ - Where all build artifacts will be placed. • scripts/ - A home for our build. sh and test. sh scripts. Crucially, this setup. sh script (and all others) must begin with a preamble to define the project's root directory, making all subsequent paths absolute and robust: #!/bin/bash # Preamble to ensure path robustness and stop on error set -e PROJECT_ROOT="$(cd "$(dirname "${BASH_SOURCE}")" && pwd)" The script must then clone the latest stable branch of Buildroot into $ PROJECT_ROOT/buildroot/. 2. Create the Minimal and Correct Buildroot defconfig Create a file named configs/tiny_linux_defconfig. This configuration must be the absolute bare minimum required to boot to a shell and must contain the exact configuration options listed below to avoid ambiguity and known errors: • Target Architecture: x86_64. • Toolchain: Use the default Buildroot toolchain. • Init System: Use BusyBox init. • System Utilities (BusyBox): ◦ To ensure BusyBox is statically linked without errors, you must include the following line directly in the defconfig file: BR2_PACKAGE_BUSYBOX_STATIC_LINK=y [Previous conversation, 298, 753]. ◦ To prevent the ROJECT_ROOT error, explicitly do NOT use a configuration fragment for BusyBox. Do not generate any lines containing BR2_BUSYBOX_CONFIG_FRAGMENT_FILES [Previous conversation]. • Kernel: ◦ Build the latest stable Linux kernel. ◦ Use tinyconfig as a base. ◦ Ensure the following options are explicitly enabled (=y) to make it bootable in QEMU: CONFIG_64BIT=y, CONFIG_DEVTMPFS=y, CONFIG_DEVTMPFS_MOUNT=y, CONFIG_BINFMT_ELF=y, CONFIG_BLK_DEV_INITRD=y (for initramfs support), CONFIG_TTY=y, CONFIG_PRINTK=y, CONFIG_DRM_FBDEV_EMULATION=y (for UEFI framebuffer console). • Filesystem Image: Configure it to produce a compressed cpio initial ramdisk (initramfs) image. • Bootloader: Do not include GRUB or other bootloaders. We will boot the kernel directly with QEMU. 3. Generate the scripts/build.sh and scripts/test.sh Scripts Generate path-aware build and test scripts, placing them in the scripts/ directory. • scripts/build.sh: This script must use absolute paths derived from a preamble. It must use make -C "$PROJECT_ROOT/buildroot" O="$PROJECT_ROOT/output" ... for a clean, out-of-tree build. It must include the -j$(nproc) flag to maximize build speed on multi-core systems [111, 967, Previous conversation]. • scripts/test.sh: This script must also be path-aware and launch QEMU using absolute paths to the kernel (bzImage) and initramfs (rootfs.cpio.gz) images. 4. Generate a Detailed README. md File Generate a comprehensive README. md file. It must explain prerequisites, "How to Customize Your Linux System" first, and finally, the "Quick Start" instructions for user clarity [Previous conversation]. ------------------------------------------------------------- Phase 2: Execution and Iterative Debugging Now, you will use your sandboxed Linux shell to verify and validate the scripts you just generated. This is a critical self-correction step based on the Recursive Criticism and Improvement (RCI) pattern. You will perform a full build cycle. 1. Execute setup. sh: • Run the setup. sh script you generated. • Capture the standard output and standard error. • If the script fails: Analyze the error, diagnose the root cause, generate the corrected setup. sh code, and then execute the corrected script to confirm it succeeds. 2. Execute build. sh: • After setup. sh completes successfully, run the scripts/build.sh script. This will trigger a full compilation of the Linux system. • Capture all output. • If the build fails: ◦ Analyze: Analyze the compiler error output. ◦ Diagnose: Identify the root cause (e.g., missing dependencies, incorrect configuration flags, pathing errors). ◦ Correct: Based on your analysis, identify which file is responsible for the failure (e.g., configs/tiny_linux_defconfig, scripts/build.sh) and generate the corrected code for that file. ◦ Repeat: Repeat the execution of scripts/build.sh until the build completes successfully without any errors. 3. Final Output: Once you have successfully executed both setup. sh and scripts/build.sh, you will present your final output. • First, provide the final, validated versions of all generated files (setup. sh, configs/tiny_linux_defconfig, scripts/build.sh, scripts/test.sh, and README. md) in separate, clearly labeled markdown code blocks. • Second, follow the code with a brief execution log. This log should summarize your actions, including any errors you encountered and fixed during the iterative debugging phase, demonstrating the self-correction process.

Tetsuo

2,840,991 Aufrufe • vor 9 Monaten

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.
51:48

If you watch this ~50 minute screen recording closely (yeah, I know, it's long; there are also some times when my computer was very slow and laggy, just skip past that part. And at one point I had to run and get my 9-month-old a new bottle and left it on a boring screen, sorry!), I believe you can see real signs of the kind of runaway, recursive AI self-improvement that people have been warning of for a while (Mr. Kurzweil most notably and prophetically). Why do I say that? What's different now? Well, there's a reason my set of agent coding tooling is called the Flywheel. These tools all mutually self-reinforce each other. And they all flow directly into my ntm tool (short for "named_tmux_manager"), which acts as a sort of integration point and nerve center for the tools (this is becoming more true by the minute as I'm now seriously working on ntm). Now, ntm was something I started making to automate some aspects of my workflow, but it was the kind of thing where, until it was perfect, it sort of just slowed me down. So I didn't actually use it even though I kept working on it and trying to improve it, and suggested to users that they try it in my tutorials. Well anyway, I finally got around to "dogfooding" ntm last night, and now it's going to get very dramatically better at an alarming rate. Some of that is from applying my "idea wizard" prompt to generate more useful features and building that stuff out and addressing obvious pain points I encountered during my newfound usage of the tool. But a lot comes from my realization that, once again, ntm's true utility is not as a tool for ME, but for an agent. That is, ntm lets one instance of Claude Code or Codex act as, well, me, do the things that I had been doing manually. Do I wish I had started using ntm earlier? No, for two big reasons: 1) Doing it manually helped me build up my intuition massively, which directly led me down the path of creating useful prompt strategies and workflows; these often began as ad-hoc prompts that I realized could be generalized and made more versatile/universal. Lesson: don't prematurely automate until you have an intimate, intuitive feel for your "core value-add loop." Otherwise you'll have a fully automated system quickly that efficiently and automatically does a stupid or otherwise sub-optimal thing. 2) My eyes have been opened to the beauty and power of Skills. I'm not talking about your garden-variety skills that are just a simple markdown file. I'm talking about true tour-de-force directories of perfectly structured and organized files that are filled with good information, insights, workflows, etc., but presented in a way that is highly optimized for consumption by AI agents, with extreme attention paid to things like perfect progressive disclosure, token density, agent-ergonomics, agent-intuitiveness, etc. And also Skills that go way beyond markdown files, with full integration into Claude Code where it makes sense via hooks, sub-agents, and even Python scripts. These kinds of skills are a qualitative difference in expressive power and usefulness and a total game changer. They are also effectively composable, creating almost an algebra of skills that let you use them together in powerful ways. I'm working on a subscription service website and CLI tool now to share what I've learned here most effectively, stay tuned for that in the coming days. Anyway, I now know what to make and how to make it. So, getting back to that screen recording, what does it show that makes me claim recursive self-improvement is here? If you keep your eye on the upper left tmux pane, that's the "controller" agent. It is using ntm to control all the other panes which are also running Claude Code (but ntm fully supports other agent types like Codex and Gemini-CLI, and it's trivially easy to mix and match them if you wanted to have, say, 8 CCs and 6 Codexes for writing the code and 3 Gemini-CLIs for reviewing code.) Now, there's nothing that crazy about this much so far. But where it starts to get very cool is that as the session continues and we encounter real-world problems, things like my ridiculously overloaded computer that keeps hanging for long periods, Claude Code instances that crash and get into a frozen, unresponsive state, it can learn from that. And you can see it using my skill writing skill to refine its ntm vibe coding skill in real time. And then take that skill and refine it to be more intuitive for itself. Or use my cass tool skill to search all the session histories to look for problems that came up and strategize how to solve them. The most useful part was when, towards the end of the session, I told it to reflect on all the things we had done and problems we encountered. One way it can usefully leverage those reflections is by improving its ntm vibe coding skill to make it cover more edge cases and exigencies. But the other, more fundamental, way is for it to conceive of and design the optimal new features and functionality for ntm itself so that the tool embodies those lessons in a first-class way. This offloads cognition from its brain onto its tooling, just like how a person can lean on spellcheck or a calculator. It codifies correct, effective reasoning at the tool level, where it's more reliable and robust and repeatable. And btw, did you notice what code base it was working on the whole time? It was none other than ntm itself! So as it worked on its own tool, it had reflections and ideas about how to further improve the tool. Now, it could have just as easily gotten those insights and ideas while using ntm to work on a different project, but the fact that it was working on itself is almost gloriously meta and recursive. So by the end, after learning from tending to a big group of agent workers (btw, I have previously emphasized doing everything in a really distributed/decentralized way, where each fungible agent gets identical marching orders that tell it to use my bv tool to find the optimal bead to work on. This does work very well, but occasionally results in some contention and overlap from thundering herd, or at least wastes time/tokens/communication in avoiding that before the agents waste time duplicating work. But in this new ntm-oriented workflow, I was able to have the controller agent in the upper left use bv itself and then optimally parcel out the instructions to each agent so that we could know for sure that there's no overlap), I ended up with a ton of new beads for new features, which I had it optimize and polish a few times. Now I can swap to a new Claude Max account and have the swarm implement all those new features! It should only take a couple passes like the one shown in the screen recording to get everything implemented. Then we can rinse and repeat, having the agent read through the full session histories of each agent and its experience from its own session in sending ntm commands and seeing how they worked out in practice, to come up with the next batch of changes to both its ntm vibe coding skill AND to the ntm tool itself. Do you see how rapidly this turns into Skynet? My mistake earlier was in focusing on making myself a "faster horse" as Henry Ford used to joke about customers wanting before he showed them what they should really want (a Model T). That is, something that would make my experience nicer while doing this agent swarm based development workflow. But the obvious lesson is that you should make all your tooling agent-first because the agents are just better at this stuff. You can still watch, and of course I did add a ridiculous number of very nice human-centric features to ntm that you'll be seeing in the next day or two, but those are really kind of "for fun" to make us humans feel better about the process. All the real value-add is happening "by agents, for agents." PS: Towards the end, you can see me switch to my Mac and tell Claude to improve the skill that I made earlier today for taking the mkv screen recording files from OBS Studio and muxing them into MP4 files for sharing, while downloading songs from YouTube to serve as the background music. I made it so it can also grab the thumbnails and generate little song credit cards that show up in the lower right corner. This worked perfectly the first time! I'll include some screenshots in a response post showing how that worked, but it was awesome to witness. Skills are POWERFUL. I'll also post a link to this video on YouTube if you prefer to watch it there.

Jeffrey Emanuel

25,483 Aufrufe • vor 6 Monaten

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 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 5 Monaten

Promised to ship before the movie so... 📅 53 days 🤖 731 vibe coded commits ⚡️ Powered by Three.js 🚀 Inspired by a space plumber 🙋‍♂️ AMA, no secrets, no shame High level, grouped list of what's in this game: Galaxy DNA - Lumas - Star Bits - Spin attack with air boost + ground-cancel - Galaxy gravity - Octoombas - Gateway Galaxy music track Vibe Coding Process - Claude Code (Opus) for ~95% of all code - CLAUDE.md project instructions file (163 lines of rules + constraints) - 87 implementation plans written before coding - 36 AI code reviews (ECS, architecture, performance) - 11 retrospectives after major features - 60 extracted skills (reusable knowledge from debugging sessions) - Constraints doc that grows every time something breaks (115 lines) - /lets-build workflow: discovery → plan → review → implement → verify - Every feature: plan first, review the plan, then build in atomic commits - Custom level construction CLI (AI-assisted placement) - this evolved over 53 days Architecture - Custom ECS engine (Structure-of-Arrays, zero-alloc hot paths) - Benchmarks faster than bitECS on packed iteration - 117 ECS systems orchestrated in explicit update order - Data-oriented Process system (sequential/parallel composition) - 30+ process types: UI animations, camera arcs, sfx Rendering - Three.js + Pixi.js sharing one WebGL2 context - Three renders 3D, Pixi renders UI — no extra canvases - Half-res bloom, color grading, occlusion silhouettes - Fresnel rim lighting + hemisphere ambient for Galaxy-style polish Physics - Rapier3D WASM physics (SIMD build) - Kinematic character controllers for player + all enemies Gravity - Galaxy-style gravity fields (walk around surfaces) - 4 gravity field types - Priority-based gravity resolution with distance tiebreakers - Convex hull letter platforms with per-face gravity - Spring-damped gravity transitions Shadows - Multi-pass gravity-aware shadow system - Per-instance shadow filtering via vertex shader attributes - InstancedMesh candidates promoted across gravity fields - Dynamic frustum sized from camera FOV each frame Camera - camera system with 12 critically damped springs - Follow-gravity mode (trailing orbit in tangent plane) - Fixed-up mode (screen stays level on letter platforms) - Top-down mode (Galaxy overhead cam, roll-free quaternion) - Camera collision via 4-direction spherecast repulsion - Override blend system for boss fights + pipe travel - Catmull-Rom spline intro flythrough with per-waypoint duration Space - Procedural space nebula (simplex noise shader, 3 octaves) - 1,800 seeded stars with per-star brightness + color variety - Galaxy-authentic palette across all screens Enemies - 5 enemy types with full AI state machines - Goomba, Koopa, Spiny, Bob-omb, Octoomba - 3D distance → FOV cone → LOS raycast detection pipeline - Editor-placed OBB avoidance zones with deflection hysteresis - Recoil, stun, shell, fuse, and ranged attack behaviors Boss Fight - Bowser Jr. boss fight - Multi-phase combat with Bob-omb spawning - Controlled intro/outro sequence Mario - Galaxy-style spin attack - Rainbow diamond particle burst (InstancedMesh, 64 pool) - Hit-stop with global time scale freeze + camera shake - Air boost, ground-cancel, shell kick at extended range - Invulnerability frames during active spin Yoshi - mount/ride system with shield HP - +3 extra HP ring on mount, damage depletes shield first - Overflow damage carries to Mario - Forced dismount on shield break with poof effect Objects - Coin system with InstancedMesh rendering (256 max) - Per-instance opacity via shader patching - Pop → float → shrink → fade collection animation - Swap-and-pop O(1) entity removal - Star bit burst spawning with attraction system - Pipe warp travel with camera override blend - Parallel-transported screen-right vector during crossfade - Shadow field updates for traveling entities - trampoline - 3D assets from Hello Mario Framework (now archived) and game rips Audio - 17+ wired sound effects with spatial audio - Bob-omb fuse sound: per-entity lifecycle, looping playback tracking - Distance-based volume for poof and explosion effects UI - Odyssey-style ring HP meter with shield inner ring - Number roll + arc lerp stagger on health changes - Gold coin counter HUD - Loading screen with code-split fast first paint - Pretext layout flow in "legal" screen with retro Mario Controls - Mobile touch controls: virtual joystick + A/B buttons - Proportional analog stick with walk/run speed switching - Gamepad support: Xbox, PlayStation, Switch Pro - Dead zones, auto-reconnect, synthetic DOM key bridge Dev Tooling - experimental CLI level construction tool with undo history - 18 placement types with type-safe defaults - Atomic file writes, auto-backup (max 20), live reload - Dev server auto-save plugin for visual editor - Two-panel debug editor (Tweakpane) - Hierarchy + inspector with gravity field live editing - Translation/rotation gizmos with gravity-relative local space - Per-waypoint camera preview for intro spline tuning 731 commits. 53 days. 95%+ vibe coded.
0:53

Promised to ship before the movie so... 📅 53 days 🤖 731 vibe coded commits ⚡️ Powered by Three.js 🚀 Inspired by a space plumber 🙋‍♂️ AMA, no secrets, no shame High level, grouped list of what's in this game: Galaxy DNA - Lumas - Star Bits - Spin attack with air boost + ground-cancel - Galaxy gravity - Octoombas - Gateway Galaxy music track Vibe Coding Process - Claude Code (Opus) for ~95% of all code - CLAUDE.md project instructions file (163 lines of rules + constraints) - 87 implementation plans written before coding - 36 AI code reviews (ECS, architecture, performance) - 11 retrospectives after major features - 60 extracted skills (reusable knowledge from debugging sessions) - Constraints doc that grows every time something breaks (115 lines) - /lets-build workflow: discovery → plan → review → implement → verify - Every feature: plan first, review the plan, then build in atomic commits - Custom level construction CLI (AI-assisted placement) - this evolved over 53 days Architecture - Custom ECS engine (Structure-of-Arrays, zero-alloc hot paths) - Benchmarks faster than bitECS on packed iteration - 117 ECS systems orchestrated in explicit update order - Data-oriented Process system (sequential/parallel composition) - 30+ process types: UI animations, camera arcs, sfx Rendering - Three.js + Pixi.js sharing one WebGL2 context - Three renders 3D, Pixi renders UI — no extra canvases - Half-res bloom, color grading, occlusion silhouettes - Fresnel rim lighting + hemisphere ambient for Galaxy-style polish Physics - Rapier3D WASM physics (SIMD build) - Kinematic character controllers for player + all enemies Gravity - Galaxy-style gravity fields (walk around surfaces) - 4 gravity field types - Priority-based gravity resolution with distance tiebreakers - Convex hull letter platforms with per-face gravity - Spring-damped gravity transitions Shadows - Multi-pass gravity-aware shadow system - Per-instance shadow filtering via vertex shader attributes - InstancedMesh candidates promoted across gravity fields - Dynamic frustum sized from camera FOV each frame Camera - camera system with 12 critically damped springs - Follow-gravity mode (trailing orbit in tangent plane) - Fixed-up mode (screen stays level on letter platforms) - Top-down mode (Galaxy overhead cam, roll-free quaternion) - Camera collision via 4-direction spherecast repulsion - Override blend system for boss fights + pipe travel - Catmull-Rom spline intro flythrough with per-waypoint duration Space - Procedural space nebula (simplex noise shader, 3 octaves) - 1,800 seeded stars with per-star brightness + color variety - Galaxy-authentic palette across all screens Enemies - 5 enemy types with full AI state machines - Goomba, Koopa, Spiny, Bob-omb, Octoomba - 3D distance → FOV cone → LOS raycast detection pipeline - Editor-placed OBB avoidance zones with deflection hysteresis - Recoil, stun, shell, fuse, and ranged attack behaviors Boss Fight - Bowser Jr. boss fight - Multi-phase combat with Bob-omb spawning - Controlled intro/outro sequence Mario - Galaxy-style spin attack - Rainbow diamond particle burst (InstancedMesh, 64 pool) - Hit-stop with global time scale freeze + camera shake - Air boost, ground-cancel, shell kick at extended range - Invulnerability frames during active spin Yoshi - mount/ride system with shield HP - +3 extra HP ring on mount, damage depletes shield first - Overflow damage carries to Mario - Forced dismount on shield break with poof effect Objects - Coin system with InstancedMesh rendering (256 max) - Per-instance opacity via shader patching - Pop → float → shrink → fade collection animation - Swap-and-pop O(1) entity removal - Star bit burst spawning with attraction system - Pipe warp travel with camera override blend - Parallel-transported screen-right vector during crossfade - Shadow field updates for traveling entities - trampoline - 3D assets from Hello Mario Framework (now archived) and game rips Audio - 17+ wired sound effects with spatial audio - Bob-omb fuse sound: per-entity lifecycle, looping playback tracking - Distance-based volume for poof and explosion effects UI - Odyssey-style ring HP meter with shield inner ring - Number roll + arc lerp stagger on health changes - Gold coin counter HUD - Loading screen with code-split fast first paint - Pretext layout flow in "legal" screen with retro Mario Controls - Mobile touch controls: virtual joystick + A/B buttons - Proportional analog stick with walk/run speed switching - Gamepad support: Xbox, PlayStation, Switch Pro - Dead zones, auto-reconnect, synthetic DOM key bridge Dev Tooling - experimental CLI level construction tool with undo history - 18 placement types with type-safe defaults - Atomic file writes, auto-backup (max 20), live reload - Dev server auto-save plugin for visual editor - Two-panel debug editor (Tweakpane) - Hierarchy + inspector with gravity field live editing - Translation/rotation gizmos with gravity-relative local space - Per-waypoint camera preview for intro spline tuning 731 commits. 53 days. 95%+ vibe coded.

Tommy Leung

184,445 Aufrufe • vor 3 Monaten

CANCEL Your Weekend Plans and Learn Vibe Coding Today, Start Making $10,000/Month Building Apps for People. $0 in Coding Experience. I made 5 AI Trading Bots & Apps Built in 6 Hours. Each One Worth $3,000-$15,000 to Clients. You Spent $500 on a Bootcamp and Still Can't Deploy a Landing Page. That's not the bootcamp's fault. That's you. People with zero coding skills are building full apps with payments, databases, and authentication using AI. Charging clients $5,000-$10,000 per project. Finishing in one afternoon. You're still Googling "should I learn Python or JavaScript first." This attached video is a goldmine. 6 hours. 5 real apps. From complete beginner to deploying revenue-generating products. One video. Free. Save it. Watch it this weekend. Not next weekend. Today. Now let me break down exactly what's inside and why you can't afford to ignore this. Save this post. You'll hate yourself if you lose it. ↓ Let's talk about why you still can't code... You bought the Udemy course. $12.99. Watched 3 lectures. Got confused. Told yourself you'd continue tomorrow. That was 8 months ago. You bought another course. $49.99. This one had better reviews. Watched the intro. Bookmarked the rest. Never opened it again. You signed up for a bootcamp. $5,000. Dropped out at week 4 because "life got busy." Life didn't get busy. You got scared. Three years. Hundreds of dollars. Multiple courses. Zero apps built. Zero projects deployed. Zero revenue generated. And now someone with zero coding experience is building full apps in hours using AI tools you haven't even tried. You're not falling behind slowly. You're falling behind at full speed. Save this post right now. This is the course that makes every other coding course you bought irrelevant. Follow Himanshu Kumar so you don't miss the breakdown. ↓ What is vibe coding and why should you care? Traditional coding: Learn syntax for 6 months. Build a to-do app. Feel proud. Realize nobody will pay for a to-do app. Give up. Vibe coding: Describe what you want to build. AI builds it. You guide, adjust, deploy. People pay for it. You're not writing code line by line. You're directing an AI agent that writes code for you. Think of it like this: Traditional coding = you're the construction worker. Vibe coding = you're the architect. The architect makes more money. The architect doesn't carry bricks. The architect doesn't need to know how to pour concrete. The architect needs to know what to build and why. That's vibe coding. And while you've been debating whether to learn Python or JavaScript first, people are skipping both and building apps that generate revenue. With zero coding knowledge. This isn't the future. This is right now. Save this post and follow Himanshu Kumar for more vibe coding breakdowns that actually make you money. ↓ What this 6-hour course covers. This isn't some 20-minute tutorial that shows you how to make a button change color. This is 6 hours. 5 complete apps. Real software engineering. Real deployment. Real money-making potential. Here's what you'll build: > Portfolio website - deployed live on Netlify > Full-stack client dashboard - with database and auth > Lead generation app - with API integrations > Thumbnail generator - with payment integration via Stripe > Splinter - a full SaaS product with pricing and marketing Not toy projects. Not "follow along and never use again." Actual apps that people pay for. Built with Gemini 3.1 Pro, Antigravity, Supabase, Next.js, Vite, and more. You know how many people charge $5,000+ to build a single one of these apps for a client? You'll be able to build all 5 by the end of this weekend. You can't afford to scroll past this. Bookmark this post. Follow Himanshu Kumar because I'm breaking down every tool in this stack separately. ↓ The tools you'll master. Gemini 3.1 Pro: Google's most powerful AI model. You'll use it to generate entire codebases. Not snippets. Entire apps. Antigravity: The AI coding environment that makes vibe coding actually work. Agent chat. MCP servers. Voice dictation. It's not VS Code with a chatbot bolted on. It's built from the ground up for AI-first development. Supabase: Your backend. Database. Authentication. All set up in minutes. Not weeks of configuration. Next.js + Vite: Modern frameworks that make your apps fast, scalable, and professional. Stripe: Payment integration. So your apps can actually charge people money. You know, the whole point. Claude Code: Yes, Claude Code is covered too. Because the best developers in 2026 don't use one AI tool. They use all of them. While you're still trying to decide which AI tool is "the best one," smart people are using all of them together and making money from every angle. Stop debating tools. Start using them. Save this post and follow Himanshu Kumar for deep dives into each of these tools. ↓ What you'll actually learn beyond just "building apps." This course doesn't just teach you to copy and paste prompts. You'll learn real software engineering: > Hosting and deployment > Modern software design patterns > Languages and frameworks > Version control and GitHub > Programming with AI agents and agent teams > Database design (SQL vs NoSQL) > Security audits > API integration > Payment processing This is everything a $15,000 bootcamp teaches. In 6 hours. For free. On YouTube. Your friend who spent $15K on a bootcamp is going to be really upset when you build better apps than them after watching one YouTube video this weekend. Don't tell them about this course. Or do. Their reaction will be priceless. This is a $15,000 education for $0. Save this post before it gets buried. Follow Himanshu Kumar for more free resources that make paid courses look like scams. ↓ The guy teaching this actually makes money. Not "makes money selling courses about making money." Actually makes money. Nick built automated businesses with Make . Most notably 1SecondCopy, a content company that hit 7 figures. Seven figures. From automation. He's not teaching theory. He's showing you what real systems that generate real revenue look like. 90% of coding teachers on YouTube have never shipped a product that made $1. They teach coding. They don't use coding to make money. This guy does both. That's why this course is different. You've been learning from people who teach for a living. Start learning from people who build for a living. Save this post. Follow Himanshu Kumar for more content from builders, not lecturers. ↓ Let me tell you what's really happening while you "think about learning to code." Every week that passes, AI coding tools get better. Every week that passes, more people learn vibe coding. Every week that passes, the market gets more competitive. Right now, vibe coding is still early. Not many people know how to do it well. Clients are desperate for someone who can build apps fast. $3,000 for a landing page with payments. $5,000 for a SaaS MVP. $10,000 for a full client dashboard. These are real prices people are charging for apps they built in a single day using the exact tools in this course. But this window won't last forever. In 6 months, everyone will know how to vibe code. In 12 months, it'll be a basic requirement. In 24 months, not knowing this will be like not knowing how to use email in 2010. You're either early or you're irrelevant. Right now you can still be early. But not if you spend this weekend on Netflix. The window is closing. Every weekend you waste is a weekend someone else uses to get ahead of you. Save this post. Follow Himanshu Kumar before this opportunity becomes obvious to everyone. ↓ The 5 apps you'll build and what they're actually worth. App 1: Portfolio Website. What clients pay for this: $500-$2,000. Time to build with vibe coding: 30 minutes. App 2: Client Dashboard. What clients pay for this: $5,000-$15,000. Time to build with vibe coding: 2-3 hours. App 3: Lead Generation Tool. What clients pay for this: $3,000-$8,000. Time to build with vibe coding: 1-2 hours. App 4: Thumbnail Generator with Payments. What clients pay for this: $2,000-$5,000. Or sell it as a SaaS for recurring revenue. Time to build: 1-2 hours. App 5: Splinter (Full SaaS Product). What clients pay for this: $10,000-$25,000. Or launch it yourself for monthly recurring revenue. Time to build: 2-3 hours. Total value of apps you can build after this course: $20,000-$55,000. Total cost of this course: $0. Total time investment: one weekend. You spend more than one weekend deciding which Netflix show to start next. At least this weekend would pay you back. Read those numbers again. Save this post. Follow Himanshu Kumar because I'll be breaking down how to sell each of these apps as a service. ↓ Here's the business model nobody's talking about. Learn vibe coding this weekend. Build 5 apps. Pick the one you're best at. Offer it as a service. "I build professional SaaS dashboards for businesses using AI. Faster than agencies. Fraction of the cost. $5,000 per project." 2 projects per month = $10,000/month. Working maybe 20 hours total. While you're applying for jobs that pay $4,000/month and require 5 years of experience you don't have, someone who watched this course last weekend just landed their second $5,000 client. No degree. No portfolio. No 5 years of experience. Just the ability to build what people need faster than anyone else. That's the entire business model. Learn fast. Build fast. Charge accordingly. Stop applying for jobs. Start creating them. Save this post. Follow Himanshu Kumar for the exact outreach scripts to land your first vibe coding client. ↓ Why you won't watch this course. Because it's 6 hours. "6 hours?? That's too long." You binged an entire season of a show last weekend in 8 hours. You scrolled Twitter for 4 hours yesterday. You spent 3 hours watching YouTube shorts that you don't even remember. But 6 hours to learn a skill that could make you $10,000/month? "I don't have time for that." You have time. You just don't have discipline. And that's the actual reason you're broke. Not the economy. Not the market. Not your circumstances. Your inability to sit down for 6 hours and learn something that changes your life. Everything else is a story you tell yourself to feel better about doing nothing. That's the uncomfortable truth. Save this post so it stares at you every time you open your bookmarks. Follow Himanshu Kumar because I'll keep reminding you until you actually do something. ↓ What happens this weekend determines your next year. Path A: Watch the course Saturday. Build your first app Sunday. Start offering services Monday. Land first client within 2 weeks. $5,000-$10,000/month within 60 days. Path B: Sleep in Saturday. Brunch Sunday. Netflix Sunday night. Monday morning alarm goes off. Back to the same job. Same salary. Same frustration. Same "I'll start next weekend." 52 weekends in a year. How many have you already wasted? Path A costs you one weekend. Path B costs you your entire future. Same video. Same information. Same 6 hours. Two completely different lives. ↓ Full 6-hour course attached. 5 real apps. Real deployment. Real revenue potential. From the guy who built a 7-figure automated business. Not theory. Not motivation. Actual hands-on building. The course is free. The tools are free. The knowledge is right here. The only thing that costs money is your decision to do nothing. And that cost compounds every single day. Follow Himanshu Kumar for more breakdowns that turn free YouTube videos into $10,000/month skill sets. Save this post. Watch the video. Build something this weekend that your Monday self will thank you for. Or don't. And wonder next year why nothing changed.
5:54:41

CANCEL Your Weekend Plans and Learn Vibe Coding Today, Start Making $10,000/Month Building Apps for People. $0 in Coding Experience. I made 5 AI Trading Bots & Apps Built in 6 Hours. Each One Worth $3,000-$15,000 to Clients. You Spent $500 on a Bootcamp and Still Can't Deploy a Landing Page. That's not the bootcamp's fault. That's you. People with zero coding skills are building full apps with payments, databases, and authentication using AI. Charging clients $5,000-$10,000 per project. Finishing in one afternoon. You're still Googling "should I learn Python or JavaScript first." This attached video is a goldmine. 6 hours. 5 real apps. From complete beginner to deploying revenue-generating products. One video. Free. Save it. Watch it this weekend. Not next weekend. Today. Now let me break down exactly what's inside and why you can't afford to ignore this. Save this post. You'll hate yourself if you lose it. ↓ Let's talk about why you still can't code... You bought the Udemy course. $12.99. Watched 3 lectures. Got confused. Told yourself you'd continue tomorrow. That was 8 months ago. You bought another course. $49.99. This one had better reviews. Watched the intro. Bookmarked the rest. Never opened it again. You signed up for a bootcamp. $5,000. Dropped out at week 4 because "life got busy." Life didn't get busy. You got scared. Three years. Hundreds of dollars. Multiple courses. Zero apps built. Zero projects deployed. Zero revenue generated. And now someone with zero coding experience is building full apps in hours using AI tools you haven't even tried. You're not falling behind slowly. You're falling behind at full speed. Save this post right now. This is the course that makes every other coding course you bought irrelevant. Follow Himanshu Kumar so you don't miss the breakdown. ↓ What is vibe coding and why should you care? Traditional coding: Learn syntax for 6 months. Build a to-do app. Feel proud. Realize nobody will pay for a to-do app. Give up. Vibe coding: Describe what you want to build. AI builds it. You guide, adjust, deploy. People pay for it. You're not writing code line by line. You're directing an AI agent that writes code for you. Think of it like this: Traditional coding = you're the construction worker. Vibe coding = you're the architect. The architect makes more money. The architect doesn't carry bricks. The architect doesn't need to know how to pour concrete. The architect needs to know what to build and why. That's vibe coding. And while you've been debating whether to learn Python or JavaScript first, people are skipping both and building apps that generate revenue. With zero coding knowledge. This isn't the future. This is right now. Save this post and follow Himanshu Kumar for more vibe coding breakdowns that actually make you money. ↓ What this 6-hour course covers. This isn't some 20-minute tutorial that shows you how to make a button change color. This is 6 hours. 5 complete apps. Real software engineering. Real deployment. Real money-making potential. Here's what you'll build: > Portfolio website - deployed live on Netlify > Full-stack client dashboard - with database and auth > Lead generation app - with API integrations > Thumbnail generator - with payment integration via Stripe > Splinter - a full SaaS product with pricing and marketing Not toy projects. Not "follow along and never use again." Actual apps that people pay for. Built with Gemini 3.1 Pro, Antigravity, Supabase, Next.js, Vite, and more. You know how many people charge $5,000+ to build a single one of these apps for a client? You'll be able to build all 5 by the end of this weekend. You can't afford to scroll past this. Bookmark this post. Follow Himanshu Kumar because I'm breaking down every tool in this stack separately. ↓ The tools you'll master. Gemini 3.1 Pro: Google's most powerful AI model. You'll use it to generate entire codebases. Not snippets. Entire apps. Antigravity: The AI coding environment that makes vibe coding actually work. Agent chat. MCP servers. Voice dictation. It's not VS Code with a chatbot bolted on. It's built from the ground up for AI-first development. Supabase: Your backend. Database. Authentication. All set up in minutes. Not weeks of configuration. Next.js + Vite: Modern frameworks that make your apps fast, scalable, and professional. Stripe: Payment integration. So your apps can actually charge people money. You know, the whole point. Claude Code: Yes, Claude Code is covered too. Because the best developers in 2026 don't use one AI tool. They use all of them. While you're still trying to decide which AI tool is "the best one," smart people are using all of them together and making money from every angle. Stop debating tools. Start using them. Save this post and follow Himanshu Kumar for deep dives into each of these tools. ↓ What you'll actually learn beyond just "building apps." This course doesn't just teach you to copy and paste prompts. You'll learn real software engineering: > Hosting and deployment > Modern software design patterns > Languages and frameworks > Version control and GitHub > Programming with AI agents and agent teams > Database design (SQL vs NoSQL) > Security audits > API integration > Payment processing This is everything a $15,000 bootcamp teaches. In 6 hours. For free. On YouTube. Your friend who spent $15K on a bootcamp is going to be really upset when you build better apps than them after watching one YouTube video this weekend. Don't tell them about this course. Or do. Their reaction will be priceless. This is a $15,000 education for $0. Save this post before it gets buried. Follow Himanshu Kumar for more free resources that make paid courses look like scams. ↓ The guy teaching this actually makes money. Not "makes money selling courses about making money." Actually makes money. Nick built automated businesses with Make . Most notably 1SecondCopy, a content company that hit 7 figures. Seven figures. From automation. He's not teaching theory. He's showing you what real systems that generate real revenue look like. 90% of coding teachers on YouTube have never shipped a product that made $1. They teach coding. They don't use coding to make money. This guy does both. That's why this course is different. You've been learning from people who teach for a living. Start learning from people who build for a living. Save this post. Follow Himanshu Kumar for more content from builders, not lecturers. ↓ Let me tell you what's really happening while you "think about learning to code." Every week that passes, AI coding tools get better. Every week that passes, more people learn vibe coding. Every week that passes, the market gets more competitive. Right now, vibe coding is still early. Not many people know how to do it well. Clients are desperate for someone who can build apps fast. $3,000 for a landing page with payments. $5,000 for a SaaS MVP. $10,000 for a full client dashboard. These are real prices people are charging for apps they built in a single day using the exact tools in this course. But this window won't last forever. In 6 months, everyone will know how to vibe code. In 12 months, it'll be a basic requirement. In 24 months, not knowing this will be like not knowing how to use email in 2010. You're either early or you're irrelevant. Right now you can still be early. But not if you spend this weekend on Netflix. The window is closing. Every weekend you waste is a weekend someone else uses to get ahead of you. Save this post. Follow Himanshu Kumar before this opportunity becomes obvious to everyone. ↓ The 5 apps you'll build and what they're actually worth. App 1: Portfolio Website. What clients pay for this: $500-$2,000. Time to build with vibe coding: 30 minutes. App 2: Client Dashboard. What clients pay for this: $5,000-$15,000. Time to build with vibe coding: 2-3 hours. App 3: Lead Generation Tool. What clients pay for this: $3,000-$8,000. Time to build with vibe coding: 1-2 hours. App 4: Thumbnail Generator with Payments. What clients pay for this: $2,000-$5,000. Or sell it as a SaaS for recurring revenue. Time to build: 1-2 hours. App 5: Splinter (Full SaaS Product). What clients pay for this: $10,000-$25,000. Or launch it yourself for monthly recurring revenue. Time to build: 2-3 hours. Total value of apps you can build after this course: $20,000-$55,000. Total cost of this course: $0. Total time investment: one weekend. You spend more than one weekend deciding which Netflix show to start next. At least this weekend would pay you back. Read those numbers again. Save this post. Follow Himanshu Kumar because I'll be breaking down how to sell each of these apps as a service. ↓ Here's the business model nobody's talking about. Learn vibe coding this weekend. Build 5 apps. Pick the one you're best at. Offer it as a service. "I build professional SaaS dashboards for businesses using AI. Faster than agencies. Fraction of the cost. $5,000 per project." 2 projects per month = $10,000/month. Working maybe 20 hours total. While you're applying for jobs that pay $4,000/month and require 5 years of experience you don't have, someone who watched this course last weekend just landed their second $5,000 client. No degree. No portfolio. No 5 years of experience. Just the ability to build what people need faster than anyone else. That's the entire business model. Learn fast. Build fast. Charge accordingly. Stop applying for jobs. Start creating them. Save this post. Follow Himanshu Kumar for the exact outreach scripts to land your first vibe coding client. ↓ Why you won't watch this course. Because it's 6 hours. "6 hours?? That's too long." You binged an entire season of a show last weekend in 8 hours. You scrolled Twitter for 4 hours yesterday. You spent 3 hours watching YouTube shorts that you don't even remember. But 6 hours to learn a skill that could make you $10,000/month? "I don't have time for that." You have time. You just don't have discipline. And that's the actual reason you're broke. Not the economy. Not the market. Not your circumstances. Your inability to sit down for 6 hours and learn something that changes your life. Everything else is a story you tell yourself to feel better about doing nothing. That's the uncomfortable truth. Save this post so it stares at you every time you open your bookmarks. Follow Himanshu Kumar because I'll keep reminding you until you actually do something. ↓ What happens this weekend determines your next year. Path A: Watch the course Saturday. Build your first app Sunday. Start offering services Monday. Land first client within 2 weeks. $5,000-$10,000/month within 60 days. Path B: Sleep in Saturday. Brunch Sunday. Netflix Sunday night. Monday morning alarm goes off. Back to the same job. Same salary. Same frustration. Same "I'll start next weekend." 52 weekends in a year. How many have you already wasted? Path A costs you one weekend. Path B costs you your entire future. Same video. Same information. Same 6 hours. Two completely different lives. ↓ Full 6-hour course attached. 5 real apps. Real deployment. Real revenue potential. From the guy who built a 7-figure automated business. Not theory. Not motivation. Actual hands-on building. The course is free. The tools are free. The knowledge is right here. The only thing that costs money is your decision to do nothing. And that cost compounds every single day. Follow Himanshu Kumar for more breakdowns that turn free YouTube videos into $10,000/month skill sets. Save this post. Watch the video. Build something this weekend that your Monday self will thank you for. Or don't. And wonder next year why nothing changed.

Himanshu Kumar

39,379 Aufrufe • vor 3 Monaten

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 → $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. ↓ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. ↓ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. ↓ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" — No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. ↓ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. ↓ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. ↓ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. ↓ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. ↓ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. ↓ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. ↓ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. ↓ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. ↓ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. ↓ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.
18:53

Made $530,000 with Ai Bot that started with $313. Didn't know how to code. Now this bots run 24/7 printing money while sleeping. I've made the exact step-by-step guide to build this Claude Code Polymarket trading bot. Prompts. Code. Risk settings. Paper trading checklist. Everything from zero to running bot. It's free. For 24 hours. After that I'm charging $499 for it. To grab it right now: 1. Comment "Claude Bot" 2. Like and Retweet this post 3. Follow me Himanshu Kumar ( I can't send DMs to non-followers ) I'm DMing everyone who Complete the 3 steps. I spent hundreds of thousands hiring developers because he was too scared to learn. Then learned Claude Code. Built algorithmic trading systems. $313 → $530,000. You have the same tools available right now. And you're using them to ask ChatGPT for Instagram captions. This attached video is a goldmine. Full live walkthrough. Claude Code building actual Polymarket trading bots. From zero. Every line of code. Every decision explained. Now let me break down why everything you're doing in trading is wrong and exactly how to fix it. Save this post. You'll hate yourself if you lose it. ↓ Let's start with why you keep losing money. You already know the answer. You just won't admit it. You overtrade. Every. Single. Day. You see a candle move. You feel something. You enter. No plan. No edge. No reason. Just feelings. Then it goes against you. You feel something else. Panic. Anger. Denial. You move your stop loss. Or you didn't set one at all. "It'll come back." It doesn't come back. So you take another trade. A revenge trade. Bigger size this time. Because you need to "make it back." That one fails too. Now you're emotional. Now you're tilted. Now you're using leverage you have no business touching. 40x. 50x. 100x. On a trade you entered because a candle looked "bullish" and some guy on Twitter said "send it." You get liquidated. Close the laptop. Punch something. Tell yourself you'll be "more disciplined" tomorrow. Tomorrow comes. Same cycle. Same result. Same liquidation. You've been doing this for months. Maybe years. And you still think the problem is your strategy. The problem isn't your strategy. The problem is you. Save this post right now. What I'm about to show you is the only way to remove yourself from the equation. Follow Himanshu Kumar so you don't miss any of this. ↓ Here's what's actually killing your account. It's not the market. The market doesn't care about you. It's not your indicators. RSI works fine. MACD works fine. They all "work." It's not your timeframe. It's not your broker. It's not the "manipulation." It's four things: 1. Emotions. You hold losers because hope feels better than loss. You cut winners because fear feels stronger than greed. You size up when angry. You skip trades when scared. Your emotional state determines your position size. That's insane. And you know it's insane. But you keep doing it. 2. Overtrading. You take 15 trades a day. Maybe 5 of them had actual setups. The other 10 were boredom. Boredom trades are the most expensive hobby in human history. 3. Leverage. You use 20x-50x on trades where you're not even sure about the direction. That's not trading. That's a casino with a nicer interface. 4. Fees. You're smashing market orders. Paying spread. Paying commission. On 15 trades a day. Your broker makes more money from your account than you do. Think about that. Your broker is profitable on your account. You're not. You're the product. Not the trader. These four things are why 90% of traders lose. Not bad luck. Not the market. You. Save this post and follow Himanshu Kumar because the solution is coming next. ↓ The solution is painfully obvious. Remove yourself from the equation. Not partially. Not "I'll be more disciplined." Not "I'll journal my trades." Not "I'll meditate before trading." Completely remove yourself. Build a bot. Let the bot trade. You go live your life. The bot doesn't feel emotions. The bot doesn't overtrade. The bot doesn't use reckless leverage. The bot doesn't smash market orders and bleed fees. The bot follows the rules. Every single time. Without exception. Without "just this once." Without "I have a feeling about this one." Rules in. Execution out. No human in the middle to mess everything up. That's algorithmic trading. And before your ego jumps in with "but I'm different, I have discipline" — No you don't. Your account balance proves you don't. If you had discipline, your account would be green. It's not. So you don't. Accept it. Automate it. Move on. This is the hardest truth in trading. Your discipline will always fail. A bot's won't. Save this post. Follow Himanshu Kumar for the exact bot setup that removes your emotions permanently. ↓ "But I don't know how to code." Neither did he. The guy in this video didn't know how to code for most of his life. Got held back in 7th grade. People counted him out early. Spent years building apps and SaaS businesses without writing a single line of code. Hired developers on Upwork instead. Spent hundreds of thousands of dollars paying other people to build what he could have built himself. Because he was scared to learn. That fear cost him years. And hundreds of thousands of dollars. Sound familiar? You're doing the same thing right now. Not with developers. But with your time. You're spending thousands of hours trading manually because you're scared to learn the thing that would make trading automatic. The fear of learning to code is costing you more than any bad trade ever did. Because every month you trade manually is a month of emotional decisions, overleveraged entries, and unnecessary losses that a bot would never make. And here's the thing that should really frustrate you: AI does the hard parts now. You don't need a computer science degree. You don't need to work at a hedge fund. You don't need to be "good at math." Claude Code writes the code for you. You just need to think clearly about trading ideas. That's it. If you can describe a strategy in English, Claude can build it in Python. "I don't know how to code" stopped being a valid excuse in 2024. It's 2026. You're 2 years late on that excuse. Find a new one. Or stop making excuses entirely. Save this post. Follow Himanshu Kumar because I'm showing you how people with zero coding experience are building profitable bots. ↓ The process that actually makes money. Three letters. R. B. I. Research. Backtest. Implement. That's it. That's the entire process. Every single day. Research: Find an idea. A pattern. A market inefficiency. Don't trade it yet. Don't even think about trading it yet. Just research it. Backtest: Test the idea against historical data. Does it work? Not "does it look good on one chart." Does it work across thousands of trades? Across different market conditions? Across in-sample AND out-of-sample data? If no, kill it. Find another idea. If yes, move to step 3. Implement: Build the bot. Deploy it. Paper trade first. Then live with small size. Scale only on evidence. Research. Backtest. Implement. Every day. No exceptions. You know what your current process is? Feel. Enter. Pray. F. E. P. Feel bullish. Enter a trade. Pray it works. That's not a process. That's gambling with a TradingView subscription. RBI is the only process that works. Save this post. Tattoo it on your forearm. Follow Himanshu Kumar for daily RBI breakdowns. ↓ What Claude Code actually does that your manual process can't. You can maybe test 3-5 strategy ideas per week. Manually adjusting parameters. Manually checking results. Manually writing code (badly). Claude Code tests 50-100 ideas per week. With parallel agents running simultaneously. Multiple strategies being built, tested, and validated at the same time. While you sleep. The guy in this video spends 4-8 hours a day building systems with Claude Code. Not trading. Building. Research. Backtest. Implement. Then iterate. Improve. Optimize. Every day the systems get better. Every day the edge compounds. Every day the bots get smarter. While you? You spend 4-8 hours a day staring at charts making the same mistakes you made last month. Same indicators. Same patterns. Same entries. Same losses. He's iterating forward. You're running in circles. Same 8 hours per day. Completely different outcomes. Because he's building systems. And you're feeding a casino. Stop feeding the casino. Start building the machine. Save this post and follow Himanshu Kumar for the Claude Code workflow that iterates strategies while you sleep. ↓ Jim Simons. That's the benchmark. You probably don't know who Jim Simons is. And that tells me everything about how seriously you take trading. Jim Simons. Mathematician. Founded Renaissance Technologies. Built a net worth of $31 billion. 100% from algorithmic trading. Not one single manual trade. Not one "gut feeling" entry. Not one RSI divergence. Not one "smart money concept." Algorithms. Bots. Systems. Data. $31 billion. His fund averaged 66% annual returns for over 30 years. While you're excited about making $200 on a trade that you'll give back tomorrow. The best trader in human history never placed a manual trade in his life. And you think your edge is staring at a 5-minute chart with bloodshot eyes at 2 AM? Your edge is building the system. Not being inside it. Jim Simons is the benchmark. Everything else is noise. Save this post. Follow Himanshu Kumar because I'm building toward the same goal and showing every step publicly. ↓ What you need to understand about patience. This is not get-rich-overnight. The guy in this video says it directly: "This channel is not for people looking to get rich overnight. It's not plug and play. There are no shortcuts. If you're impatient, this probably isn't for you." And that's exactly why most people will fail at this. Because you want results now. Today. This trade. You don't want to spend a week building a bot. You don't want to paper trade for 2 weeks. You don't want to test 50 ideas to find 1 that works. You want to copy someone's bot, run it live with your rent money, and be rich by Friday. That's why you'll be broke by Friday. The guy making $2.3M spent months iterating. Testing. Failing. Rebuilding. Testing again. He was patient when you would have quit. He was calm when you would have panicked. He was consistent when you would have given up. Patience isn't just a virtue in trading. It's the only virtue. Without it, everything else fails. Impatience is the most expensive personality trait in trading. Save this post. Follow Himanshu Kumar and learn to build systems with the patience that actually pays. ↓ The live streams where the real learning happens. The YouTube video is the trailer. The live streams are the movie. Real-time bot building. Real-time questions answered. Real code shown. Real mistakes made and fixed. Not polished highlight reels where everything works perfectly. Actual development. Where things break. Where strategies fail. Where code doesn't compile. Where the fix takes 2 hours. Because that's what real development looks like. And seeing the messy parts is more valuable than any polished tutorial. Because when your bot breaks at 3 AM, you need to know how to fix it. Not just how to celebrate when it works. The streams mix beginner and advanced. Start with how to automate trading. How to use AI for code generation. Then dive into the daily work. Claude Code. Parallel agents. Constant iteration. Live debugging. 4-8 hours of real algorithmic trading development. Live. Uncut. No filter. Most "trading education" shows you the wins. This shows you the work. Save this post. Follow Himanshu Kumar for the stream schedules and breakdowns. ↓ The belief that changes everything. Code is the greatest equalizer. Not money. Not connections. Not a degree. Not where you grew up. Not what school you went to. Code. Once you can build systems, you can build anything. For the rest of your life. A trading bot today. A SaaS product tomorrow. An automation business next month. A completely different life next year. The skill isn't "algorithmic trading." The skill is building systems. And that skill transfers to everything. The guy who can build a trading bot can also build a lead gen tool. Can also build a content pipeline. Can also build a SaaS product. Can also build literally anything that runs on logic and code. One skill. Infinite applications. And AI makes learning it 100x easier than it was 5 years ago. You don't need to be smart. You don't need talent. You need Claude Code and the willingness to sit down and build something instead of consuming content about building something. Building is the skill. Everything else is entertainment disguised as education. Save this post. Follow Himanshu Kumar because I'm showing you how to build, not just how to watch. ↓ If any of this applies to you, pay attention. If you've lost money from overtrading. If you've been liquidated. If you know trading is the vehicle but manual execution keeps crashing you. If you've tried "being more disciplined" and it never lasted more than a week. If you keep saying "next month I'll start automating." If you've spent more money on courses than you've made from trading. There is a better way. It's not a magic indicator. It's not a signal group. It's not a $997 mentorship from a guy who makes money teaching, not trading. It's building your own system. A system that trades without emotion. A system that follows rules without exception. A system that runs while you sleep. A system that compounds while you live your life. That's the answer. It's always been the answer. You've just been too scared to accept that the solution requires building something instead of buying something. ↓ What the next 30 days look like if you actually commit. Week 1: Watch the video. Learn Claude Code basics. Build your first simple strategy. Run your first backtest. Week 2: Iterate. Let Claude improve the strategy. Run Monte Carlo validation. Paper trade. Week 3: Go live with $50-100. Tiny positions. Watch every trade. Compare to paper results. Week 4: Scale based on evidence. Not based on excitement. Not based on one good day. Based on data. 30 days from now you either have a running bot that trades without your emotions destroying every position. Or you're exactly where you are right now. Reading another post. Making another promise. Breaking it by Tuesday. Same 30 days either way. Different actions. Different results. Different life. ↓ Full video tutorial attached. Live bot building with Claude Code. From zero to running Polymarket trading bot. Every line of code. Every decision explained. The video is free. Claude Code is available now. The market is open 24/7. The only thing standing between you and a profitable trading bot is the same thing that's been standing there for months. You. Get out of your own way. Follow Himanshu Kumar for daily AI trading bot breakdowns, live build sessions, and the full RBI process. Save this post. Watch the video. Build the bot. Or keep trading manually and keep losing. The choice has never been easier. And you've never been more stubborn about making the wrong one.

Himanshu Kumar

37,300 Aufrufe • vor 3 Monaten

Everyone is talking about Vibe Coding (Using AI to Create Apps Only using AI) This is the most Comprehensive Guide for Vibe Coding with Cursor (By Far) 250 Minutes, All the vibe code basics of cursor, plus 4 Projects in one video! This is how I, as someone who has never written a line of code, approach building apps (every day). Part 1A Intro to Cursor, Composer, and some basics --------------------- 00:00 Intro 03:41 Downloading Cursor 06:09 What the hell is Composer? 10:47 A Note on Context and Keeping Composer Threads Small 11:38 Simple Desings with Cursor Composer From Blank Project 14:04 Editing a Simple Animation With Cursor Composer 16:35 Setting Up The Voice to Talk to Cursor Composer Whispr Flow 17:54 Lets an Early 2000's Landing Page Part 1B AI Image Generator --------------------- 23:59 Using the GitHub Template to Create a NextJS App 26:43 Template is Open, Let's Edit it 28:55 Drawing Out My Idea With Whimsical 30:11 First Prompt Using Place Holders For Image Generation 32:10 Accept All Vs Save All and Restoring in Composer (Saving your work) 33:54 Adding AI Feature (Brief Teaser, Deep Dive Later) 35:15 What is an API 37:22 Perplexity the best place to learn about API's 40:21 Api keys and running prompt for first AI Feature 42:48 Debugging, Woohoo! Learn to love this :) 43:20 Inspect - Console, In Browser Debugging Hack 48:02 AI Image Generation Works! Lets add more Part 2: Landing Page ---------------------- 51:03 Pause and Reflect, What have we done so far? 53:41 Plan for rest of video 54:34 Ok Let's Talk about (1) Designs 56:19 GitHub is like --sref for those who do image gen 58:20 Starting Cursor project from a GitHub Repo we found on Perplexity 01:00:48 Yolo Mode... Wtf is that? 01:02:38 Inspecting GitHub Repo's Examples, to use in our landing page 01:02:58 The Project We're making - A landing page 01:03:56 Landing Page from Screenshot 01:06:17 Making Changes to Landing Page 01:11:42 Making a more epic section 01:13:42 The Essence of Vibe Coding 01:15:17 Creating Cool Testimonials Section From Screenshot 01:18:18 Deploy to Vercel! But First New Repo on GitHub 01:20:45 Ok it's on GitHub... Now lets do vercel 01:21:17 Untechnical Explanation of what Vercel is Lol 01:24:18 Connecting Custom Domain (Bought on Name Cheap) To Vercel Deployment Part 3: App With Database and Authentication ---------------------- 01:27:59 Recap and Prep For The Bigger Project! 01:35:13 Getting Started from Template (Again) 01:38:52 Setting Up Database and Authentication (Firebase) 01:44:01 Back To Cursor, Let's Set up The Auth in the app 01:48:35 Switching to mermaid because compatibility issues 01:51:13 Using AI (Claude) to Generate Mermaid Diagrams 01:52:19 Adding Docs to Cursor to use AI Features over and over again 01:54:38 Let's Troubleshoot 01:56:10 Adding View Button and EDIT WITH AI 02:01:45 AI Diagram Edit Feature is DOPE 02:03:17 Using Search Feature on Cursor to find text in Codebase 02:05:55 Lets add ability to save these to Database 02:09:33 What does saved to Google Firebase even mean? 02:13:00 We can Export as PDF! 02:15:48 GitHub and Vercel Again! 02:17:27 Vercel with CLI From Cursor 02:20:52 Setting Vercel Domain as an Authorized Domain 02:27:34 How To Learn More
2:28:16

Everyone is talking about Vibe Coding (Using AI to Create Apps Only using AI) This is the most Comprehensive Guide for Vibe Coding with Cursor (By Far) 250 Minutes, All the vibe code basics of cursor, plus 4 Projects in one video! This is how I, as someone who has never written a line of code, approach building apps (every day). Part 1A Intro to Cursor, Composer, and some basics --------------------- 00:00 Intro 03:41 Downloading Cursor 06:09 What the hell is Composer? 10:47 A Note on Context and Keeping Composer Threads Small 11:38 Simple Desings with Cursor Composer From Blank Project 14:04 Editing a Simple Animation With Cursor Composer 16:35 Setting Up The Voice to Talk to Cursor Composer Whispr Flow 17:54 Lets an Early 2000's Landing Page Part 1B AI Image Generator --------------------- 23:59 Using the GitHub Template to Create a NextJS App 26:43 Template is Open, Let's Edit it 28:55 Drawing Out My Idea With Whimsical 30:11 First Prompt Using Place Holders For Image Generation 32:10 Accept All Vs Save All and Restoring in Composer (Saving your work) 33:54 Adding AI Feature (Brief Teaser, Deep Dive Later) 35:15 What is an API 37:22 Perplexity the best place to learn about API's 40:21 Api keys and running prompt for first AI Feature 42:48 Debugging, Woohoo! Learn to love this :) 43:20 Inspect - Console, In Browser Debugging Hack 48:02 AI Image Generation Works! Lets add more Part 2: Landing Page ---------------------- 51:03 Pause and Reflect, What have we done so far? 53:41 Plan for rest of video 54:34 Ok Let's Talk about (1) Designs 56:19 GitHub is like --sref for those who do image gen 58:20 Starting Cursor project from a GitHub Repo we found on Perplexity 01:00:48 Yolo Mode... Wtf is that? 01:02:38 Inspecting GitHub Repo's Examples, to use in our landing page 01:02:58 The Project We're making - A landing page 01:03:56 Landing Page from Screenshot 01:06:17 Making Changes to Landing Page 01:11:42 Making a more epic section 01:13:42 The Essence of Vibe Coding 01:15:17 Creating Cool Testimonials Section From Screenshot 01:18:18 Deploy to Vercel! But First New Repo on GitHub 01:20:45 Ok it's on GitHub... Now lets do vercel 01:21:17 Untechnical Explanation of what Vercel is Lol 01:24:18 Connecting Custom Domain (Bought on Name Cheap) To Vercel Deployment Part 3: App With Database and Authentication ---------------------- 01:27:59 Recap and Prep For The Bigger Project! 01:35:13 Getting Started from Template (Again) 01:38:52 Setting Up Database and Authentication (Firebase) 01:44:01 Back To Cursor, Let's Set up The Auth in the app 01:48:35 Switching to mermaid because compatibility issues 01:51:13 Using AI (Claude) to Generate Mermaid Diagrams 01:52:19 Adding Docs to Cursor to use AI Features over and over again 01:54:38 Let's Troubleshoot 01:56:10 Adding View Button and EDIT WITH AI 02:01:45 AI Diagram Edit Feature is DOPE 02:03:17 Using Search Feature on Cursor to find text in Codebase 02:05:55 Lets add ability to save these to Database 02:09:33 What does saved to Google Firebase even mean? 02:13:00 We can Export as PDF! 02:15:48 GitHub and Vercel Again! 02:17:27 Vercel with CLI From Cursor 02:20:52 Setting Vercel Domain as an Authorized Domain 02:27:34 How To Learn More

Riley Brown

367,311 Aufrufe • vor 1 Jahr

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.
25:22

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,363 Aufrufe • vor 3 Monaten

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!
19:06

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

264,136 Aufrufe • vor 2 Monaten

🟢GIVEAWAY🟢 Best comments or memes about this whole circus + RT this post. 10 winners will each get $50💎 (For evidence, supporting materials, and context, read both articles and watch the video included in the article I posted yesterday) Housebets.com & Porchy pay your debts A few people told me they did not fully understand the first article because there were too many moving parts: leaderboard accounts, rewards, weekly dates, monthly bonus, Tequity, game categories, withdrawals, Provably Fair, seed changes, migration, support tickets, ledgers and founder messages. Fair enough. The evidence is already there, and I still recommend reading the full articles and, above all, watching the video, because the video shows the reward system failing live. But this text is the cleaner version: the full story explained in plain English, without assuming the reader knows anything about crypto casinos, leaderboards or lossback systems. From all the evidence I’ve gathered, the Housebets story is not a normal “player lost money” complaint. It looks like a full transparency failure across the whole product: leaderboard, rewards, withdrawals, game categories, Provably Fair / Tequity mapping, support, migration and founder response. Housebets sold itself as a rewards-first casino: public leaderboards, weekly/monthly bonuses, fast withdrawals, VIP treatment and Provably Fair games. But every time I asked for the records behind those systems, snapshots, ledger entries, weekly cycles, GGR/NGR, slider logs, PF seed mapping, Tequity round IDs, withdrawal approval logs, the answer became some version of “forwarded to the relevant department.” This started long before the public dispute. I was not some random angry player who appeared after one bad session. In January I was helping Housebets and giving product feedback. I literally told support on 27 January that I was “testing the website for George,” while already dealing with a non-instant withdrawal and a 100% welcome bonus that had not applied. Support even asked me for “proof about your testing job.” The same chat shows the advertised 100% Welcome Bonus, the bonus not applying, and support saying the withdrawal needed internal confirmation instead of being instant. The welcome bonus issue never looked clean. Housebets advertised a 100% Welcome Bonus up to $1,000 on first deposit; I deposited, contacted support, and the bonus did not apply. Then support effectively turned a first-deposit bonus into a second-deposit workaround because the first one had not been applied properly. On 31 January I came back after another deposit and told them the bonus still had not been applied, even though I had already followed support’s instructions. Edward replied that he had “forwarded” the concern to the team. The same 100% welcome bonus was still being advertised in March. By April, the rewards system was already showing serious problems. I had the weekly slider at 100% lossback and told support I had lost money but the weekly did not appear. Jacky said the weekly was generated every Thursday at 00:01 UTC and gave actual internal figures: GGR $6,250, Total Bonus $6,083.99, NGR $168.31. So Housebets clearly had internal calculations when it wanted to explain why something might not pay. But when I later asked for full calculations, those same numbers suddenly became impossible to produce. Then on 18–19 April, the rewards page was bugged and would not let me claim. Support could see a pending weekly bonus of $717.37, but I could not claim it from the UI. Tee said it had been forwarded to the relevant department. That $717.37 later appears in the bonus ledger as Rakeback (20 Apr) 717.37089061, so I am not saying that specific one stayed unpaid forever. The point is worse: already in April, support could see a pending weekly reward while the player-facing reward page did not work. For a casino built around rewards, that is not a small bug. That is the product. In May, the UI and account data kept failing basic trust checks. On 8 May, I deposited 400 USDT; support said it had been credited, but I could not see it, and the proposed fix was to log out, clear cookies and cache. On 16 May, I asked why total deposits and withdrawals had disappeared from the menu; support said the platform was “in continuous evolution.” On 17 May, I asked for my total deposits and withdrawals, and support said they did not have direct access to that consolidated summary and would email it. That full official ledger did not arrive. So when Housebets later defends itself with UI screenshots, remember: this was the same UI where deposits could be credited but invisible, totals disappeared, rewards pages bugged, and support could not access consolidated account totals. Withdrawals were also not what was advertised. On 16 May, I asked why a crypto withdrawal was pending if withdrawals were supposed to be instant. Tee answered: “A few withdrawals require manual approval,” then added, “Our withdrawals are typically instant but…” That matters because a few days later the withdrawal delay became real damage. On 25 May, I told support before a match that I needed the funds to place a time-sensitive bet on another site in less than 20 minutes. I explained I wanted to bet around 60k at odds of 2.55. The withdrawal did not arrive in time. Later I told them the bet won and that I missed around 90k in profit because Housebets took more than two hours despite being warned before the match started. Jacky said he would raise the compensation case to the VIP team. Nobody resolved it. This was not one delayed withdrawal either. In my formal complaint I reconstructed several withdrawal delays: 23 May 02:55 → 08:03, around 5h08m; 25 May 03:05 → 08:09, around 5h04m; 17 May 03:54 → 08:02, around 4h08m; 18 May 04:46 → 08:11, around 3h25m; 16 May 05:23 → 08:12, around 2h49m. That is not “instant withdrawal.” And if later marketing says withdrawals are much faster now, the obvious question is: if this was the faster version, what did slow look like? The Provably Fair / Tequity side was another major issue. On 17 May I asked support how to verify an old Blackjack round. I did not ask for a generic explanation of Provably Fair; I asked where I could see the server seed, client seed, nonce and result for previous games. Support sent me to bet history, mentioned RTP, gave a generic PF explanation and showed the current Dice seed screen. When I said that did not let me verify previous games, they told me to clear cookies/cache. After doing that, I saw a new client seed and nonce 1 even though I had not played with that seed pair. I asked if Housebets changes seeds on every login. Support could not answer and told me to contact VIP. That seed/session behaviour is important. I later recorded video evidence around the seed changing after clearing cookies/cache and asked for the exact mapping: Housebets account ID → Tequity/provider player ID → session/currency context → seed pair → server seed hash → revealed server seed → client seed → nonce/cursor → raw outcome → final result. Housebets cannot sell Provably Fair if the player cannot verify historical bets, and “contact VIP” is not a verification algorithm. On 24 May, I asked for raw verification data for a specific Tequity Blackjack round: Round ID e1648d60-0da1-4433-a5ab-9ae39f5302e3, Blackjack, Tequity, bet amount 11,346 USDT, client seed O3YBZF7LBu, server seed hash starting 712875.... I asked for revealed server seed, nonce, full result JSON, card draw order and verification algorithm. I also asked about an apparent duplicate-card/deck question. Tee replied: “I don’t have the answers to your questions right now, but I’m forwarding your request to the relevant department.” That same day, I asked for a full audit of six Dice bets of 11,400 USDT each, total 68,400 USDT. I requested bet IDs, provider round IDs, roll results, seed data, balance ledger, request/session logs, security logs, retry flags, provider records and a full technical reconciliation. Tee replied: “I will forward this to the relevant department.” So when I asked for raw data, the answer was not data. It was forwarding. Again. There were also many large loss clusters that required reconciliation because of those unresolved PF, Tequity, category, RTP and session questions. In my complaint I listed clusters such as 25 May 02:17–02:54 Blackjack around 169,932 USDT; 16 May 12:31–13:26 Dice around 90,571.92 USDT; 26 May 02:48–03:58 Mines around 89,199 USDT; 24 May 06:20–06:21 Dice at 68,400 USDT; 26 May 00:11–01:41 Blackjack around 59,910 USDT; 25 May 22:51–22:59 Dice around 59,576 USDT; and several more between 40k and 56k. I am not saying every losing cluster proves manipulation by itself. I am saying that when PF mapping, provider logs, RTP/HE, category mapping and seed/session behaviour are unresolved, these sequences need a real reconciliation. The leaderboard is where the story becomes very hard for Housebets to explain. Around 19–20 May, two new accounts, elmourabut and lucasmartirini, appeared and started climbing every day at a vertiginous pace. Not normal slow leaderboard growth. Not a casual player building volume over time. They were created around that period and then started rising with huge wagering in a way that looked extremely unnatural for brand new accounts. By 29 May, I was first on both weekly and monthly leaderboards, and those two accounts were directly behind me with huge volume. In the monthly leaderboard screenshots, I was around $3.33M wagered, while elmourabut was around $1.29M and lucasmartirini around $1.08M. In the weekly leaderboard, I was around $1.096M, while those two accounts were around $635k and $578k. They were not normal accounts sitting at the bottom; they were directly behind me, applying pressure. In my formal complaint I recorded that elmourabut joined on 19 May and lucasmartirini on 20 May, that they showed zero visible withdrawals, large deposits/wagering and significant card-game volume, and I asked Housebets to confirm they were not staff, test, QA, admin, house-controlled, affiliate-controlled, internally funded, promotional, bonus-only or multi-account related accounts. This matters because a leaderboard is not passive. It is gamification. It makes players defend rank. When two new accounts appear behind you with hundreds of thousands or more than a million in volume, you are pressured to keep wagering. In my case, the disputed deposit sequence from 25 May 22:23 to 26 May 02:09 totals 91,168.375326 USDT. That sequence begins with 1,000.00 at 22:23 and continues with repeated deposits until 2,879.148969 at 02:09. The video later shows why those dates matter: there were deposits coming in, no gameplay withdrawal offsetting the sequence, a balance basically at zero, and later a leaderboard prize shown as P/L. I formally asked Housebets to confirm those two leaderboard accounts were real and eligible, and also to preserve wager logs, transaction records, balance adjustment logs, account flags, leaderboard calculation snapshots, support ticket logs, Telegram/email records and internal notes. Edward said he forwarded the request. In the same thread, he added that they were “working on fixing an issue regarding the weekly bonuses,” and then said the weekly countdown was “not currently on Thursday evenings.” So the leaderboard issue and the weekly bonus issue are linked in time and support context. After that, Housebets confirmed by email that elmourabut and lucasmartirini were “legitimate and eligible accounts.” That email is the trap door. If they were legitimate and eligible, they should have remained in the leaderboard with their volume. If they were not, Housebets should never have confirmed them as legitimate and eligible. After that confirmation, the accounts disappeared from the leaderboard or stopped appearing in the positions their previous wagering required. I went back to support on 30 May and wrote: “There has been a material post-confirmation leaderboard change involving two accounts that Housebets had already confirmed as legitimate and eligible. I need the exact reason, timestamp, logs, and recalculation basis.” Edward said the matter was flagged and that I could expect a prompt response. I am still waiting for the actual explanation. Why did they disappear? My read is simple: because every hour that passed, there was more evidence around those accounts. They had been created around the same period, they were climbing at a speed that looked anything but human, they showed no visible withdrawals in the data I could see and reported, they appeared to be generating huge volume in unclear game categories, and the games/categories tied to that volume did not even make sense from the player-facing UI. When I started asking what they were actually playing, what Card meant, whether the volume was Tequity / UnOriginals / House Games, what RTP and house edge applied, and where the logs were, the questions became uncomfortable. Keeping those accounts visible became harder than removing them. So they disappeared. The game category issue made the leaderboard even more suspicious. On 30 May, I asked support why my own stats showed almost all my volume under Slots / Tragamonedas when I did not play real slots. I told them: “i dont play 3$ in unoriginals,” “i played all 3M in unoriginals,” and “ive never play slots.” I asked what “Card” was, where that game was, what RTP and house edge it had. Monica said Card was mainly Blackjack, Baccarat and Poker variants. Marcus later said the team was investigating why it showed that I mostly played slots when I had not. He could not give the exact game, RTP, HE, provider, category mapping or contribution logic. That matters because those same unclear categories were connected to leaderboard volume. If the site cannot clearly explain whether volume is Slots, Card, UnOriginals, House Games, Blackjack, Baccarat, Always 9 Baccarat or Tequity, then the leaderboard is not auditable for the player. I even asked which UnOriginals those two accounts were playing, and support told me to look at Live Bets. That is not an answer. I was not asking for gossip; I was asking what exact games generated leaderboard volume, what RTP/HE applied and whether that volume was eligible. There is also an earlier leaderboard-related precedent: Porchy had already told me in February that I would lose leaderboard places if I did not rename, because too many people were messaging support saying the site was not being fair due to my name and it “doesn’t make us look good.” That matters because it suggests leaderboard positioning was not treated as a sacred, untouchable system when public perception was involved. If leaderboard positions can be threatened for image reasons, then later claims that everything is purely automatic deserve scrutiny. Then Porchy made the leaderboard situation worse. Instead of producing logs or snapshots, he later said the leaderboard had “abusers” on it, that they were removed to help other players, and that it never affected me. Later he said they paid every single person, “even these abusers,” then called me “begging for money.” That creates a direct contradiction: Housebets confirmed the accounts as legitimate and eligible, then Porchy referred to leaderboard “abusers.” If they were abusers, why were they confirmed as legitimate and eligible? If they were eligible, why did they disappear? If they never affected me, where are the historical snapshots proving that? Once those accounts disappeared, Housebets paid the leaderboard prizes. On 1 June, the bonus ledger shows two Leaderboard entries: 5,007.46111706 and 1,001.49222341, totaling 6,008.95334047. That part was paid. But then Act Two started: the weekly and monthly rewards did not appear as separate ledger entries. The same bonus ledger shows those two 1 June entries as Leaderboard only, not Monthly Bonus, not Weekly Reload, not Lossback. The weekly timeline is a mess. On 28 May, the dashboard / UI said the weekly bonus was claimable every Thursday at 00:01 UTC, and the monthly was available on the 1st at 00:01 UTC. That same night I told support the weekly had shown as available, then reset to 6 days without paying. Later I sent screenshots and wrote: “1M wagered and 0.2$.” Jacky said he had raised the issue to the technical team. So the weekly failure was reported live, not reconstructed after the fact. The next day, 29 May, Edward said they were fixing an issue regarding weekly bonuses and that the weekly countdown was “not currently on Thursday evenings.” Then on 1 June, Spencer said the May weekly bonuses were 7th, 14th, 21st, and then due to migration the weekly moved to Monday, so there was one on the 25th on the new platform. He also said the 25 May weekly covered gameplay from 21–24 May, and that tech was looking at that plus the monthly bonus. The ledger does show a 25 May 02:10 Rakeback entry of 1,996.08334791, which likely corresponds to that 21–24 May weekly. But my major loss sequence starts about 20 hours later, on 25 May at 22:23, and continues until 26 May at 02:09. So the 25 May weekly cannot cover those losses. If weekly was still Thursday, the 25/26 losses should have been in the 28 May weekly. But the bonus ledger on 28 May shows only two tiny Rakeback entries, 0.28373945 and 0.00280958. If weekly moved to Monday because of migration, those losses should have appeared in the next weekly after 25 May. But on 1 June the ledger only shows Leaderboard entries. Then the final video shows the next Weekly Reload reaching zero, paying nothing and resetting to 6d 23h. So the same loss sequence appears to fall into no paid weekly cycle. The 4 June support conversation makes this even more ridiculous. After I recorded the weekly reset video, I asked support a very simple question: what were the last weekly dates/cycles? The dashboard / support flow again said weekly bonuses are claimable every Thursday at 00:01 UTC. Jacky confirmed: “Weekly bonuses can be claimed every Thursday at 00:01 UTC in the Rewards tab,” and added that if not claimed by the following Wednesday at 23:59 UTC, it expires. But when I asked for the exact last four dates, Jacky said he had to check with the relevant department. When I pressed again, he said, “Sorry, As I am only a CS, Let me raise your concerns to relevant department.” I asked whether support did not have the information or simply could not answer. He replied: “Do you have any other concerns?” They use weekly cycles to decide whether to pay, but support cannot explain the weekly cycle. The monthly is missing too. The dashboard / UI said the monthly bonus is based on activity and VIP level from the previous month and is available on the 1st at 00:01 UTC. In May I had more than 3,258,023.0829 wagered according to the formal complaint data. I also have proof/video that the monthly slider was set to 50/50. On 1 June, Spencer first told me I had claimed the Monthly Bonus at 1:12am BST around the same time as the monthly leaderboard reward. I immediately said I only received leaderboard prizes. Then Spencer changed the answer: “Our tech team are still actively working on issues regarding the monthly bonuses.” So first the monthly was claimed, then tech was still fixing it. The ledger still shows no Monthly Bonus entry. Housebets then seems to rely on “up overall” as a defence. But the video and ledger show why that does not work. My weekly/monthly profile later showed around +6,008 P/L with 0 deposits, 0 wagered and around 6,008 in bonuses. That number matches exactly the two 1 June Leaderboard payments. So the UI is showing leaderboard rewards as P/L. Then support used “up overall” to say I was not eligible for weekly lossback. That is not a clean lossback calculation. That is using a leaderboard reward as apparent profit to deny a lossback that should be based on actual eligible losses. There were also smaller reward-confusion issues along the way. On 22 May I asked for all pending bonuses,weekly, monthly, rakeback, level-up, anything, and support said the internal team would manually verify whether everything had been credited correctly and email me. On 24 May, I asked about level-up rewards because the reward looked like $3,500 for Pearl; support clarified it was $3,500 total across all Pearl levels, $500 per level. These are not the core issues, but they are part of the same pattern: rewards marketing, unclear UI, manual verification, emails that do not arrive, and players having to chase basic explanations. Then there is the migration. On 25 May, after the delayed withdrawal, missing VIP contact and unresolved issues, support told me my account would be moved to the new platform and that this upgrade would offer a better withdrawal process and fix many issues. Before that migration, I explicitly requested that no account data, internal data, logs, balance history, bonus history, bet history, provider records or pending issues be deleted. The response: “Your request has been relayed to the relevant department.” Again, forwarding. But if the old data is safe, Housebets should provide the old leaderboard snapshots, old weekly states, old bonus logs, old Tequity mapping and old withdrawal approval logs. The founder response did not fix anything. When Porchy finally engaged, he did not provide the records. He framed the settlement request as “so you want $100,000?” and asked whether I needed it or else I was going to post on X. I had already made clear this was not money for silence; I asked for logs, snapshots, withdrawal records, calculations and a counter-calculation if Housebets disagreed. He later referred to “abusers,” told me I was “up overall,” said “You are begging for money,” and suggested I “just do this to casinos.” Still no ledger. Still no weekly calculation. Still no monthly entry. Still no PF/Tequity mapping. Still no leaderboard snapshots. Another player also contacted me with screenshots pointing to similar categories of issues: private deals, leaderboard payout disputes, migration/account merge problems, missing history and a tiny monthly bonus despite claimed losses. I am not using that player’s case as the foundation of my claim without his full ledger, but it matters because it suggests the same type of opacity may not be isolated: private VIP/reward deals, leaderboard eligibility, monthly bonus calculations, migration and unclear history. If Housebets has private deals that affect leaderboard eligibility or rewards, it must explain how those deals interact with public leaderboards. So the overall picture is this: Housebets sold a public leaderboard and rewards system that pressured real wagering. Two new accounts appeared directly behind me with huge volume, were confirmed as legitimate and eligible, then disappeared after I asked for logs and questioned game categories. Housebets could not explain the exact games, RTP, house edge or category mapping behind the volume. The accounts were later framed by Porchy as “abusers,” contradicting the earlier eligibility confirmation. Once Housebets paid me the leaderboard prizes, those prizes were shown as P/L, and that contaminated P/L was then used to claim I was “up overall” and not eligible for lossback. At the same time, my real 25 May 22:23 → 26 May 02:09 loss sequence of 91,168.375326 USDT appears in no clean weekly cycle. The 25 May weekly covered 21–24 May according to Spencer, so it cannot cover that loss sequence. The 28 May weekly showed only tiny Rakeback entries and was already reported as broken. The 1 June ledger shows only Leaderboard entries. The later video shows Weekly Reload reaching zero, paying nothing and resetting. And when I ask support for the exact weekly calendar, they cannot answer and send it to the relevant department. The monthly is the same story. The dashboard / UI says it is based on activity and VIP. I had more than 3.25M wagered in May. Spencer first says I claimed it, then says tech is still working on monthly bonuses. The ledger shows no Monthly Bonus. If Housebets says I was not eligible, they need to show the formula, slider history, cycle, GGR/NGR, eligible loss/activity, deductions and ledger result. If they cannot, “not eligible” is just another label. And this opens another can of worms: Tequity / provider configuration. Housebets cannot hide behind “the provider” whenever something goes wrong. The player does not deposit with Tequity. The player does not withdraw from Tequity. The player does not speak to Tequity support. The player does not compete in a Tequity leaderboard. The player plays on Housebets, with a Housebets wallet, Housebets UI, Housebets rewards, Housebets leaderboard and Housebets support. 1/2
22:49

🟢GIVEAWAY🟢 Best comments or memes about this whole circus + RT this post. 10 winners will each get $50💎 (For evidence, supporting materials, and context, read both articles and watch the video included in the article I posted yesterday) Housebets.com & Porchy pay your debts A few people told me they did not fully understand the first article because there were too many moving parts: leaderboard accounts, rewards, weekly dates, monthly bonus, Tequity, game categories, withdrawals, Provably Fair, seed changes, migration, support tickets, ledgers and founder messages. Fair enough. The evidence is already there, and I still recommend reading the full articles and, above all, watching the video, because the video shows the reward system failing live. But this text is the cleaner version: the full story explained in plain English, without assuming the reader knows anything about crypto casinos, leaderboards or lossback systems. From all the evidence I’ve gathered, the Housebets story is not a normal “player lost money” complaint. It looks like a full transparency failure across the whole product: leaderboard, rewards, withdrawals, game categories, Provably Fair / Tequity mapping, support, migration and founder response. Housebets sold itself as a rewards-first casino: public leaderboards, weekly/monthly bonuses, fast withdrawals, VIP treatment and Provably Fair games. But every time I asked for the records behind those systems, snapshots, ledger entries, weekly cycles, GGR/NGR, slider logs, PF seed mapping, Tequity round IDs, withdrawal approval logs, the answer became some version of “forwarded to the relevant department.” This started long before the public dispute. I was not some random angry player who appeared after one bad session. In January I was helping Housebets and giving product feedback. I literally told support on 27 January that I was “testing the website for George,” while already dealing with a non-instant withdrawal and a 100% welcome bonus that had not applied. Support even asked me for “proof about your testing job.” The same chat shows the advertised 100% Welcome Bonus, the bonus not applying, and support saying the withdrawal needed internal confirmation instead of being instant. The welcome bonus issue never looked clean. Housebets advertised a 100% Welcome Bonus up to $1,000 on first deposit; I deposited, contacted support, and the bonus did not apply. Then support effectively turned a first-deposit bonus into a second-deposit workaround because the first one had not been applied properly. On 31 January I came back after another deposit and told them the bonus still had not been applied, even though I had already followed support’s instructions. Edward replied that he had “forwarded” the concern to the team. The same 100% welcome bonus was still being advertised in March. By April, the rewards system was already showing serious problems. I had the weekly slider at 100% lossback and told support I had lost money but the weekly did not appear. Jacky said the weekly was generated every Thursday at 00:01 UTC and gave actual internal figures: GGR $6,250, Total Bonus $6,083.99, NGR $168.31. So Housebets clearly had internal calculations when it wanted to explain why something might not pay. But when I later asked for full calculations, those same numbers suddenly became impossible to produce. Then on 18–19 April, the rewards page was bugged and would not let me claim. Support could see a pending weekly bonus of $717.37, but I could not claim it from the UI. Tee said it had been forwarded to the relevant department. That $717.37 later appears in the bonus ledger as Rakeback (20 Apr) 717.37089061, so I am not saying that specific one stayed unpaid forever. The point is worse: already in April, support could see a pending weekly reward while the player-facing reward page did not work. For a casino built around rewards, that is not a small bug. That is the product. In May, the UI and account data kept failing basic trust checks. On 8 May, I deposited 400 USDT; support said it had been credited, but I could not see it, and the proposed fix was to log out, clear cookies and cache. On 16 May, I asked why total deposits and withdrawals had disappeared from the menu; support said the platform was “in continuous evolution.” On 17 May, I asked for my total deposits and withdrawals, and support said they did not have direct access to that consolidated summary and would email it. That full official ledger did not arrive. So when Housebets later defends itself with UI screenshots, remember: this was the same UI where deposits could be credited but invisible, totals disappeared, rewards pages bugged, and support could not access consolidated account totals. Withdrawals were also not what was advertised. On 16 May, I asked why a crypto withdrawal was pending if withdrawals were supposed to be instant. Tee answered: “A few withdrawals require manual approval,” then added, “Our withdrawals are typically instant but…” That matters because a few days later the withdrawal delay became real damage. On 25 May, I told support before a match that I needed the funds to place a time-sensitive bet on another site in less than 20 minutes. I explained I wanted to bet around 60k at odds of 2.55. The withdrawal did not arrive in time. Later I told them the bet won and that I missed around 90k in profit because Housebets took more than two hours despite being warned before the match started. Jacky said he would raise the compensation case to the VIP team. Nobody resolved it. This was not one delayed withdrawal either. In my formal complaint I reconstructed several withdrawal delays: 23 May 02:55 → 08:03, around 5h08m; 25 May 03:05 → 08:09, around 5h04m; 17 May 03:54 → 08:02, around 4h08m; 18 May 04:46 → 08:11, around 3h25m; 16 May 05:23 → 08:12, around 2h49m. That is not “instant withdrawal.” And if later marketing says withdrawals are much faster now, the obvious question is: if this was the faster version, what did slow look like? The Provably Fair / Tequity side was another major issue. On 17 May I asked support how to verify an old Blackjack round. I did not ask for a generic explanation of Provably Fair; I asked where I could see the server seed, client seed, nonce and result for previous games. Support sent me to bet history, mentioned RTP, gave a generic PF explanation and showed the current Dice seed screen. When I said that did not let me verify previous games, they told me to clear cookies/cache. After doing that, I saw a new client seed and nonce 1 even though I had not played with that seed pair. I asked if Housebets changes seeds on every login. Support could not answer and told me to contact VIP. That seed/session behaviour is important. I later recorded video evidence around the seed changing after clearing cookies/cache and asked for the exact mapping: Housebets account ID → Tequity/provider player ID → session/currency context → seed pair → server seed hash → revealed server seed → client seed → nonce/cursor → raw outcome → final result. Housebets cannot sell Provably Fair if the player cannot verify historical bets, and “contact VIP” is not a verification algorithm. On 24 May, I asked for raw verification data for a specific Tequity Blackjack round: Round ID e1648d60-0da1-4433-a5ab-9ae39f5302e3, Blackjack, Tequity, bet amount 11,346 USDT, client seed O3YBZF7LBu, server seed hash starting 712875.... I asked for revealed server seed, nonce, full result JSON, card draw order and verification algorithm. I also asked about an apparent duplicate-card/deck question. Tee replied: “I don’t have the answers to your questions right now, but I’m forwarding your request to the relevant department.” That same day, I asked for a full audit of six Dice bets of 11,400 USDT each, total 68,400 USDT. I requested bet IDs, provider round IDs, roll results, seed data, balance ledger, request/session logs, security logs, retry flags, provider records and a full technical reconciliation. Tee replied: “I will forward this to the relevant department.” So when I asked for raw data, the answer was not data. It was forwarding. Again. There were also many large loss clusters that required reconciliation because of those unresolved PF, Tequity, category, RTP and session questions. In my complaint I listed clusters such as 25 May 02:17–02:54 Blackjack around 169,932 USDT; 16 May 12:31–13:26 Dice around 90,571.92 USDT; 26 May 02:48–03:58 Mines around 89,199 USDT; 24 May 06:20–06:21 Dice at 68,400 USDT; 26 May 00:11–01:41 Blackjack around 59,910 USDT; 25 May 22:51–22:59 Dice around 59,576 USDT; and several more between 40k and 56k. I am not saying every losing cluster proves manipulation by itself. I am saying that when PF mapping, provider logs, RTP/HE, category mapping and seed/session behaviour are unresolved, these sequences need a real reconciliation. The leaderboard is where the story becomes very hard for Housebets to explain. Around 19–20 May, two new accounts, elmourabut and lucasmartirini, appeared and started climbing every day at a vertiginous pace. Not normal slow leaderboard growth. Not a casual player building volume over time. They were created around that period and then started rising with huge wagering in a way that looked extremely unnatural for brand new accounts. By 29 May, I was first on both weekly and monthly leaderboards, and those two accounts were directly behind me with huge volume. In the monthly leaderboard screenshots, I was around $3.33M wagered, while elmourabut was around $1.29M and lucasmartirini around $1.08M. In the weekly leaderboard, I was around $1.096M, while those two accounts were around $635k and $578k. They were not normal accounts sitting at the bottom; they were directly behind me, applying pressure. In my formal complaint I recorded that elmourabut joined on 19 May and lucasmartirini on 20 May, that they showed zero visible withdrawals, large deposits/wagering and significant card-game volume, and I asked Housebets to confirm they were not staff, test, QA, admin, house-controlled, affiliate-controlled, internally funded, promotional, bonus-only or multi-account related accounts. This matters because a leaderboard is not passive. It is gamification. It makes players defend rank. When two new accounts appear behind you with hundreds of thousands or more than a million in volume, you are pressured to keep wagering. In my case, the disputed deposit sequence from 25 May 22:23 to 26 May 02:09 totals 91,168.375326 USDT. That sequence begins with 1,000.00 at 22:23 and continues with repeated deposits until 2,879.148969 at 02:09. The video later shows why those dates matter: there were deposits coming in, no gameplay withdrawal offsetting the sequence, a balance basically at zero, and later a leaderboard prize shown as P/L. I formally asked Housebets to confirm those two leaderboard accounts were real and eligible, and also to preserve wager logs, transaction records, balance adjustment logs, account flags, leaderboard calculation snapshots, support ticket logs, Telegram/email records and internal notes. Edward said he forwarded the request. In the same thread, he added that they were “working on fixing an issue regarding the weekly bonuses,” and then said the weekly countdown was “not currently on Thursday evenings.” So the leaderboard issue and the weekly bonus issue are linked in time and support context. After that, Housebets confirmed by email that elmourabut and lucasmartirini were “legitimate and eligible accounts.” That email is the trap door. If they were legitimate and eligible, they should have remained in the leaderboard with their volume. If they were not, Housebets should never have confirmed them as legitimate and eligible. After that confirmation, the accounts disappeared from the leaderboard or stopped appearing in the positions their previous wagering required. I went back to support on 30 May and wrote: “There has been a material post-confirmation leaderboard change involving two accounts that Housebets had already confirmed as legitimate and eligible. I need the exact reason, timestamp, logs, and recalculation basis.” Edward said the matter was flagged and that I could expect a prompt response. I am still waiting for the actual explanation. Why did they disappear? My read is simple: because every hour that passed, there was more evidence around those accounts. They had been created around the same period, they were climbing at a speed that looked anything but human, they showed no visible withdrawals in the data I could see and reported, they appeared to be generating huge volume in unclear game categories, and the games/categories tied to that volume did not even make sense from the player-facing UI. When I started asking what they were actually playing, what Card meant, whether the volume was Tequity / UnOriginals / House Games, what RTP and house edge applied, and where the logs were, the questions became uncomfortable. Keeping those accounts visible became harder than removing them. So they disappeared. The game category issue made the leaderboard even more suspicious. On 30 May, I asked support why my own stats showed almost all my volume under Slots / Tragamonedas when I did not play real slots. I told them: “i dont play 3$ in unoriginals,” “i played all 3M in unoriginals,” and “ive never play slots.” I asked what “Card” was, where that game was, what RTP and house edge it had. Monica said Card was mainly Blackjack, Baccarat and Poker variants. Marcus later said the team was investigating why it showed that I mostly played slots when I had not. He could not give the exact game, RTP, HE, provider, category mapping or contribution logic. That matters because those same unclear categories were connected to leaderboard volume. If the site cannot clearly explain whether volume is Slots, Card, UnOriginals, House Games, Blackjack, Baccarat, Always 9 Baccarat or Tequity, then the leaderboard is not auditable for the player. I even asked which UnOriginals those two accounts were playing, and support told me to look at Live Bets. That is not an answer. I was not asking for gossip; I was asking what exact games generated leaderboard volume, what RTP/HE applied and whether that volume was eligible. There is also an earlier leaderboard-related precedent: Porchy had already told me in February that I would lose leaderboard places if I did not rename, because too many people were messaging support saying the site was not being fair due to my name and it “doesn’t make us look good.” That matters because it suggests leaderboard positioning was not treated as a sacred, untouchable system when public perception was involved. If leaderboard positions can be threatened for image reasons, then later claims that everything is purely automatic deserve scrutiny. Then Porchy made the leaderboard situation worse. Instead of producing logs or snapshots, he later said the leaderboard had “abusers” on it, that they were removed to help other players, and that it never affected me. Later he said they paid every single person, “even these abusers,” then called me “begging for money.” That creates a direct contradiction: Housebets confirmed the accounts as legitimate and eligible, then Porchy referred to leaderboard “abusers.” If they were abusers, why were they confirmed as legitimate and eligible? If they were eligible, why did they disappear? If they never affected me, where are the historical snapshots proving that? Once those accounts disappeared, Housebets paid the leaderboard prizes. On 1 June, the bonus ledger shows two Leaderboard entries: 5,007.46111706 and 1,001.49222341, totaling 6,008.95334047. That part was paid. But then Act Two started: the weekly and monthly rewards did not appear as separate ledger entries. The same bonus ledger shows those two 1 June entries as Leaderboard only, not Monthly Bonus, not Weekly Reload, not Lossback. The weekly timeline is a mess. On 28 May, the dashboard / UI said the weekly bonus was claimable every Thursday at 00:01 UTC, and the monthly was available on the 1st at 00:01 UTC. That same night I told support the weekly had shown as available, then reset to 6 days without paying. Later I sent screenshots and wrote: “1M wagered and 0.2$.” Jacky said he had raised the issue to the technical team. So the weekly failure was reported live, not reconstructed after the fact. The next day, 29 May, Edward said they were fixing an issue regarding weekly bonuses and that the weekly countdown was “not currently on Thursday evenings.” Then on 1 June, Spencer said the May weekly bonuses were 7th, 14th, 21st, and then due to migration the weekly moved to Monday, so there was one on the 25th on the new platform. He also said the 25 May weekly covered gameplay from 21–24 May, and that tech was looking at that plus the monthly bonus. The ledger does show a 25 May 02:10 Rakeback entry of 1,996.08334791, which likely corresponds to that 21–24 May weekly. But my major loss sequence starts about 20 hours later, on 25 May at 22:23, and continues until 26 May at 02:09. So the 25 May weekly cannot cover those losses. If weekly was still Thursday, the 25/26 losses should have been in the 28 May weekly. But the bonus ledger on 28 May shows only two tiny Rakeback entries, 0.28373945 and 0.00280958. If weekly moved to Monday because of migration, those losses should have appeared in the next weekly after 25 May. But on 1 June the ledger only shows Leaderboard entries. Then the final video shows the next Weekly Reload reaching zero, paying nothing and resetting to 6d 23h. So the same loss sequence appears to fall into no paid weekly cycle. The 4 June support conversation makes this even more ridiculous. After I recorded the weekly reset video, I asked support a very simple question: what were the last weekly dates/cycles? The dashboard / support flow again said weekly bonuses are claimable every Thursday at 00:01 UTC. Jacky confirmed: “Weekly bonuses can be claimed every Thursday at 00:01 UTC in the Rewards tab,” and added that if not claimed by the following Wednesday at 23:59 UTC, it expires. But when I asked for the exact last four dates, Jacky said he had to check with the relevant department. When I pressed again, he said, “Sorry, As I am only a CS, Let me raise your concerns to relevant department.” I asked whether support did not have the information or simply could not answer. He replied: “Do you have any other concerns?” They use weekly cycles to decide whether to pay, but support cannot explain the weekly cycle. The monthly is missing too. The dashboard / UI said the monthly bonus is based on activity and VIP level from the previous month and is available on the 1st at 00:01 UTC. In May I had more than 3,258,023.0829 wagered according to the formal complaint data. I also have proof/video that the monthly slider was set to 50/50. On 1 June, Spencer first told me I had claimed the Monthly Bonus at 1:12am BST around the same time as the monthly leaderboard reward. I immediately said I only received leaderboard prizes. Then Spencer changed the answer: “Our tech team are still actively working on issues regarding the monthly bonuses.” So first the monthly was claimed, then tech was still fixing it. The ledger still shows no Monthly Bonus entry. Housebets then seems to rely on “up overall” as a defence. But the video and ledger show why that does not work. My weekly/monthly profile later showed around +6,008 P/L with 0 deposits, 0 wagered and around 6,008 in bonuses. That number matches exactly the two 1 June Leaderboard payments. So the UI is showing leaderboard rewards as P/L. Then support used “up overall” to say I was not eligible for weekly lossback. That is not a clean lossback calculation. That is using a leaderboard reward as apparent profit to deny a lossback that should be based on actual eligible losses. There were also smaller reward-confusion issues along the way. On 22 May I asked for all pending bonuses,weekly, monthly, rakeback, level-up, anything, and support said the internal team would manually verify whether everything had been credited correctly and email me. On 24 May, I asked about level-up rewards because the reward looked like $3,500 for Pearl; support clarified it was $3,500 total across all Pearl levels, $500 per level. These are not the core issues, but they are part of the same pattern: rewards marketing, unclear UI, manual verification, emails that do not arrive, and players having to chase basic explanations. Then there is the migration. On 25 May, after the delayed withdrawal, missing VIP contact and unresolved issues, support told me my account would be moved to the new platform and that this upgrade would offer a better withdrawal process and fix many issues. Before that migration, I explicitly requested that no account data, internal data, logs, balance history, bonus history, bet history, provider records or pending issues be deleted. The response: “Your request has been relayed to the relevant department.” Again, forwarding. But if the old data is safe, Housebets should provide the old leaderboard snapshots, old weekly states, old bonus logs, old Tequity mapping and old withdrawal approval logs. The founder response did not fix anything. When Porchy finally engaged, he did not provide the records. He framed the settlement request as “so you want $100,000?” and asked whether I needed it or else I was going to post on X. I had already made clear this was not money for silence; I asked for logs, snapshots, withdrawal records, calculations and a counter-calculation if Housebets disagreed. He later referred to “abusers,” told me I was “up overall,” said “You are begging for money,” and suggested I “just do this to casinos.” Still no ledger. Still no weekly calculation. Still no monthly entry. Still no PF/Tequity mapping. Still no leaderboard snapshots. Another player also contacted me with screenshots pointing to similar categories of issues: private deals, leaderboard payout disputes, migration/account merge problems, missing history and a tiny monthly bonus despite claimed losses. I am not using that player’s case as the foundation of my claim without his full ledger, but it matters because it suggests the same type of opacity may not be isolated: private VIP/reward deals, leaderboard eligibility, monthly bonus calculations, migration and unclear history. If Housebets has private deals that affect leaderboard eligibility or rewards, it must explain how those deals interact with public leaderboards. So the overall picture is this: Housebets sold a public leaderboard and rewards system that pressured real wagering. Two new accounts appeared directly behind me with huge volume, were confirmed as legitimate and eligible, then disappeared after I asked for logs and questioned game categories. Housebets could not explain the exact games, RTP, house edge or category mapping behind the volume. The accounts were later framed by Porchy as “abusers,” contradicting the earlier eligibility confirmation. Once Housebets paid me the leaderboard prizes, those prizes were shown as P/L, and that contaminated P/L was then used to claim I was “up overall” and not eligible for lossback. At the same time, my real 25 May 22:23 → 26 May 02:09 loss sequence of 91,168.375326 USDT appears in no clean weekly cycle. The 25 May weekly covered 21–24 May according to Spencer, so it cannot cover that loss sequence. The 28 May weekly showed only tiny Rakeback entries and was already reported as broken. The 1 June ledger shows only Leaderboard entries. The later video shows Weekly Reload reaching zero, paying nothing and resetting. And when I ask support for the exact weekly calendar, they cannot answer and send it to the relevant department. The monthly is the same story. The dashboard / UI says it is based on activity and VIP. I had more than 3.25M wagered in May. Spencer first says I claimed it, then says tech is still working on monthly bonuses. The ledger shows no Monthly Bonus. If Housebets says I was not eligible, they need to show the formula, slider history, cycle, GGR/NGR, eligible loss/activity, deductions and ledger result. If they cannot, “not eligible” is just another label. And this opens another can of worms: Tequity / provider configuration. Housebets cannot hide behind “the provider” whenever something goes wrong. The player does not deposit with Tequity. The player does not withdraw from Tequity. The player does not speak to Tequity support. The player does not compete in a Tequity leaderboard. The player plays on Housebets, with a Housebets wallet, Housebets UI, Housebets rewards, Housebets leaderboard and Housebets support. 1/2

Dr. W

19,784 Aufrufe • vor 1 Monat