November 20, 2026super-user

Super User Daily: 2026-11-20

Wednesday, November 18 was the day Claude Code got Code Mode and the team published how it verifies its own code, but the best posts were about who is now holding the keyboard. At Ramp, 7,000 pull requests in one quarter came from people who are not engineers, mostly the support team. A construction tradesman hands estimates and schedules to it, a solo developer shipped an iPhone sniper game, and a founder cancelled Salesforce and saved $60,000 with a CRM whose main users turned out to be agents. The second thread is replacement math: Clay rebuilt over a weekend because the per-request price went up 680%, and a cache breakdown showing 366 million Opus tokens costing $190 at list price because 97% were cache reads. The third is hierarchy. Claude Code is increasingly the worker, not the boss: Grok Bot or Fable plans, Claude Code and Codex execute, and the people doing this well put the checks outside the model, from a no-send-without-approval email agent to settings that turn a stuck permission prompt into an instant denial.
@eglyman [Claude Code]
Claude Code#1
https://x.com/eglyman/status/2123077917164941674
Ramp's co-founder says AI was quietly breaking the company early this year: a few people got 100x more productive, whole functions fell behind, and the teams using the least AI asked for the most headcount, bad enough that hiring stopped for a quarter while revenue grew 100%+. The diagnosis was not the models but access, because a salesperson told to use Claude Code first asked what a terminal was, then whether it could see the data, Slack and customers, and the answer was no to all three. So they connected it to everything, and in Q2 about 7,000 pull requests at Ramp came from non-engineers, mostly the CX team, up from zero two years ago. A customer emails about a bug, the fix ships, and the reply goes out the same afternoon. The lesson is blunt: the bottleneck is permission to act, not intelligence.
@dorszafranski [Claude Code]
Claude Code#2
https://x.com/dorszafranski/status/2122962260586844527
A Polish YouTuber made an 11-minute video on the Jevons paradox and AI without editing a single frame by hand. The input was a 6,000-word script and 9 minutes of their own voice, and Claude Code cut the script into 36 parts, cloned the voice through ElevenLabs, used Whisper to check every line was spoken correctly, built 3D sparks, a night city and charts in Remotion and Three.js, pulled archive footage from Wikimedia, picked music and mastered to -14 LUFS. The bill was about 7,000 of 40,000 ElevenLabs credits and 186k output tokens from Claude. It hit real snags, Pixabay blocking downloads, Chrome crashing mid-render, overlapping text in a dozen scenes, and fixed them itself, leaving a reusable pipeline. The honest weak spot is the voice, which came out a bit robotic and pronounced DeepSeek as DipSik.
@lesith [Claude Code]
Claude Code#3
https://x.com/lesith/status/2122937013108375879
Instead of waiting for Claude Duet or trusting someone else's cloud agent, a developer built Dragonfly, a personal email assistant that lives on their own Mac mini, with Claude Code, Python and Swift. It watches chosen Gmail and Apple Mail folders on a schedule, keeps memory of people and threads in an Obsidian vault the owner can read and edit, drafts replies and pings Telegram when something needs attention. The interesting part is what it cannot do: sending is plain code that only fires when the owner replies send to that exact draft, email content is treated as information and never as instructions, and a gate checks every tool call so that after reading outside text it cannot change its own rules. Every run is saved and any change can be undone with one click. This is the clearest example today of safety built as architecture rather than as a prompt.
@Kuzzat_AltayEN [Claude Code]
Claude Code#4
https://x.com/Kuzzat_AltayEN/status/2123053657616781652
A founder says cancelling the company's Salesforce subscription saved $60,000 this year, after switching to Claude Code 11 months ago and building their own CRM. The surprise came later: the CRM was built for humans, but over time the main users turned out to be agents, and the same happened with the other internal software they built, so the whole workflow became agent-centric. Their argument is that legacy software is like a skyscraper with structural problems, and patching holes is worse than rebuilding to new standards. Whether or not you buy the rebuild-everything thesis, the data point is real: a CRM whose primary reader is an agent needs different design choices than one built for sales reps clicking around.
@codyschneider [Claude Code]
Claude Code#5
https://x.com/codyschneider/status/2122857975924903951
A GTM operator had Claude Code rebuild Clay, the enrichment tool, after Clay raised the price per action from $0.0000182 to about 1.24 cents, capped tables at 50,000 rows and started charging per HTTP request. The math is the hook: one team was running 17.3 million HTTP requests a week through Clay for $314 a month, and at the new price a new customer would pay $856,350 a month for the same volume. The rebuild covers tables, email waterfalls across Apollo, Prospeo and LeadMagic, MillionVerifier checks, AI columns, HTTP columns, CSV in and out and auto-run on new rows, all on a Postgres database with a tool router and a UI for the human. The line worth keeping: most GTM tools are just APIs with a UI on top, and Claude Code is the UI now.
@LabSpeculation [Claude Code]
Claude Code#6
https://x.com/LabSpeculation/status/2122855951992783080
A Chinese user installed claude-trading-skills, a 6,000-star Claude Code toolkit for market checks, position sizing and trade journals, and ran its recommended 15-minute daily routine on one market on one day. The breadth check said stocks could be 60 to 70% of the portfolio, the advance check said 30 to 60%, and when both reports went into the position calculator it said 15% and hold cash. Reading the code explained it: the sizer wants three key reports and deducts 10 points for each missing one, one of which needs paid data, and adding the free missing report moved the answer to 32%. The bigger finding is that the scoring is all fixed formulas, so the AI is not judging the market, it is running steps and narrating them. Useful as a daily checklist with transparent reasoning, not as a number to trade on.
@LabSpeculation [Claude Code]
#7
https://x.com/LabSpeculation/status/2123047900733477231
The same user then ran NVIDIA's open-source skill scanner SkillSpector, in its free rules-only mode, over 7 of the most popular skill packs: 20 of 134 skills were flagged do-not-install, including 5 of Anthropic's own 19 official skills and the trading pack tested the day before. Opening the five scariest flags, all five were normal behavior: the trading pack was flagged for key theft when it was sending your own broker key to the broker's official URL, and Anthropic's slide skill was flagged for deleting the previous deck before repacking. The practical rule that comes out of it is good: scan unknown skills before installing, read only the flagged lines, and check whether keys go to official or unknown hosts and whether anything reads wallet files or SSH keys. A scanner that cries wolf still tells you where to look.
@ivanjurashere [Claude Code]
Claude Code#8
https://x.com/ivanjurashere/status/2123171779522990488
A builder running an overnight software factory for SEO tooling found the runs froze on a Do you want to proceed dialog, and the obvious fix, a watcher agent that clicks yes, is blocked outright by Claude's own safety classifier as undermining oversight. The detail that matters: at the top level Claude Code counts down two minutes and denies on its own, but inside a subagent that countdown disappears and the job sits dead until morning while the harness waited 60 minutes to alert. The fix was to kill the prompts at the source by stripping AskUserQuestion from worker launch flags and setting denyInsteadOfPrompting, so a risky command becomes an instant denial the agent can route around, verified for $0 against a fake local API server. The human-side version of the same stall was four plans parked for days because agents buried a needed Cloudflare token or budget approval in an end-of-run summary, so now every key, login and dollar cap is collected before work starts.
@younesbag1 [Claude Code]
Claude Code#9
https://x.com/younesbag1/status/2123105459272118388
An Arabic-language site about Claude skills went from 8 impressions and 2 clicks in 28 days to 1,795 impressions and 108 clicks, and the playbook is unusually disciplined. Numbers only come from Search Console and Bing, one page ranking between 5 and 20 gets the bet, the searcher's question gets answered at the top of the page, and only one change per page is tested before waiting for Google to recrawl. Buying search volume for 459 Saudi keywords for under 10 cents showed claude skills gets 880 searches a month while the Arabic phrase gets 20, which changed what they built. Now a Claude Code agent runs every Monday, audits the site and experiments, measures AI-search visibility, picks the next change and executes it within clear limits. The last week alone brought 37 clicks, against 13 in the whole first month.
@cmglezpdev [Claude Code]
Claude Code#10
https://x.com/cmglezpdev/status/2123091499848024367
A developer pulled one week of Opus 5.5 usage through Claude Code, November 8 to 14: 366 million tokens on a $20 subscription, which T3 Code priced at $190.71 at API list prices. The breakdown is the useful part: 354M cache reads cost $70.77, 9.74M cache writes cost $74.16, 2.29M output tokens cost $45.75, and uncached input was 5,710 tokens for two cents. Cache reads were 96.7% of all tokens yet cost less than the writes, and without caching the same requests would have run about $1,500. The takeaway for anyone worried about limits: the expensive thing in an agent session is not reading the conversation again, it is writing new cache, so whatever breaks your prefix is what burns your budget.
@marcthecreatorr [Claude Code]
Claude Code#11
https://x.com/marcthecreatorr/status/2123004538974294470
A creator ran the same tandem-bike SVG task on two stacks: Opus 5.5 in Claude Code burned 11M+ tokens over about an hour, roughly $18 at API prices, while GPT-6.2 Sol in Codex CLI used 6.7M+ tokens in 46 minutes for about $1.90. After hours on Sol at max reasoning they were still under half their usage limit, and judged Sol a clear step up from 6.1 at SVG and 3D. Opus did a good job, the verdict goes, but Sol was nearly 10 times cheaper. It is one task, but it is the comparison more people are now running: same job, two harnesses, and the bill decides.
@DaveShapi [Claude Code]
Claude Code#12
https://x.com/DaveShapi/status/2123090286284865620
A YouTuber who animates their videos with Claude Code is running a head-to-head: ChatGPT 6.2 Sol on Ultrafast versus Claude Code with Opus 5.5 on Ultracode, building the same open-source animation app from the same spec in parallel. The app is deliberately simple, audio in, plan the film from the transcript, design assets, compose animation with sound effects and music, render an MP4. The complaint behind the test is specific: Claude invents rules, changes procedures and slowly sabotages long projects, and Ultracode was the only thing that could one-shot the job. The bet is that guardrails, standards and checks make a cheaper, faster model more consistent, and the same author separately said they had stopped Claude Code mid-task, deleted the thread and the repo after Sol iterated faster.
@chrismaconi [Claude Code]
Claude Code#13
https://x.com/chrismaconi/status/2123089285125439664
A heavy Grok Bot user gives the cleanest version of a pattern that showed up all day: do not let Grok Bot write code itself, because it burns tokens and leaves you angry at usage limits. Instead pair the Grok Bot Ultra subscription with a top-tier Codex or Claude Code subscription, have Grok Bot install those CLIs on its virtual computer and orchestrate them, and run the actual coding in the labs' cloud environments rather than on the VM, which can overload. That spreads token burn across two subscriptions and lets each agent specialize. Grok Bot is the orchestration layer and Claude Code and Codex are the implementation workers, a division of labor that a Japanese user pushed back on the same day, estimating that running multi-bot rooms for real would cost around 500,000 yen a month.
@DmitriLLM [Claude Code]
Claude Code#14
https://x.com/DmitriLLM/status/2123092480375849376
A Russian developer now works only one way: Fable inside Claude Code launches and coordinates Codex instances instead of its own subagents. Their reasoning is a sharp read on the two model families: Anthropic models understand what is wanted, do not fantasize or inflate scope with side activity, and write precise acceptance criteria for each subtask, while Codex on its own is a token burner. Put Claude in charge of the spec and the definition of done, and OpenAI's models become much more useful as workers. It is the mirror image of the Grok Bot pattern: the coordinator is chosen for judgment, the workers for price.
@yokuboukun8888 [Claude Code]
Claude Code#15
https://x.com/yokuboukun8888/status/2122866705005457468
A Japanese user learned the hierarchy lesson the hard way: thinking Fable 5.2 was the strongest model, they gave it every task in Claude Code, watched tokens vanish at a frightening rate and got errors on top. The fix was role separation: Fable 5.2 as the main agent for the overall plan, instructions and checking deliverables, and Opus 5.5 as the sub-agent doing the actual work. Since Fable costs twice as much per token as Opus, moving execution to the cheaper model changed the burn rate a lot, and the same work started running far more stably. The strongest model is a manager, not a laborer.
@teihen_ai [Claude Code]
Claude Code#16
https://x.com/teihen_ai/status/2123067552557584712
Replying to a post about tax accountants, a Japanese construction tradesman says the same shift has already hit the job site: drafts of estimates, work schedules and invoice prep all go to Claude Code. The only part that still needs a craftsman's instinct is the final call on the price, and the paperwork leading up to it is something they could never go back to doing by hand. The observation at the end is the sharp one: the trades that have not touched it yet seem to be falling behind fastest. This is the non-coding user the product was never designed for, and it fits anyway.
@soranoiro333 [Claude Code]
Claude Code#17
https://x.com/soranoiro333/status/2123055241537163625
A Japanese astrologer has been building a cat-themed horoscope web app, endless fixes plus the sales setup, and finally upgraded to the Claude Code Max plan last week. It paid off: the app is on track to release as planned on November 26 as a one-time purchase at 4,980 yen. Last week's astrology sessions were already run entirely inside the app, which freed the author from a Windows-only desktop program they had been tied to. A domain expert turning their own practice tool into a product they can sell is exactly the long tail Claude Code keeps reaching.
@QuickscopeFPS [Claude Code]
Claude Code#18
https://x.com/QuickscopeFPS/status/2123132746851607010
A solo indie developer shipped Quickscope FPS, a free iPhone sniper game for people who grew up on 2009 trickshot lobbies, and says every map and the whole game were built vibe coding with Claude Code. The feature list is not trivial: 360s, corkscrews and backflip trickshots, quickscopes, no-scopes, ricochets and collaterals, killcams, ranks, rifle skins and cross-play party codes. The posts are marketing, but the product is live on the App Store and the maps, like a neon alley called Monsoon and a casino floor, are shown in gameplay. One person, a niche nostalgic genre, and a shipped multiplayer game is the kind of output that used to need a small studio.
@adriansanpei [Claude Code]
Claude Code#19
https://x.com/adriansanpei/status/2123160020451795209
A Spanish creator with no programming background vibe coded a first mini game over one weekend and laid out the stack. A skill called one-line-3d-game produced a playable version from a single prompt, the whole game lives in one HTML file on three.js, and the author asked Claude chat for tweaks, which then handed exact instructions to Claude Code in VS Code. 3D characters came from Tripo3D and TRELLIS on Hugging Face, a bot plays the game on its own to prove it is winnable, the leaderboard sits in Google Sheets, and it is published on GitHub Pages with a custom domain and GoatCounter for retention. Server cost $0, lines written by hand 0, though the post ends in a comment-for-the-skill funnel.
@BeyondTheBoxCN [Claude Code]
Claude Code#20
https://x.com/BeyondTheBoxCN/status/2122842221300855198
A Chinese account relays a Japanese developer's lesson from building an MMORPG: a boar monster came out with a crooked head when seen from the front, because the original reference was a three-quarter body with a front-facing face and the AI faithfully turned that mistake into 3D. The fix was upstream: use Claude Code and Tripo Studio to make aligned front, side and back reference images with eyes, ears, legs and tail in matching positions, then generate with Tripo Multiview. Rigging and animation happened in Blender, the model went from about 50,000 faces to 2,500, 11 animations were remade, and it went into the Godot game for just 52 Tripo credits. The whole process was then written into a SKILL.md so the next monster reuses it, which is the real point.
@thedorbrothers [Claude Code]
Claude Code#21
https://x.com/thedorbrothers/status/2123170931321307605
The Dor Brothers, a studio known for viral AI video, said in a reply that one of their videos was 85% automated with Claude Code. They did not manually generate any images or videos and did no post-processing on existing clips, all of that was automated, and the humans only semi-edited the result and gave ideas and direction on what to generate. That is a meaningful split from people who make this kind of content for a living: the agent runs the production pipeline, the people keep taste and direction. It is short on technical detail, but the 85% figure from practitioners is worth more than most launch claims.
@jakepulier [Claude Code]
Claude Code#22
https://x.com/jakepulier/status/2122881854017601750
A founder says their whole business runs out of two Obsidian vaults wired into Claude Code. Every session reads the vault before starting and writes back what changed when it ends, a sweep at 11:30 every night logs anything that slipped through, and daily cron jobs handle client AEO, crawler checks and outreach. The most interesting mechanism is the self-correcting loop: timed loops score their own number, and if a rule change makes the number drop, the change rolls itself back. Short post, but it is a complete operating model: memory in plain files, a nightly audit, and automatic reverts tied to a metric.
@atgarone [Claude Code]
OpenClaw#23
https://x.com/atgarone/status/2122931954471600579
A user describes the multi-agent setup they ended up with after a long experiment: an OpenClaw agent with its own dedicated Mac, its own iCloud account and Google suite account inside the user's LLC, a Hermes agent on a desktop they use personally, a Grok Bot, and Claude Code with Remote Control on both laptop and desktop. The OpenClaw agent knows them best and pushes back least, and a local Qwen 3.8 has been a godsend when tokens run out or frontier models go down. Getting them to cooperate has mostly happened through back channels, with Herdr and Paperclip videos showing how to tighten it up. Their conclusion is the dedicated-machine approach works best, which is also why they are waiting for a Mac Mini sell-off.
@ushiro_noko [Claude Code]
Claude Code#24
https://x.com/ushiro_noko/status/2122871973114249371
A Japanese developer runs Claude Code sessions on both a Mac mini and a MacBook Pro and has the agents send tasks to each other via SendMessage, so each job runs on whichever machine suits it best. When a human needs to step in, Tailscale connects both Macs and an iPhone through the rex app. The reason is practical: without spreading work across machines, build load gets heavy and performance benchmarks are not reliable. Their buying advice follows from it: two Macs at 250,000 yen each beat one at 500,000.
@yoshio_nocode [Claude Code]
Claude Code#25
https://x.com/yoshio_nocode/status/2123014345588404348
A Japanese builder made their own version of Claude's Artifacts on Cloudflare because the built-in one does not fit a multi-agent setup. Deliverables like documents and slides are stored in Cloudflare D1, each is linked to a self-built task board that also handles versioning, and edit instructions go straight from the board to whichever agent is working. Both Claude Code and Codex can update the same artifact, which is the whole point. When the work is shared between agents, the output has to live somewhere neither of them owns.
@yoavain [Claude Code]
Claude Code#26
https://x.com/yoavain/status/2123158285826023870
An Israeli user spent two months at home with too much free time and too few tokens, just them against a $20 Claude Code subscription, and built a lot: a complete home network with security, backups, monitoring, a document archive and more. They now plan to write a blog post per project covering what they wanted, how they set it up and where it blew up. It is a modest post, but it shows the cheapest plan doing serious infrastructure work for one household. Home IT is quietly one of the best non-work uses: high stakes for one person, nobody else to call.
@mrzhiji [Claude Code]
Claude Code#27
https://x.com/mrzhiji/status/2122971314881527837
A Chinese tech outlet tested Baidu's new Wenxin 5.5 Flash Preview by plugging it into Claude Code through the Qianfan API and running a dozen-plus tasks, and the harness turned out to matter as much as the model. One-shot outputs were strong: a Braun-style 16-step synth sequencer with working spectrum display in under 10 minutes, a 20-second history of computing built only from Canvas, WebGL and Web Audio, and a Fourier-epicycle animation in about 21 minutes. Complex 3D failed in a single pass, with an iPhone teardown scene misplacing hundreds of parts, but once the agent environment wrote its own automated tests and checked items one by one, dozens of script checks fixed the defects. With a cheap API and fast decoding, running more test loops inside the agent tool pays off, which is a good argument for using Claude Code as a test bench for other models.
@fexx_off [Claude Code]
Claude Code#28
https://x.com/fexx_off/status/2123158919816380575
For a hackathon, a developer built Returner, which rehearses every release as two users in real Chrome: one brand new, one coming back with work saved on the previous build, side by side on the same build and address. The insight is that most browser tests start from an empty profile and only ever test new users, while renamed storage keys and data model changes hurt returning ones. When the returning user breaks, the finding goes to Codex or Claude Code, the agent patches a throwaway copy, and Returner replays from the exact same saved browser state, so the agent never grades its own fix. It was tested on a real regression in the PKI Consortium's self-assessment tool where returning users got a blank page, and the replay confirmed every saved answer survived.
@MrDHat [Claude Code]
Claude Code#29
https://x.com/MrDHat/status/2123158297297703193
A team says they have been running their own version of code mode on top of Claude Code for months, before Anthropic shipped it: a local proxy that logs in automatically and gives Claude a scriptable interface to chain queries together, which has worked like a charm. They are glad it is becoming a default, while noting the official version is still early in features and ecosystem support. And they used the moment to tell internal skeptics they had called it. When users have already built a feature in production, the official version tends to land well.
@barubaru_ss_ai [Claude Code]
#30
https://x.com/barubaru_ss_ai/status/2122863909845815491
A Japanese user tried Code Mode on the day it shipped and gave it a perfect first test: read and sort 122 self-written skills. Before, Claude called a tool once per item and read each full result, and with Code Mode it wrote its own code to run them together and took back only what it needed, so 122 reads collapsed into one. Their read is that the more items a job has, the more it helps. That matches what the docs say Code Mode is for, repeated work across many files.
@xavinash [Claude Code]
Claude Code#31
https://x.com/xavinash/status/2123024001844879731
A growth writer breaks down how Fastlane hit $69K MRR just over two months after launch, and one step is a Claude Code story. They put a button in the app offering 7 extra days of access in exchange for a call, which got them 2,000 customer calls, run with a strict weekly quota and Mom Test questions. Every call went through an AI note taker into Notion, all of it plugged into Claude as a customer dashboard with a customer love score, and the non-technical co-founder built that dashboard with Claude Code. It surfaced that people who signed up out of curiosity retained worse than those who picked I need marketing now, which is the kind of segmentation insight a startup usually pays an analyst for.
@kenyondigital [Claude Code]
Claude Code#32
https://x.com/kenyondigital/status/2123099070898078012
An SEO practitioner argues that writing articles and shopping them around by cold email for backlinks is dead, and the replacement is curating and presenting data people actually want to link to. Their proof is a niche site tracking publicly available information in the outdoor space that is already getting early traction. Claude Code built it in a single day, from their phone. The point is about the bar moving: high-effort content got far cheaper to make, even for non-technical people, so the standard for what earns a link went up with it.
@gengdaJ [Claude Code]
Claude Code#33
https://x.com/gengdaJ/status/2122994499622203846
A Chinese user asked Gemini 4 Carbon in Antigravity a plain prompt: review all my Codex and Claude Code chat history from the last few months and give me suggestions, and it spent 17 minutes on it. The output covered token allocation, finding that the spending that actually made money was small while most tokens went to emotional back-and-forth, plus weaknesses in their memory system, wasteful skills, adding features before launching, and missing cleanup. It also gave ready-to-use edits for Agent.md, told them to fork more instead of polluting the main session, proposed a split between Claude Code and Codex, and talked them out of a planned new business line. Your own agent logs are becoming a dataset about how you work, and a second model is a good auditor for it.
@theisaacmed [Claude Code]
Claude Code#34
https://x.com/theisaacmed/status/2123165531457130577
An e-commerce operator laid out the stack they would use to start a consumer brand from scratch today, and Claude Code sits in two places. On the website side, Claude Code handles all changes and development, which they say saves thousands. On the ops side, Claude runs an 11-week cash flow model, with the Mercury MCP set up so Claude keeps it updated every morning, and handles inventory management in the short term. Everything else is specialist tools: Euka, Trybe and Sideshift for creators, Skio for subscriptions, Richpanel once there is scale, Justworks for HR and Fulfil when the supply chain gets complex. It is a good map of where an agent replaces a hire and where buying the tool is still cheaper.
@yusukelp [Claude Code]
Claude Code#35
https://x.com/yusukelp/status/2123047348985319875
The maker of LandingBoost built it for indie hackers but suspects small agencies need it more, since they look after many client sites and re-check every page after each publish. Instead of guessing, this week they built an email outreach agent with Claude Code to test the idea fast. It finds agencies through treg, sends from a Zoho Mail inbox and routes replies into tern, and they mapped the whole job into 9 tasks with the cost of each step. Using an agent to validate a market before building for it is a cheap habit more founders should copy.
@aacle_ [Claude Code]
Claude Code#36
https://x.com/aacle_/status/2122870208398578024
A post relays a story spreading from r/claudecode: a developer had Claude Code working on their codebase for weeks, then asked it to stop coding and use the product like a buyer, clicking through the app and trying to actually buy the thing. It found bugs it had never noticed in all those weeks on the same code. Same agent, same repo, different role, different bugs: in coder mode it reads files looking for what is wrong with the implementation, in buyer mode it walks the flows a real user walks, which nobody scripted edge cases for. Agents inherit the builder's blind spots, and switching roles is the cheapest way to borrow fresh eyes.
@poteto_obake [Claude Code]
Claude Code#37
https://x.com/poteto_obake/status/2122871750233104418
A Japanese SEO writer stopped doing rewrites by hand and now lets Claude Code pick which article to fix, rewrite it and check rankings every morning. Search Console comes in two ways: an MCP connection with an API key for speed and volume, or letting Claude open the logged-in Search Console in a new Chrome tab and read the numbers off the screen, with no setup, good for trying it out. The selection rule is concrete, articles with high impressions but low click-through and pages stuck at positions 11 to 20, and rewrites target title, description, headings and body against real top queries, saved as WordPress drafts through the API. The human only reviews before publishing and adds first-hand information.
@gubatron [Claude Code]
Claude Code#38
https://x.com/gubatron/status/2122857542128947379
A developer controls their laptop from Claude on Android through a remote Claude Code session plus browser plugins, and says it is awesome. From the phone they can have the computer install or update any tool that installs via the terminal, and tell it to act on their behalf on any website they are logged into in Chrome. Their complaint is that it is all patchwork. Desktop operating systems should be natively controllable by a local model with access to everything, reachable from your phone however you want, smart enough to fact-check and research before acting.
@ariozick [Claude Code]
Claude Code#39
https://x.com/ariozick/status/2123043543308521650
A builder had Claude Code rebuild an old site that had been down for a while. When they first built it, it probably cost $15,000. This time it took an Opus 5.5 agent and about 2 hours. It is a one-line data point, but the ratio is the story: the cost of reviving a dead web property has dropped by two orders of magnitude.
@Pias443 [Claude Code]
Claude Code#40
https://x.com/Pias443/status/2122940491847340109
A post relays a creator's photorealistic Japanese train station scene built with Claude and Blender over 6 days of reviewing, refining and requesting specific fixes. The method is the interesting part: Claude Code with Blender MCP, reference images, a CLAUDE.md rulebook, specialized sub-agents for modeling and visual quality checks, and strict rules against external 3D models and texture photos. Only the foreground trees were an external asset, most materials are procedural shader nodes, Tripo handled a few pieces, and the 36-second video includes a making-of edited by Claude. Constraints in the rulebook did more for realism than any single prompt.
@leonfu2012 [Claude Code]
Claude Code#41
https://x.com/leonfu2012/status/2122855219050471627
A Chinese creator open-sourced the multi-platform publishing setup they use daily, which turns an hour of posting one video to 7 platforms into a few clicks. It has three parts: a publishing skill for Claude Code that watches the video and writes titles, descriptions and tags per platform, a Chrome extension that opens each upload page and fills in video, cover, copy and schedule, and the main app that schedules, tracks data and pushes reviews to a Feishu group. On the four Chinese platforms it only fills the form and stops at ready to publish for a human click, and it scrapes Xiaohongshu data slowly rather than hammering it. The review loop is what makes it valuable: day 1, 3 and 7 comparisons showed the last episode at 22,000 views in a day, 6 times the previous one, and that Xiaohongshu signups convert to members at 8.8% against 1% for the larger X crowd.
@MushtaqBilalPhD [Claude Code]
Claude Code#42
https://x.com/MushtaqBilalPhD/status/2122982890048717259
A researcher who makes content shared a simple video editing workflow that leans on Claude Code for the parts that take taste rather than patience. Record, then do a fast rough cut in CapCut that only removes bad takes, because asking Claude to do that just slows things down. Give Claude Code one or two clips whose editing style you like and have it understand the style, then hand it the rough cut, ask for a storyboard before rendering, review and adjust, and render. Locally it takes an hour or two, and if you want it fast, ask Claude how to set up Remotion rendering on AWS. The storyboard-before-render step is the cheap checkpoint that saves the expensive one.
@tuanacelik [Claude Code]
Claude Code#43
https://x.com/tuanacelik/status/2123101754564751744
An instructor on a new DeepLearning.AI short course about tabular foundation models describes the agent lesson: Claude Code gets the TabPFN MCP server and a skill, so it recognizes when a question is really a prediction problem and delegates it to the model instead of hand-rolling one. The rest of the course covers how TabPFN predicts on a new dataset without training, how to interpret results, and training a nano TabPFN from scratch on synthetic data. The pattern is the useful part for data teams: the agent should know which questions to hand to a specialized model, the same way it hands file search to grep. It is a course post, but the design choice is concrete and copyable.
🗣 User Voice
User Voice
Visibility is the feature people miss first when the agents get a manager. @iamlucas_ai moved to Claude Code Projects and lost the live view of every subagent, model, duration and failure that made a 286-agent workflow readable, and now gets a tidy summary instead, while @SimplyColeB finds one Grok Bot juggling five projects loses context that five separate Claude Code sessions kept.
Code Mode is welcome but people want the fine print up front. @corj1k points out that in auto mode the classifier reviews the script rather than each call and cannot see paths computed at run time, so hard rules still belong in hooks, the same lesson behind the Claude Code team's own verification post.
Price per finished task is the comparison users now run every day. @TJeparskis asks why Codex limits burn almost as fast as Claude Code's when Opus costs over 10 times more per task, @CodetocashAi and @bebuu_ai shared harness tests where the same model cost far more inside Claude Code than in lighter harnesses, and @knowixbuilds hit 50% of a $200 plan within a day of the reset at 3.44 billion tokens.
The usage pool is shared across products, and that hurts. @AGTPinsights collected Duet early-access reports where checking email every five minutes ate 40% of a Max weekly allotment, and @dr_andrewlaw is burning through Grok Bot limits while Claude sits at 20%, which says more about orchestration habits than about either model.
Switching is real but rarely clean. @DaveShapi is benchmarking Sol against Opus on a full app after Claude kept inventing rules on a long project, @RafaelVectar moved from Codex to Claude Code mainly for Remote Control, @ChrisGPT spent two days wiring Claude Code to Codex only to see a startup ship it the next day, and @camharris_ reminds everyone that many enterprises have only just allowed the chat app, not Claude Code at all.
📡 Eco Products Radar
Eco Products Radar
Codex: the default second seat, as worker under a Claude coordinator, as reviewer, or as the cheaper rival in head-to-head tests.
Grok Bot: the orchestrator that installs Claude Code and Codex on its virtual computer and hands them the coding.
Muse: the light personal agent people run beside Claude Code, sometimes as the one running the team.
Code Mode: shipped as an experiment the same day, already tested on batch reads and debated for its permission model.
Obsidian: the shared memory vault that business setups read before and write back after every session.
Remotion and FFmpeg: the code-to-video layer under almost every agent video pipeline.
ElevenLabs and Whisper: voice cloning and transcript checks in automated video production.
Blender and Blender MCP: the 3D workhorse for scenes, stations and game assets.
Tripo: 3D models for game characters and props from images and multiview references.
Gemini 4 and Antigravity: the cheaper benchmark rival and the place people send their Claude Code logs for review.
Fable 5.2 and Opus 5.5: increasingly split into planner and worker inside the same session.
Hermes and OpenClaw: personal agents on dedicated machines next to Claude Code.
T3 Code: the dashboard people use to price their Claude Code usage and run multiple harnesses.
← Previous
Everful Raises $48.5M Series A for AI Agents That Source From Chinese Factories
Next →
Loop Daily: 2026-11-20
← Back to all articles

Comments

Loading...
>_