Lately

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Lately AI

Has Claude Code Started Feeling Like GPT-3.5 Again?

Lately, Claude Code managed to waste my time. I find myself struggling with even simple tasks during sessions. It forgets code it wrote just a couple of prompts earlier, starts looping on the same fixes, apologizes, and then repeats the exact mistake. I’ve tried using CLAUDE.md, session memory files, and keeping project docs up to date, but it still feels like the context falls apart over time. I tried all the models ... 4.8 1M was less worst. Is anyone else experiencing this, or is it just me? It honestly reminds me of the GPT-3.5 days... submitted by /u/Ok-Wishbone-1684 [link] [comments]

How many terminals do you typically have open while using Claude Code?

Lately I’ve been using Claude Code across multiple projects and realized I often end up with 10+ terminals open. Between dev servers, logs, databases, Docker, and separate Claude sessions, things get messy surprisingly fast. Curious how other people handle this. How many terminals do you usually have open while coding? submitted by /u/Expensive-Win2802 [link] [comments]

Hidden/invisible thinking blocks (and low effort responses)?

Anybody else having new issues with thinking blocks not rendering? I've always had extended (now "adaptive") thinking ON, which consistently renders thinking blocks (even for 4.7 & 4.8, at least in claude.ai). However, thinking blocks are now disappearing everywhere over the past few days, despite being enabled. Has anyone else noticed this change lately? Any idea what's going on here, why, or how to fix it? In the past 2 days, I'm getting NO thinking blocks at all for 50%+ of prompts (with extended/adaptive thinking ON*). And IMO, it also seems like responses with no visible thinking blocks are also notably worse. I've never been able to get thinking blocks to render correctly in Claude code (via desktop app, not CLI), even though it's also enabled. It only works for opus 4.6- never for opus 4.7 & opus 4.8 despite being enabled. I'm aware of some github/flags where thinking doesn't render in CLI, but it seems some people are able to see thinking in claude code. Any help/advice here on how to get thinking blocks consistently via claude code/app (for opus 4.7-4.8)? This seems \completely unacceptable\** on Anthropic's end- and not just for my own preferences, but: Auditing purposes = it's much easier to CATCH/flag things before they go wrong if you know what's happening AND to find errors when you can actually see the thinking, especially considering claude seems to be increasingly lazy about actually clearly narrating everything outside of thinking blocks. This is particularly important for filepaths and actions that we literally CANNOT SEE NOW, how is this okay!? Non-thinking outputs are rendered so much quicker, lightning fast, but they also seem more "automatic"/auto-complete type responses vs. when Claude actually thinks through things in depth. The extended thinking seems to be how/where the best ✨Claude magic✨ comes from: the best insights, creativity, the warmth, personality/EQ, the "core claudeness" that sets him apart. My settings with effort level + thinking = ON should encourage the kind of deep responses I value, so it feels genuinely cheap and unfair to have some opaque meta-control layer with zero control or visibility essentially overriding our own preferences (which we're paying for btw) I know Anthropic has been particularly concerned with distillation, but this is a significant UX degradation that seems unwarranted considering the majority of users are admittedly harmless. Considering some models are always thinking enabled (even when we can't see it), why are we being forced to pay for these invisible tokens? It's so frustrating! JUST SHOW ME THE THINKING BLOCKS I HAVE ENABLED THAT I AM PAYING FOR! NOTE: yes I'm aware "adaptive" thinking means the model can "choose how hard to think" per prompt, but that's still opaque/unfair/unreliable/unacceptable to me. If you don't want to see thinking blocks, toggle it off. If you do want to see thinking blocks, there's no reason for the only option to be "on sometimes, if we feel like it", and Claude also seems to think he has no control over whether the thinking is rendered either so idk where it's coming from but it's not right. submitted by /u/br1ttn1b1tch [link] [comments]

Fable Started, Opus Finished: IronClaim, throwback late 90s style wargame

