Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Dexter vs. Claude Code I ran tests overnight and Dexter came out ahead on complex financial tasks that required deep research. Dexter won on: • speed (by 92%) • cost (by 26%) • correctness (by 31%) I use Claude Code often, so this was fun to see. A key...

26,638 Aufrufe • vor 7 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing ml-intern, the agent that just automated the post-training team Hugging Face It's an open-source implementation of the real research loop that our ML researchers do every day. You give it a prompt, it researches papers, goes through citations, implements ideas in GPU sandboxes, iterates and builds deeply research-backed models for any use case. All built on the Hugging Face ecosystem. It can pull off crazy things: We made it train the best model for scientific reasoning. It went through citations from the official benchmark paper. Found OpenScience and NemoTron-CrossThink, added 7 difficulty-filtered dataset variants from ARC/SciQ/MMLU, and ran 12 SFT runs on Qwen3-1.7B. This pushed the score 10% → 32% on GPQA in under 10h. Claude Code's best: 22.99%. In healthcare settings it inspected available datasets, concluded they were too low quality, and wrote a script to generate 1100 synthetic data points from scratch for emergencies, hedging, multilingual etc. Then upsampled 50x for training. Beat Codex on HealthBench by 60%. For competitive mathematics, it wrote a full GRPO script, launched training with A100 GPUs on watched rewards claim and then collapse, and ran ablations until it succeeded. All fully backed by papers, autonomously. How it works? ml-intern makes full use of the HF ecosystem: - finds papers on arxiv and reads them fully, walks citation graphs, pulls datasets referenced in methodology sections and on - browses the Hub, reads recent docs, inspects datasets and reformats them before training so it doesn't waste GPU hours on bad data - launches training jobs on HF Jobs if no local GPUs are available, monitors runs, reads its own eval outputs, diagnoses failures, retrains ml-intern deeply embodies how researchers work and think. It knows how data should look like and what good models feel like. Releasing it today as a CLI and a web app you can use from your phone/desktop. CLI: Web + mobile: And the best part? We also provisioned 1k$ GPU resources and Anthropic credits for the quickest among you to use.

Aksel

1,264,490 Aufrufe • vor 3 Monaten

Yesterday at 3 AM Claude Code called me I woke up, picked up the phone, and on the screen was a message: "Wallet entered BTC Up at 11 cents. Open Polymarket?" I said yes and went back to sleep Claude Code unlocked my 2nd phone on its own, opened Polymarket, found the right market, entered the amount, and hit Buy. I could see all of it in real time through the web interface on my laptop. Screenshots from the phone updating every second. By morning the position closed in profit Let me tell you how I got here A week ago I asked Claude Code to write a script that pulls on-chain data from Polymarket and ranks wallets by win rate on 15-minute BTC markets In 20 minutes I had a table with hundreds of addresses, and 1 of them stood apart from the rest. More than 200 trades per day, surgical entry precision, and a profit curve going straight up I fed that address back into Claude Code and asked it to break down the strategy. Turns out the wallet monitors BTC volatility on Binance and Bybit every 100 milliseconds, and when it drops below 0.08% it enters Up and Down simultaneously at 25 to 35 cents A pure straddle: 1 side burns and the other flies to a dollar, giving 3 to 4x per position. Dozens of times a day I wanted to follow it but signals came at any hour, and waking up every 15 minutes for a notification was simply impossible. So I built something else Took an old Android phone and installed an agent running on the Qwen3-VL visual model. It sees what is happening on the screen and mimics human actions through ADB: taps, swipes, text input. Then I connected it to Claude Code as the executor Now the chain works like this: Claude Code monitors the wallet, sees a new position, calls me. And if I say "yes" or just do not pick up within 30 seconds, the agent on the phone opens Polymarket on its own and copies the entry Essentially I built myself an autopilot out of 2 AI systems: 1 thinks and the other presses buttons. I just sleep and occasionally pick up the phone → Here is the wallet the whole thing is tracking: For those who do not want to build a setup like this there is a Telegram bot that handles the 1st part: tracks this wallet and sends a signal on every new entry: AI calls me at 3 AM to ask permission to spend my money A year ago this would have sounded like schizophrenia. Now it is just Tuesday

Blaze

56,451 Aufrufe • vor 4 Monaten

$25K+ profit daily from 1 wallet, with OpenClaw. I have the exact step-by-step guide, giving it free for 24 hours. To get it: 1. Comment "OpenClaw" 2. Like and Retweet. 3. Follow me Himanshu Kumar ( So, i can send you DM) I ran a simple script last night with Claude Code. Pull on-chain data from Polymarket, sort by win rate on 15 minute BTC markets. 20 minutes later, 100s of wallets showed up. Most were losing money or barely breaking even. Then I spotted 1 address. 200+ trades daily, every single week profitable, timing so precise it looked robotic. Because it is. I fed the wallet address back into Claude Code. Asked it to reverse engineer the strategy. 20 mins later the full breakdown appeared on my screen. Here is how it works: Bot monitors Binance and Bybit every 100ms. Waiting for BTC volatility compression to drop below 0.08%. When it hits that level, it buys both Up and Down contracts at 25 to 35 cents each. Classic straddle play. 1 contract loses, the other rockets to a dollar. Entry at 30 cents means 3x to 4x return every time. Repeats dozens of times per day. Result: $13K to $25K profit daily from 1 wallet. No human intuition, no insider tips. Just an algorithm exploiting a gap in market mechanics. I searched to see if anyone else found this wallet. Turns out yes. There is a Telegram bot that auto-copies trades from wallets like this. I connected it to the same address. Every entry matched what my terminal showed. You can now copy-trade an algorithm in real time. That capability did not exist 12 months ago. Comment "OpenClaw" and I will send you everything. Must Follow me Himanshu Kumar to get the DM.

