Claude Code wrote the code. u/vkorost pulled the trigger. He built ScreenPlink in about two weeks: shoot a laser at your monitor, and a webcam detects the hit while the game scores it. The tricky part was helping Claude debug something it couldn’t physically test. He added an MCP server exposing camera frames, coordinates, and rejected detections so Claude could inspect what the app actually measured. One error kept blaming the camera. Claude traced it to a missing artwork file. He also reintroduced known bugs to verify the tests caught them, and required five clean cold starts before calling a build ready.
brandSteady
Claude Code on X
The biggest single theme is finished work: people describe apps, automations and fixes Claude Code completed, often naming the setup that made it work. The recurring objections are what it costs and how fast allowances drain, and Codex is the comparison people keep making.
First written 27 Oct · what changed · from 392 posts by 359 people
Tracking posts that say “claude code”
Track this for your marketPosts, last 24h
96
−32%vs. previous 24h
Posts, last 7 days
775
237 in the last 72h
Velocity
111/day
7-day average
Momentum
−13%
Last 24h vs. a normal day this week
Posts per day, last 30 days
as of Nov 3, 08:00 UTCWhat changed
as of 27 Oct · checked once a monthFirst written 27 Oct. When what people say changes, it shows here.
Tone· 189 posts from 183 people· written 27 Oct
How do people feel about Claude Code?
People judge it on what it finished: 150 of the 183 people here describe real work it completed, from a CarPlay app to a server fixed after an attack, rather than general praise. Unqualified enthusiasm is a smaller, separate group (21 people), and 3 come away disappointed enough to cancel or call the harness intolerable.
The positive reports are specific about the job. People describe a CarPlay screen rebuilt off one prompt, internal CRM, pricing and reporting tools replacing paid SaaS, a 61KB WebGPU page, 1Password accounts rotated by script, 2.1M Polymarket trades analysed, spyware found on a phone, and a site under attack patched and redeployed in 15 minutes.
What they pass on is the method rather than the magic. One project split into a planner session on Opus and a builder on Sonnet is described as "one project, two sessions"; others add CLAUDE.md rules, MCP servers that expose what the agent cannot test itself, and a rule that a build is not done until five clean cold starts pass.
A smaller group states the caveat with the praise (6 people): building the wrong thing faster, with judgment and verification still theirs. A few like it but say allowances get in the way (4 people). Among the disappointed, one calls the harness "legitimately evil" and another tells a user to cancel.
- Works well155
- Loves it21
- Fast, but you still own the judgment6
- Likes it, but the limits hurt4
- Disappointed with it3
See 5 of 189 postsHide the posts
I gave Claude one prompt and this is what happened to my CarPlay... My BMW screen looked the same every single day. Same 3 icons, same blue wallpaper. Last night I sat in the car in the rain and asked Claude Code one thing: can you build me my own app for this screen I didn’t
Hassan 把他日常做应用的工作流公开了！ 语音 → 视觉参考 → 澄清问答 → v1 反馈 → 录屏验收 → 发帖或扔掉 的闭环；harness 混用 Claude Code（Opus 5.5 high） 与 OpenCode（DeepSeek V4.1 Flash / GLM 5.3），并给 Agent 接上部署/模型/设计类 CLI 与 skills。 六步工作流 · 用 @WisprFlow 录 1–5 分钟语音作 prompt，细节越多越好 · 补视觉灵感：截图，或 Inspo MCP，让 Agent 知道想要的样子 · 用 @mattpocockuk 的 grill-me skill，让 Agent 主动追问澄清，而不是一上来闷头写 · 拿到 v1 后，再发一串反馈、功能需求与设计微调（通常又是一段语音） · 每个新功能合并 PR 前，先要一段 快速录屏，证明真能跑 · 迭代到满意再发到 X；不满意就扔掉 工具栈 · Harness：Claude Code + Opus 5.5（high）；OpenCode + DeepSeek V4.1 Flash / GLM 5.3 · 给 Agent 的能力：Vercel + GitHub CLI（推代码、部署）；Together skills（聊天/图像/语音模型）；Design/animation skills（间距与交互指引）
Claude Code已经无敌了！！！！ 它基本上可以为你做任何事情！！！ 真的是任何事情！！！！ 🥹🥹
Hot take: AI didn’t make building software easy. It made building the wrong thing much faster. After 10 years of working with clients, I’ve learned that the hardest part isn’t writing code. It’s understanding the problem well enough to build something people actually need.
5 of the 189 posts behind this answer, one per person. The other 184, and every new one as it’s posted, come with tracking. Get early access
Pain points· 107 posts from 95 people· written 27 Oct
What do people complain about with Claude Code?
Cost is the loudest complaint: 23 people count token bills, cache rebuilds and per-task prices, often against a cheaper harness or model. Next is allowances that drain too fast (14 people), followed by security worries (11 people) about sandboxes, keys and a bundled runtime.
The bill talk is arithmetic, not vibes. People total a week of local logs and price it per model, report one session at 500K+ tokens and $50-100 an afternoon, or work out that the harness itself resends instructions every step — roughly 16k tokens here. Others find spend hiding in cache rebuilds and fast-mode credits.
The limit complaints are about pace: a session jumping from 55% to 95%, the 5-hour window "hit in 30 minutes", and Agents SDK usage said to burn the 5-hour meter about 1.7x faster than Claude Code itself.
Security posts read like warnings: sandboxed commands still reading keys unless denied, an AGENTS.md planted in a downloads folder hijacking the agent, and a bundled Bun runtime carrying a disclosed RCE until version 2.1.308.
Behind these sit lost context on new sessions, sessions that loop or fail silently, and diffs that touch 41 files for a one-line fix.
- Expensive28
- Usage limits hit too fast15
- Security and privacy worries11
- Loses context10
- Unreliable, erratic sessions9
- Opaque and clunky to operate9
See 5 of 107 postsHide the posts
PSA for Claude Code users: 1. Claude Code bundles its own Bun runtime, independent of your system's Node.js installation. 2. I confirmed that Claude Code 2.1.296 includes Bun 1.4.3, which contains the newly disclosed Brotli RCE vulnerability. 3. Note that while updating your
One Claude Code session can burn 500K+ tokens on a hard coding task. At Opus pricing ($15/$75 per M tokens), that's $50-100 for one afternoon. Now multiply that across a team — or an always-on agent.
abso-fucking-lutely hate the 5 hours limit in claude code. ngl.
every harness resends its instructions every step - ~16k tokens in claude code, under 1k in mini-swe-agent. one task on glm flash: $1.81 vs $0.56. the loop overhead is the bill before the cap ever matters. optimize the loop, then cap it.
the numbers 👇 - each harness resends its instructions every step: ~16k tokens in Claude Code, ~7k in OpenCode, under 1k in mini-SWE-agent - one hard task on GLM Flash: 1.81 CNY in Claude Code, 0.97 in mini-SWE-agent, 0.56 in OpenCode (list prices) - rerun the same agent on the 45 hardest tasks and about 1 in 8 flips pass/fail. Switching harness flips about the same, so small gaps are mostly luck link
5 of the 107 posts behind this answer, one per person. The other 102, and every new one as it’s posted, come with tracking. Get early access
Alternatives· 87 posts from 83 people· written 27 Oct
What are the alternatives to Claude Code?
Codex is the comparison that matters here: 42 of the 83 people who weigh another tool against Claude Code name it, and most run both rather than pick one. Behind it come Grok Bot (7 people) and Gemini (7 people) for always-on assistant work, then Cursor, opencode and a long tail of harnesses.
The Codex talk is less a switch than a division of labour: one tool hands tasks to the other, each agent gets its own branch, or Opus writes the PR and Codex reviews it. Strengths are split by task — long-session steering, whole tickets, and speed per fix go to Claude Code in these posts; Codex is credited with running live browser and app tests, a smoother CLI and more frequent resets.
Loyalty is tied to allowance. People say they will re-decide after the next Codex reset, and one calls their loyalty "strictly quota-based". Benchmarks are cited both ways: one timed Claude Code at 14.4s per fix against Codex at 34.5s, another at 23.8s against Codex at 44.1s.
The rest is an ecosystem argument. Grok Bot is preferred for persistent, always-on work; Gemini for a first sketch handed to Claude Code; Cursor for nudging code, Claude Code for whole tickets. OpenCode, T3 Code, Orca and Capy appear as shells, and price sends some work to DeepSeek.
- Codex43
- Grok Bot7
- Gemini7
- Cursor5
- opencode4
- Orca4
See 5 of 87 postsHide the posts
AI is moving insanely fast. Codex, Claude, and everything else keep shipping new features, and my head spins every time. I've been building with Claude Code, and a few days ago I tried Codex — honestly it felt smoother. But switching back and forth gets confusing. I can't pay for
Claude Code, and it's not close: Cursor is where I nudge code, Claude Code is where I hand over the whole ticket. Ask me again after Codex's next reset though, my loyalty is strictly quota-based 😅
Pick ONE for the next 30 days, no switching: Claude Code, Codex, or something else (Cursor, Gemini, Copilot...)? Mine's Claude Code. The weekly limits are not good, but it's still better than Codex for me. Reply with your pick and the one reason.
Flint runs 125+ tokens/s on a MacBook. We timed Claude Code vs Codex: 96% and 99.9% of a median fix was model time. Richard Socher's Recursive just shipped Flint, a local coding model sold on speed. So we measured where a coding agent's minute actually goes. 3 bugs planted in a
Codex is WAY better than Claude It’s ability to take over your computer and actually run real live testing on websites or apps is elite Full 360 build loop Claude code can do it with cowork but it doesn’t have nearly the full testing capabilities that open AI has Night and
5 of the 87 posts behind this answer, one per person. The other 82, and every new one as it’s posted, come with tracking. Get early access
Questions· 11 posts· written 27 Oct
What do people ask about Claude Code?
The questions are practical and few: 5 of the 11 people here ask how to choose between Claude Code and Codex or split work between them, and 3 ask how the usage allowances are counted and shared.
Choosing between the two is the recurring one. People who pay for both ask how to divide the work — frontend to which, big refactors to which — and builders who ship with both are asked what decides which one they reach for on a real build. One reader also asks whether Codex and Claude Code sessions can share a single instructions file or need one each, since a stale line in CLAUDE.md can fight a newer model.
The allowance questions are about accounting: whether using up chat limits blocks coding, whether a longer run counts only model time or also the tests and tool calls the agent chose to run, and how usage is managed when Claude Code runs on a subscription on someone else's VM.
Two smaller ones: whether it needs a paid plan or works on the free version, and where the Claude Code window actually is.
- Claude Code or Codex?5
- How do the usage limits work?3
- Is it free or do I pay?2
- How do I get it running?1
See 5 of 11 postsHide the posts
不懂就问： Claude Code 和 Codex 都订了的朋友，你们怎么分活？ 前端给谁，大重构给谁？后端咋弄比较好？
Hey Shakhzod, I'm into AI agents and SaaS. Saw that you ship with both Claude Code and Codex. What decides which one you reach for on a real build?
genuine question: if i use up my chat limits but not my Claude Code limits, can i still send prompts to Claude? because if not then how am i supposed to code?
Does the 1.5x longer count only model time? Or does it also count the tests and tool calls Claude Code chose to run on its own?
Not seeing the model also hides which lines in CLAUDE.md went stale. One added because an older model kept skipping tests can fight a newer one that already runs them. Do your Codex and Claude Code sessions share one instructions file, or keep one each?
5 of the 11 posts behind this answer, one per person. The other 6, and every new one as it’s posted, come with tracking. Get early access
Wishes· 11 posts· written 27 Oct
What do people want from Claude Code?
The largest ask is memory that travels: 3 of the 11 people here want project memory shared across Claude Code, Codex and Cursor instead of re-explaining it at every switch. The other asks are for visible, durable work — an edit log across sessions, background runs that survive an idle machine, and a clearer view of what the agent is doing.
Shared memory is the ask with the largest group behind it: memory kept outside any one company, plugging into whichever agent comes next, and updating everywhere when one of them changes. The stated cost is time — re-explaining the whole project each time you switch tools.
The rest is about seeing and keeping the work. People want a log of edits shared across sessions so changes stay traceable, and one user asks the team directly for it. Background runs freezing when a bot's computer goes idle is met with a request for a keep-awake option. Clearer progress is wanted too: a beginner-friendly setup, and knowing when the agent has wandered off.
Two asks are small and literal: Claude Code on the car screen, and an iPhone widget button that opens Claude Code directly, as they say Codex has.
- Shared memory across agents3
- A shared edit log2
- Keep background runs alive2
- Easier setup and progress2
- Claude Code in CarPlay1
- An iPhone widget button1
See 5 of 11 postsHide the posts
Looking for a tool that: • keeps my AI memory outside any one company • plugs into Claude Code, Codex, Grok, whatever comes next • updates everywhere when I change something in one of them Does this exist? Drop the name 👇
one memory across claude code, codex and cursor is the dream. re-explaining the whole project every time you switch tools gets old fast
Shared memory across coding agents could save hours of repeated explanations and make switching between Codex and Claude Code much easier
The bot's computer pauses when no bot is active, so Claude Code running in the background freezes mid-run. I've moved long runs to my laptop for now. An option to keep the computer awake would fix it. My bot emailed the full report to tibo@ @bot @poteto
Exploring @trycua Spaces and I like the idea behind it. Giving AI agents like Claude Code or Codex their own desktop to work on feels like a practical way to let them handle real tasks without interfering with my usual workflow. I'd love to see a more beginner-friendly setup
5 of the 11 posts behind this answer, one per person. The other 6, and every new one as it’s posted, come with tracking. Get early access
In their words
How do people talk about Claude Code?
The phrases people use most, counted once per person.
- 1“claude code codex”8
- 2“tool calls”3
- 3“side by side”2
- 4“claude code sub”2
- 5“usage limits”2
- 6“per token”2
- 7“per task”2
- 8“resends its instructions”2
- 9“context size”2
- 10“memory across”2
Posts are shown the way X shows them. One of them yours? Here’s why it’s shown, and how to take it off.
Also in AI coding agents and editors
See all 12 in AI coding agents and editors →- Cursor−60%People still credit Cursor with real shipped work and recommend it by name, but the argument has moved to what the bundled X plan gives them and what happens when something breaks.1,180 posts / 7d
- OpenAI Codex+7%The biggest share of the talk is people showing what Codex builds for them.773 posts / 7d
- Cognition (Devin)−91%Cognition's talk centres on a lead-plus-sidekick setup people read as cheaper per task at the same score, and on firsthand users sold on cloud agents — set against crashes, lost sessions, price and limits, with Claude Code the comparison people keep making.470 posts / 7d
- GitHub Copilot+117%The largest group of people praise GitHub Copilot — for accurate code suggestions, work finished faster, and Claude and Codex models reachable on the free plan — while the complaints that follow are about price and credits running out, and people weigh Codex, Cursor and Claude Code as replacements.258 posts / 7d
Get every post about Claude Code, filtered and labelled
This page is the summary. Tracking gives you the stream behind it for any brand, keyword or @mention: each new pain point, request and question as it’s posted, with the spam and promotions already taken out.