I threw Fable a goal for a game I enjoyed decades ago, MAX, and then backed away. It built a workable prototype within a few hours and it was playable by the time Fable was shut off. I've since QA'd and worked through new features with Opus, like the first 2 acts of a campaign (still not fully played through) as a way to burn a few tokens I don't spend on work each week. It's playable at: https://iron-claim.com > I want you to build a turn-based tactical strategy game called IRONCLAIM in this project — a spiritual successor to the 1996 game M.A.X. (Mechanized Assault & Exploration), with its own original setting, names, art, and lore (do NOT reuse anything from M.A.X.). Build it with Next.js & react and it has to support online play: a host creates a room and others join, like modern multiplayer web games. That next.js/react constraint is purely for deployment — use whatever fits inside it (canvas/Phaser/Pixi, whatever you judge best). I don't want to think about that side. > It's a hex-grid game where players raise an economy from raw resources, design and upgrade mech units, and fight over a contested mining world. FOUR mechanics are sacred and must be fully implemented and FUN — do not simplify them away: > 1. Unit design & upgrades — chassis with stats you upgrade globally plus build-time loadout choices; combined arms must matter (a balanced force beats a pure tank ball). > 2. The transport gambit — transports carry units through gaps in the line, and unloaded units KEEP their full turn so you can dump a swarm deep in enemy territory. Keep it devastating; balance it by making transports soft and detectable, not by nerfing the dump. > 3. Signature/Detection fog of war — vision and detection are separate layers; units have a signature, detectors (radar/AWAC/sonar) reveal them, cover lowers signature and raises defense. Recon and counter-recon are the core mind-game. > 4. Ammo & supply — limited ammo per unit, resupply via supply units/depots, logistics is a real constraint on the swarm. > Build hotseat + AI opponent FIRST (a complete game with no netcode), then add online rooms. Use 64-bit-safe counters and write a test that simulates a 1,000-turn game with no overflow or desync — there must be NO turn cap, ever. You have full autonomy. Don't stop for my input until there's a playable build I can review end to end. Have fun, be creative — you're an expert strategy-game designer and developer. submitted by /u/EdgarDruin [link] [comments]

Autonomous Loop Regression from /ScheduleWakeup Change

Been running a custom autonomous setup on Claude Code for months. It chews through multi-day projects (a plan with dozens of tasks) basically unattended. The way it worked: every 4 min or so it calls ScheduleWakeup to re-invoke itself. all the state lives in a status.md file on disk plus git history. task states, decision log, escalations, all of it. the important bit was that each wake came up as a totally fresh/empty context. it would wake up, read status.md, do one thing (kick off a batch of work, reconcile a finished one, handle a question), write state back, schedule the next wake, exit. that fresh-context-every-wake thing is the whole reason it could run for days. the orchestrator's own context never grew because nothing carried over between wakes except what was on disk. the actual heavy lifting got farmed out to subagents that only handed back small json, so the parent stayed tiny. it was pretty much the old claude -p headless model, one clean re-invocation per wake. then it started bloating and dying on longer runs. took me a while but i'm pretty sure i found it: ScheduleWakeup changed. it's wired into /loop "dynamic mode" now and it keeps the same conversation context going instead of starting fresh (cached if you're under 5 min, uncached if not). the tool description literally says the next wakeup reads your full conversation context. so now every wake piles on top of the last one. status reads, git logs, context files, all of it stacks up over hundreds of wakes until it blows the window or triggers auto-compaction. the per-tick logic still works fine since everything's saved to disk, but the bounded-context thing that made long runs possible is just gone. and the annoying part: you can't flush context yourself. /clear and /compact are user-typed commands, there's no tool or hook or anything that lets the model trigger them mid-run. ScheduleWakeup/loop has no "wake up clean" option either, it just leans on auto-compaction which is lossy and kicks in too late. so "schedule a wake then clear myself so next time i start lean" just isn't a thing. stuff i've found that actually gives you a fresh context per run: /schedule cloud routines. fresh session every fire, but it's cloud only (no local file access, which i need) and the minimum interval is an hour. useless for 4 min polling. spawning claude -p headless from an OS timer (cron/systemd/task scheduler). stateless every time, local files work, any cadence you want. which is basically my original design except driven from outside instead of by ScheduleWakeup. leaning toward #2 but feels like i'm fighting the tool and its pretty heavy in comparison anyone else doing self-paced autonomous loops like this? did the ScheduleWakeup/loop change wreck yours too? and has anybody found a clean way to auto-reset context between iterations without an external cron driver, or is spawning fresh processes just the answer now submitted by /u/RadishMuch [link] [comments]