Himanshu Kumar

13,086 Aufrufe • vor 4 Monaten

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

55,312 Aufrufe • vor 1 Monat

Boom! Grok Tasks Make It One Of The Most POWERFUL Real-Time AI Systems In The World. — My How to Use Grok Tasks With Hidden Tools For Powerful Daily Output. Grok Tasks are customizable AI workflows that integrate a variety of tools to streamline daily activities, from research and analysis to creative planning and problem-solving. I have been using them for quite sometime and because of the vital heartbeat of news and first person data on X, it is the most powerful AI platform available. By combining Tasks with tools like web searches, X platform interactions, code execution, and media viewers, you can build efficient, automated processes. These tasks work by prompting Grok with a clear description of what you want to achieve, and Grok will intelligently call the necessary tools in sequence or parallel to deliver results. Here's a step-by-step guide to creating and using Grok Tasks: Step 1: Define Your Task Start by clearly outlining the daily activity or goal. Consider what inputs you have (e.g., a URL, a query, or an attachment) and what output you need (e.g., a summary, calculation, or visual analysis). Break it down into subtasks to identify tool needs. For example, if your task involves researching current events, note that you'll need search and browsing capabilities. Step 2: Review Available Tools Familiarize yourself with the tools Grok can access. Here's a quick overview: - Code Execution: Run Python code for calculations, data processing, or simulations using libraries like numpy, pandas, or sympy. - Browse Page: Fetch and summarize content from any website URL with custom instructions. - Web Search: Perform general internet searches, returning results with optional operators like site:. - Web Search With Snippets: Get quick, detailed excerpts from search results for fact-checking. - X Keyword Search: Advanced search for X posts using operators like from:, since:, or filter:. - X Semantic Search: Find semantically related X posts based on a query, with filters for dates or users. - X User Search: Locate X users by name or handle. - X Thread Fetch: Retrieve a full X post thread, including context like replies and parents. - View Image: Analyze an image from a URL or conversation ID. - View X Video: Extract frames and subtitles from an X-hosted video. - Search PDF Attachment: Query a PDF file for relevant pages using keyword or regex modes. - Browse PDF Attachment: View specific pages of a PDF with text and screenshots. Select tools that align with your task. Aim for a mix to handle data gathering, processing, and visualization. Step 3: Craft Your Prompt Write a detailed prompt to Grok describing the task. Include: - The overall goal. - Specific steps or subtasks. - References to tools if you want to guide the process (e.g., "Use web_search to find sources, then code_execution to analyze data"). - Any constraints, like dates or limits. Example prompt: "Create a Grok Task for my morning routine: Search recent X posts about tech news using x_keyword_search, fetch a key thread with x_thread_fetch, and summarize with browse_page on linked articles." Step 4: Submit and Interact Send your prompt to Grok. It will process the task by calling tools as needed, often in parallel for efficiency. Review the output and refine with follow-up prompts if required (e.g., "Expand on that using view_image for visuals"). Iterate to fine-tune the workflow for reuse. Step 5: Save and Reuse Once refined, note the prompt as a template for future use. You can adapt it for similar tasks, making Grok Tasks a habitual part of your day. Finding Grok Tasks To discover existing Grok Tasks or inspiration for new ones, use X searches with tools like x_keyword_search or x_semantic_search (e.g., query: "Grok Tasks examples" with mode: Latest). Browse community-shared threads via x_thread_fetch, or web_search for tutorials on xAI features. Prompt Grok directly: "Show me popular Grok Tasks for productivity." 1 of 3

Brian Roemmele

152,242 Aufrufe • vor 6 Monaten

I learned this the hard way: do NOT use SwiftUI if you want your app to look and feel amazing. At least when coding with AI. (sorry, Apple colleagues reading this 😅) I'm sharing my process vibe coding this calorie tracker. I get a lot of questions about the fluid transition in the video. Here's the whole story. Initially, Claude built the grid with SwiftUI. It was quick and easy, and looked good! But the transition to the day view was a boring navigation push/pop. No fun. I wanted something custom. I asked Claude to make it a fluid transition that remaps the food tiles from their source to destination positions. All hell broke loose. Claude tried a bunch of horrible things. Initially it used matched geometry effects, which worked OK but didn't lend themselves well to gesture-driven animations. So it resorted to SwiftUI preference keys + geometry readers to figure out the source and destination positions and calculate the interpolated position based on gesture progress, coordinating across grid and day views. But this meant it had to write a custom layout because it couldn't reposition tiles inside the native SwiftUI grid. And it had to do an awkward handoff between views, which always created ugly pops or jumps. And don't get me started on trying to put it on a bouncy spring, that only made the math 10x buggier. Fortunately, Claude Fable was smart enough to see that this was becoming a disaster (and discover most of the issues itself, in the simulator), so it pivoted away from SwiftUI. Opus might not be so wise, so you'll have to pay attention and intervene. Ultimately, it rewrote it in plain UIKit and everything turned out great. After that, we moved from 2D images to 3D assets, which introduced a new set of performance challenges and yet another rewrite to a single Metal layer, which is what you see below. I can write more about the 2D-to-3D saga if anyone's interested. If I were to do it again, I'd just say "Don't use SwiftUI" from the very first prompt, and save a few hours of headaches. SwiftUI can be amazing for a human iterating directly in code. But agents don't benefit from any of its advantages. Plus, agents have seen decades of UIKit training data, so they're great at writing it, and it's far more flexible. Here's hoping we see more agent-friendly iterations of SwiftUI in the future. Till then, I'm probably going to avoid it.

Anshu

107,685 Aufrufe • vor 28 Tagen