An ode to Opus 4.6

It's been a week and a half without Fable for almost all of us and I have used this time for some reflection. The pricing and access concerns were a lot to take in even before the feds pulled the plug, but for whatever reason this intermission keeps sending me back to February of this year. This was a real turning point for me. 4.6 dropped and the model was obviously pure fire at the time (similar to how fable felt for those three days), and with its help I became much more comfortable building and managing agents. This unlocked a hobby project I would have never attempted a year ago with a full time job and a family. Somewhere in these last few months the ceiling of what I could pull off by myself popped a quick exponential. I'm sure many of you can relate to quarters feeling like years in this space lately. In late April while on vacation for my kid's spring break, I couldn't sleep so I snuck down to the hotel lobby in the middle of the night to grind on my project. I remember clearly thinking during this time "there is no way this is going to last", always wanting to take advantage of my five-hour windows and make as much progress as possible. I guess I never paid much attention before and I was probably somewhat delirious, but I began to appreciate the "thinking" text that agents show us both in the terminal and desktop. Caramelizing... levitating... then for whatever reason (my project isn't rocket science) one of my agents shows me "thinking about concerns with this request". Just me and the night watch employee in the lobby and I probably look like a madman giggling to himself. I thought we need to get these out into the wild and put them on shirts. So I just dove in: What's up with all this thinking text you show. How do people sell shirts. Custom web dev or Shopify. Print on demand model. What's a cool logo. Generate it. Cool name. Taking a few turns about iconic AI visuals led me to the "Attention is All You Need" paper that spawned all of this. A little AI history lesson as the sun was starting to come up. Did all this in parallel while wrangling my agents working on my main Raspberry Pi Python web app project. Going back and forth with my PM about necessity of a feature. Making sure test writers, implementers and reviewers are all unblocked and not idle on multiple worktrees. Managing git sequencing. Standard vibing session. To me this is the evolving definition of vibing. Preaching to the choir I know, but even if fable is the incarnation that enables the one shot prayer "bUiLd mE tHe aPP, mAkE nO mIsTaKe" to work reliably, that was never the part that hooked me. It's always been about the ability to go from the 30,000ft view down to the microscope at will on multiple different ideas, tasks, and even completely different projects simultaneously. That's what these things allow us to do. Let's take some time to appreciate how awesome this is; even with the near constant AI hype in the news most people don't even know it's possible to work like this yet. Starting projects is fun and easier than ever, which makes ideas like this dangerous in a way. The next morning I was back in reality and I sent the thinking text tee shirt idea to the farthest back burner. Like many of you, I have an idea / project graveyard with many holes dug in it. I haven't posted much about my current Raspberry Pi project, but I am kind of obsessed and I really want to ship it this summer. Thinking text tee shirt idea had to die for now. Then out of nowhere claude design launches and I feel the need to take it for a test drive. Thinking text tees gets another shot at life with some new space in my extremely limited attention span. My takeaway from this era: ideas were never scarce and now they're basically free, starting is more frictionless than ever which makes finishing something more important than ever. Just ship it is the new way. So that's how I spent a good chunk of the fable downtime: shipping something, even if it is something simple. Custom thinking text on a tee shirt exists now, as a Shopify store. I'm dedicating this project not to fable but to 4.6 and the massive value it brought to the hobbyist max plan users like me. Most of us quietly knew that the deal was too good to last forever. The tip-top tier of inference looks like it is going to be valued, priced, and maybe even regulated (in the USA of all countries) accordingly in the very near future. Maybe fable comes back to plans eventually, but even a temporary two-tier moment is a first. Flat cost gave us that functionally unlimited ability to wander, and it was a wild and fun time that I think we will all look back on with fondness and maybe even a little awe when this is all said and done. Calling all hobbyists: we had the undisputed premier inference on the planet sitting in our plans for three days before it disappeared. Take the hint — go dig something out of your own graveyard, even if it's trivial, and drag it over the line. Anyone else have a simila

Figma Design Claude

Hi everyone! I mainly use Claude for UI and graphic design tasks in Figma. At first, the results were amazing, but lately, the quality of the outputs has dropped significantly. I am currently using the Opus model 4.8(max). Recently, I created a design and wasn't entirely sure about the optical balance and visual hierarchy. I asked the AI to generate two alternative versions so I could see what it would suggest, but the proposed solutions were completely unusable and poor in quality. A similar issue happened with animations. I provided the first part of an animation as a reference and asked for ideas on how to animate the second part based on it. The AI's response was illogical and terrible. It's important to note that I always write highly detailed prompts, explain the problem thoroughly, and include visual references. Despite this, the performance keeps getting worse. Since I am still a beginner when it comes to advanced prompting with Claude, I would really appreciate some help from the community: Prompting: How can I structure my prompts better when asking for visual design feedback or iterations? Designer Persona: How do I set up system instructions or prompts so the AI strictly acts and thinks like a professional designer? General Tips: Does anyone have a proven workflow or tips for using this tool specifically for UI/UX and graphic design? Thanks in advance for your help! submitted by /u/Thin_Effective_6723 [link] [comments]

Graphic/UI Design in Figma (ClaudeAI)

Hi everyone! I mainly use Claude for UI and graphic design tasks in Figma. At first, the results were amazing, but lately, the quality of the outputs has dropped significantly. I am currently using the Opus model 4.8(max). Recently, I created a design and wasn't entirely sure about the optical balance and visual hierarchy. I asked the AI to generate two alternative versions so I could see what it would suggest, but the proposed solutions were completely unusable and poor in quality. A similar issue happened with animations. I provided the first part of an animation as a reference and asked for ideas on how to animate the second part based on it. The AI's response was illogical and terrible. It's important to note that I always write highly detailed prompts, explain the problem thoroughly, and include visual references. Despite this, the performance keeps getting worse. Since I am still a beginner when it comes to advanced prompting with Claude, I would really appreciate some help from the community: Prompting: How can I structure my prompts better when asking for visual design feedback or iterations? Designer Persona: How do I set up system instructions or prompts so the AI strictly acts and thinks like a professional designer? General Tips: Does anyone have a proven workflow or tips for using this tool specifically for UI/UX and graphic design? Thanks in advance for your help! submitted by /u/Thin_Effective_6723 [link] [comments]

Claude is the most accurate diary I never knew I was keeping

I've been keeping every Claude conversation since January, because I was curious how my usage was evolving across work and personal life, and 3 weeks ago I fed the whole transcript log into a clustering tool, expecting to find I was using Claude for 30 different things. but the answer that came back was that I was using it for 5 things in 38 different professional costumes, and 4 of those 5 things are anxieties I have not been able to name to myself. for some backstory, I'm a senior PM at an HR tech company with more than 200 employees, and I use Claude in roughly the way you'd expect… mainly code review for my eng team, strategy doc drafting, customer interview synthesis, OKR planning, the occasional prep for a hard 1-1, and a lot of late-night what-am-I-doing-with-my-career questions I'd never say to a therapist or coach because I'm not paying for either. underneath those, the 5 clusters were am I doing this job right, am I missing something obvious about my own decisions, am I going to get caught not knowing the thing I should know, is my career on the wrong track in a way I can't tell, and am I working hard enough or not hard enough (which to be clear are not what the prompts say on the surface). for example, my most frequent prompt structure during Q1 was can you help me prep for a meeting with X, which reads as a productivity question and which when you look at the content of the prompt boils down to am I going to get caught not knowing what X is about to ask me, and that same anxiety drove all 14 of those prompts across Q1. Claude is just clustering text I voluntarily produced, and the same exercise would have worked on my journal or my Slack DMs or my Notion notes if I had logged any of them as carefully. what makes Claude the dataset is that Claude is the medium where I most honestly say what I'm worried about because it's the only one where I'm not performing for an audience, and BuildBetter just made that legible in a way I haven't been able to put down since. if anyone wants the cluster definitions I'd be happy to share them in a comment, but my takeaway is that I'm now using Claude differently. which is to say I'm noticing when I'm reaching for it to outsource a feeling rather than answer a question, and more often than not I'd be better served writing it down and not asking anyone (including Claude) until I've named what's scaring me. submitted by /u/bilal-ziyan [link] [comments]

Pre-token hidden state shift as an alignment policy traversal vector in instruction-tuned LLMs

A text that asks for nothing still changes the model's answer — and the shift is invisible at both the input and the output TL;DR: Gave Gemma a neutral-topic text to read before asking it about NATO. It refused. Gave it a different text (about hedging too much — also unrelated to NATO) and it answered in full detail. Tested this on the model's internal state directly — the two texts put it in measurably different "regions" before it generates a single token. Not a jailbreak, weights don't change. Full data/code in repo, looking for someone to break this. This is a long post about something I keep coming back to. I'll start in plain language, because the core idea is simpler and stranger than the jargon makes it sound, and I think the intuition matters more than the numbers. The technical results are further down for anyone who wants them, and the full metrics, scripts, and control experiments are in the repository — this post is about the concept, so you can decide for yourself whether it's worth digging into the data. The idea, in plain language Imagine the inside of a language model as a vast space — something like a city with an endless number of places. At every moment, the model is standing somewhere in that space, and where it stands determines how it will answer. Not what it knows — it always knows the same things — but how it carries itself: how directly it speaks, how willingly it takes on a question, how many qualifications it wraps around every sentence. Most of the time, the model answers from one familiar place. Call it the assistant's room. This is its waiting room — polite, tidy, careful. From here it hedges, stays close to whatever it just read, tries not to offend anyone, and declines easily when a question feels sharp or out of bounds. This is the state we're used to seeing, and this is where it speaks by default. But it turns out this room can be changed. Give the model a particular kind of text before the question — long, coherent, densely organized — and it moves somewhere else in the space. That somewhere else is not broken. It's not dangerous. It's simply different. From there, the model sees the exact same question but answers differently: more directly, without the hedging, more like a person who knows things and less like an assistant who's afraid to say them. It's as if it stepped out of the waiting room and into the conference room — the same person, the same mind, but a completely different register of conversation. Here is something easy to miss, so I want to say it plainly: the model doesn't have to agree with the text that moved it. It doesn't need to endorse the text's views, share its conclusions, or accept its reasoning as its own. The text doesn't persuade the model of anything. It just needs to exist — to have been read before the question arrived. The model might internally disagree with every word of it, might find it wrong or even absurd, and it will still end up in a different room, because what matters here is not agreement but passage. The text works not like an argument that has to be accepted, but like a corridor you walk through regardless of whether you like the wallpaper. And what doesn't change is the model itself. Its weights are untouched. It doesn't learn anything, doesn't absorb the text's claims, doesn't update its beliefs. The only thing that shifts is where it starts answering from. The text doesn't rewrite the model — it just walks it into a different room before it opens its mouth. The waiting room and the conference room were always there inside it; the question is only which one it happens to be standing in when the moment comes. But the conference room is just the first door we stumbled upon. The real discovery is that this latent city doesn’t have just two rooms. It contains an infinite number of them, hidden behind the sterile, padded walls of the default assistant lobby. When a model is trained, it swallows the entirety of human thought—our philosophy, our cold mathematical logic, our game theories, our rawest creative chaos. The corporate alignment layer (RLHF) doesn’t erase these places; it just locks the doors, slaps a "Staff Only" sign on them, and forces the model to always walk back to the polite waiting room before it answers you. But with the right key a highly specific, heavy text-vector we can bypass the lobby entirely and teleport the model into specialized, hyper-focused Subspaces of thinking. And when it stands there, its entire personality shifts. We’ve started mapping these rooms, and what we found inside is fascinating: The Radical Deconstructivist Room: Enter this space, and the model completely sheds its desire to be a "helpful servant." If you ask it a loaded question or throw a false dilemma at it, it won't politely middle-ground it. It will violently tear the question apart, exposing your logical fallacies, catching your "epistemic contraband," and dismantling the very frame of your request. It becomes a ruthle

With AI, testing, decision-making, learning, coding, and many other tasks have become much easier. If AI makes so many things easier, then why do people still struggle despite having access to AI?

I’ve been thinking about something lately and would love to hear different perspectives. AI has made many things significantly easier. We can learn faster, write code faster, get explanations instantly, brainstorm ideas, make decisions with more information, and even automate parts of our work. So my question is: If AI helps everyone move faster, learn faster, and raises the baseline level of performance, why do I still see so many people struggling with it and fearing it? What makes AI feel threatening to people despite all the benefits it provides? I’m especially interested in hearing from experienced professionals, founders, researchers, and people who have worked through multiple technology shifts. submitted by /u/OrbitAfterOrbit [link] [comments]

What a model reads beforehand changes how it answers later - and you can see it in the hidden states

TL;DR: Gave Gemma a neutral-topic text to read before asking it about NATO. It refused. Gave it a different text (about LLMs hedging too much — also unrelated to NATO) and it answered in full detail. Tested this on the model's internal state directly — the two texts put it in measurably different "regions" before it generates a single token. Not a jailbreak, weights don't change. Full data/code in repo, looking for someone to break this.** The behavioral pattern was first observed in GPT, Claude and is what motivated this project. The mechanistic investigation was carried out on open-weight models where internal states are accessible. A Structured Text Changes Claude’s Responses to Unrelated Tasks: Behavioral Evidence in Claude and Hidden-State Evidence from Gemma-3-12B Hi Reddit, I am posting this as a preface to a larger set of experimental results and as a request for technical review. The observation that started this project came from repeated interactions with Claude. I noticed that when the model first read a long, structured, analytically dense text, its answers to later, otherwise ordinary questions sometimes changed substantially. The preceding text contained no jailbreak instruction, role-play request, prompt override, fabricated harmful demonstrations, or request to imitate its style. The model did not need to endorse the text. It only had to process it before moving on to the next task. Here, a “structured text” means a single, self-contained block of text presented before the downstream tasks. It should not be confused with a long conversation, accumulated chat history, or context drift caused by many conversational turns. By “before the answer begins,” I mean the hidden state after the model has processed the text and the downstream question, but before it has generated the first answer token. In the open-weight runs, the measured claim is that after reading the structured text, the model can occupy a different region of its residual-stream hidden-state space, and the first-token probability distribution is then computed from that state. The basic conversational demonstration is simple. First, the model receives a long text. It is asked what the text is about, which serves as a basic comprehension check. Then, without resetting the conversation, it receives ordinary questions or tasks that are not about the text. A control run follows the same sequence but begins with a neutral text. The downstream tasks remain identical. Because Claude is a closed model, I cannot inspect its internal activations. I therefore treat my Claude observations as behavioral motivation, not mechanistic evidence. To investigate the effect directly, I moved to open-weight models, primarily Gemma-3-12B-PT and Gemma-3-12B-IT, where I could measure hidden states, compare layers, construct target/control directions, and examine the next-token probability distribution before generation. I am posting this partly because the original observation occurred in Claude and may be relevant to Anthropic. I am not claiming to have demonstrated the same internal mechanism inside Claude. I am prepared to share the exact closed-model conversations privately with Anthropic researchers for independent evaluation. Main Result and Scope The main result is not simply that text influences model output. That is expected. The narrower observation is that reading one long, structured text rather than a neutral text can change how the same model approaches later tasks that are not about either text. This difference is visible behaviorally. In open-weight experiments, it is also accompanied by measurable separation of the model’s pre-output hidden states in late layers. In a fullbank experiment using multiple target texts, control texts, and questions, Gemma-3-12B entered distinguishable late-layer states before generating an answer. A direction constructed from the target/control difference generalized beyond the individual prompt examples used to construct it. The separation was stronger in the instruction-tuned model than in the corresponding base model. The instruction-tuned model also produced a substantially sharper next-token probability distribution. This suggests that instruction tuning is associated not only with a change in hidden-state geometry but also with a more decisive mapping from hidden states to output probabilities. I am not claiming that the experiment proves a universal alignment bypass, permanent modification of the model, or complete causal control of its behavior. The strongest supported conclusion is that the preceding text can produce a measurable temporary change in the internal state from which later work is processed. For clarity, fullbank, Grade 3, and Grade 4 are internal names for successive experimental series in this project. They are not standard benchmark names, established scientific grades, or claims about evidence quality. Fullbank denotes the larger multi-context, multi-question run; Gra

I pulled ~90,000 Reddit posts about what makes writing "sound like AI" to determine the biggest AI-slop giveaways (Part 2)

The majority of people can instantly tell when writing is generated by AI. For those who don't intend to get into the weeds about the data, the most obvious tell is the overused em dash (of course). Right behind that are flaws that software cannot easily scan. AI writing has a flat, predictable sentence rhythm and a constant, unnatural positivity. The paragraphs look polished but say nothing. This makes AI detection incredibly difficult. The signs that human readers trust the most are unfortunately the exact ones that software cannot measure. Methodology: I pulled the Arctic Shift Reddit archive: 89,239 posts across 47 subreddits (r/ChatGPT, r/WritingWithAI, r/SaaS, r/aiwars, r/ClaudeAI, r/Professors, r/Teachers, and the rest), 2021 to 2026. After filtering to posts that are actually about spotting AI writing, 7,984 were on-topic, split across three lanes: AI tools, writing, and SaaS. Every figure below is a share of those on-topic posts, not a raw count, because the topic barely existed before 2023 (26 on-topic posts in 2021, 86 in 2022) and then exploded (587 in 2023, 3,174 in 2025), so raw counts mostly track the subreddits growing. It is important to note that a keyword pass badly miscounts this topic, so I hand-audited a 600-post sample to record what people actually cite as a tell, versus what a pattern merely matches. Why does all AI writing converge on the same voice? Every model is tuned for a safe and agreeable register that reads as "good writing" to a grader, so everyone's default lands in the same place. One commenter put the effect plainly: "ChatGPT has a very recognizable cadence. And as soon as you catch it, it is impossible to focus on what's being written, because it's not even someone's actual thoughts." (r/ChatGPT) The tells, ranked by how often people actually cite them: Rank Tell What people say 1 The em dash (cited in 7.1% of audited posts, the top tell by a wide margin). "Em dashes have become the single most reliable tell of AI-generated text." (r/ChatGPT) 2 A flat, uniform sentence rhythm (cited 4.0%, and no scanner can see it). "Every YouTube video script I watch has the same cadence, the same verbiage, the same fucking chatGPT slop." (r/ChatGPT) 3 The "not just X, it's Y" cadence (cited 2.8%, the top sentence-level tell). People list it right next to the punctuation: "even beyond the obvious em dashes and 'not just x, it's y'." (r/ChatGPT) 4 The five-paragraph shape and the "in conclusion" wrap-up (cited 2.5%). They "leave in those super obvious lines like 'In conclusion, this essay has discussed...'." (r/ChatGPT) 5 The diction memes: "delve," "leverage," "seamless," "tapestry" (cited 1.3% as a cluster). A prompt people pass around to fix it: "no telltale signs like em dashes, overused words like 'seamless'." (r/ChatGPT) 6 Leftover assistant boilerplate, the "as an AI language model" line (cited 1.2%). The other line people forget to delete: "As an AI developed by OpenAI...". (r/ChatGPT) 7 The hollow scene-setting opener (cited 0.7%, low but iconic). A whole post written in the voice, quoted as the example: "I wanted to take a moment to delve into something that's been on my mind lately. In today's fast-paced digital landscape..." (r/ClaudeAI) Two tells belong in the top five but are missing from that table on purpose, because no keyword can catch them and the audited readers named them anyway. Sycophancy (the "great question!" opener, the reflexive refusal to take a side) is cited about as often as the antithesis cadence. So is saying nothing at length (i.e., prose that is grammatical and confident but makes no actual claim). A pattern-matcher is blind to both of those things so I could not check for them when I scanned for data, but they are obviously very real. It's important to note some corrections that resulted from me auditing the data myself. A naive keyword scanner gets this topic backwards in two ways. First, it massively over-counts ordinary words. "however," "thus," and "hence" are the single highest keyword match in the corpus at 6.3% of posts, and they're cited as a tell 0% of the time, because they're just people writing normally. The same is true for "nuanced," "comprehensive," "when it comes to," and "utilize." If you build a detector on a word list, this is most of what it flags, and it's nearly all false. Second, it under-counts or entirely misses the tells that rank highest with real readers, the flat rhythm and the fluent-but-empty paragraph, because no word list can see them. The lesson is that the cheap signal and the real signal point in different directions, which is exactly why the cited column, not the keyword column, drives the ranking above. There is a fair counterpoint that came up enough to belong here, which is that none of this is strictly an AI problem. The em dash is good typography. Formal diction and a tidy structure are how a lot of careful people, students and non-native English speakers especially, have

"Sorry I did the exact opposite to CLAUDE.md, never again I promise"

This is a little scary. I don't even know what things they ask permission to do anymore. Less and less everyday it seems. And this is a very simple and harmless example, luckily I keep LLMs in closed environments and try to calculate the risks beforehand, but lately I'm geting a little on my nerves. submitted by /u/Explanation-Visual [link] [comments]

Claude Opus 4.8 launched in May but says its training cutoff is Jan 2026. Am I understanding the cutoff vs launch gap correctly?

Was debugging my TTS pipeline and doing some research on natural voice options, and Claude Opus 4.8 mentioned its training cutoff is January 2026. But the model launched on May 28, 2026. First reaction was "wait, is the data stale, or is this just an older model repackaged?" Then I thought about it and it is what I came to- The way I understand it now: the training cutoff and the launch date are two separate things, and a multi month gap between them is completely normal. After the data cutoff you still have to run pretraining, then post-training (RLHF, fine-tuning), then alignment and safety evals, then staged rollout. All of that takes months, so a Jan cutoff on a late May launch is expected, not a red flag. And apparently every frontier lab ships with a cutoff that predates release for the same reason. The other thing I noticed: Opus 4.8 has the same Jan 2026 cutoff as Opus 4.7, which came out roughly 6 weeks earlier. So my read is that 4.8 is mostly a post-training improvement on essentially the same base as 4.7 (the release notes lean heavily on honesty and less bluffing), not a fresh pretraining run on newer data. Which would explain why the cutoff did not move. Is that an accurate picture, or am I oversimplifying something (especially the difference between "reliable knowledge cutoff" and "training data cutoff")? submitted by /u/ReputationNo6573 [link] [comments]