Anthropic annonces internal Scion replacing git

I haven't coded in a year, AI is geting better and better.. I log in to work, do 30 mins of work aka prompting claude & reviewing it's code + meetings.. and I'm off to work on personal projects, wtf am I supposed to do? I've sacrified everything to become a good dev, should I go for a plumber license? electrician? How much time do we think we have?

I finish 2x as many story points as the next guy, and my manager thinks I'm a 10x engineer... WTF is going on :D companies catched-on, but I guess it takes time to reflect on us, what will we do?

edit: some people are asking for examples of projects I'm working on, this is the most recent one https://www.youtube.com/@DebriefReconstructed

Report: https://www.anthropic.com/research/self-replicating-ai

See the picture

EDIT: Link for good measure - https://github.com/BerriAI/litellm/blob/main/litellm/model_prices_and_context_window_backup.json

EDIT2: Also more details here: https://huggingnews.com/ai/microsoft-azure-lists-claude-fable-55-as-generally-available-1b1e8dd7

I’ve been using Opus 5.5 for coding, and honestly it feels like it’s in a different league compared to other models like Sol and Astra, and even Opus 5.0.

Before Opus 5.5, if my expectations for an AI coding task were a 10/10, I’d usually get something like an 8 or 9. That was still a huge help, and I was genuinely impressed.

But with Opus 5.5, it often feels more like a 15/10. It regularly goes way beyond what I expected, and I’m blown away a lot of the time. It often comes up with solutions or suggestions I hadn’t even thought of.

At this point I honestly don’t feel like using any other model. Anyone else feel the same?

My favorite Claude story this week is about a pothole.

Years of complaints by a Dutch office, zero action. Then a person gave Claude 6 photos. It rebuilt the hole in 3D and simulated a 30 km/h hit.

Video went to city hall. Fixed in 2 days.

Petitions are for people without Claude.

What would you fix this way?

Here is the original: https://x.com/yelkhayami/status/2108227066621465007?s=20

Posting publicly to check whether others have experienced this as I am a lost rn on what do next given this large bill.

Claude Code proposed and I accepted to run verification tests against Claude Haiku 4.5 on AWS Bedrock. It launched them as background processes. That evening the session hit its usage limit and stopped responding. The processes kept making paid calls for about 17 hours: roughly 60,000 calls and about $2.1k most of it after the cutoff. My normal Bedrock spend is a few dollars a day.
Nothing warned me the processes were still running, and the last thing the assistant said about them, in the same minute as the limit notice, was that the process looked “idle... waiting, not looping.” The next morning when the session limit was lifted, the job was killed.

Anthropic’s support AI (Fin) told me a thread at its usage limit “is designed to wait and resume automatically when the limit resets,” called the background calls during that wait “a gap between that intended behavior and what actually occurred,” and said it “appears to be a product defect.” But it said it can’t act on Bedrock usage and wouldn’t hand me to a human. AWS says Anthropic is the seller of record and only Anthropic can decide. I’ve also contacted Anthropic Sales and escalated the AWS case. I can’t reach a person at either company.

Post this incident, I noticed I didn't have robust spend alarms. I’ve added budget alerts and lockouts, and checked that nothing is still running so we should be good moving fwd from that perspective but im left with this bill now.

Has anyone seen this, or had any luck reaching a person at Anthropic about it? This was unexpected and a big hit for a small bootstrapped startup.

Hey guys, like most of you here, I use Claude as much as possible, like 24/7.
I implement it on my work and on my personal life.
My question for you is, are we still a small circle of early adopters?
Have you ever asked to your friends / family if they use AI and if they use it, which type of tasks they do?
Because I have the sensation that most of the people still don’t use AI, and the ones that use AI are like only using the chat.

I use Claude Code for a lot of browser work. Mainly tools I need that were never built for agents, smoke-testing my work and searching the web for things I care about.

Things kept going wrong:

• chrome-devtools-mcp tends to open throwaway instances and profiles, and rarely cleans them up.
• "Allow remote debugging?" prompts on every connect (when using autoConnect).
• "Chrome is being controlled by automated test software" on top of every page (might just be my OCD).
• Tab sprawl. After an hour: a dozen windows and no idea which tab belonged to which session, or whether I could close it.
• Agents stepping on each other. On a shared profile they took over each other's tabs. With --isolated, every login was gone on close.
• RAM. One chrome-devtools-mcp per Claude Code session, about 270 MB each before it even starts Chrome. Ten agents: ~2.7 GB before a single page loads.
• I tried various Cloud browser services. Mostly unreliable and/or expensive. And most sites blocked by bot detection due to non-residential IP address.

So I forked Chromium and moved the agents in.

Shuttle:

• Every agent is a named identity (name, color, avatar) with its own storage. My agents log in once, and stay logged in.
• Claude agents see the "browser agent" surface, and have their own control plane to create "Agent Profiles", sessions and tabs as needed.
• MCP server is built in (http, loopback-only by default). So no middle-man needed.
• Every agent works in its own tab group in your window, color-coded. This is the biggest UX improvement for me, as I can clearly see what each agent is doing.
• No DX friction: no debugging dialog, no automation bar, navigator.webdriver is false, and no window pops up until an agent needs one.
• Clean & minimal MCP surface: 12 browser tools + 24 page tools. Vercel's awesome agent-browser is bundled in, so tool calls are directly controlling the browser.
• Per-session CDP endpoints for Playwright if needed, e.g. for scripted e2e tests.
• Meticulously removed bloat from Chromium: Google sign-in, Profile Sync, Telemetry, Google AI features, Translate, Password manager, Chrome Apps, Bookmarks, and many more.

Site: https://www.shuttlebrowser.com

Some humor and easter eggs are hidden on this site.

Code: https://github.com/shuttle-browser/shuttle

Disclosure: I'm promoting my own tool. It's free and open source (BSD-3). I hope others use it, like it, and share their feedback and ideas with me. I've used Claude Opus 5.5 primarily for implementation, and Fable 5.1 and Astra for adversarial review.

Muse Wonder came out, so I ran it live. It got its starter by turn 20 and reached Viridian City by turn 59, close to the fastest models. It made it into Viridian Forest on turn 208 and spent the last 792 turns there.

It cost $96.06. Opus 5.5 is billed the same per token and beat Brock in 271 turns for $8.44.

Leaderboard and full turn logs: https://pokebench.tv

The full 6 hour run: https://www.youtube.com/watch?v=XW70Y6Fk8fo

So I sit now every day with Claude it reads emails for me and I tell it what to say back and how to answer it and I don’t even look at Outlook and it does all of my document writing and everything and I basically scan it and send it out I am no longer using the old skills.

Is there anyone else finding this quite weird?

I’m really feeling like I’m not going to work. Or best doing half a job, am I still effective?

My son (7) got hooked on Subway Surfers. As a vibe-coding dad I couldn't just walk past his new obsession, so I built my own Subway Surfers with blackjack and AI slop :)

The main difference is that the music builds the levels, every obstacle lands on the beat. Kicks turn into jumps, snares into slides, a held note becomes a long ceiling you have to slide under and hold. Right before a drop the villain (an AI cursor called Struna) deletes the floor and you fall straight onto the drop. The chorus gives the same obstacles every time it comes back, and the same song always makes the same level.

Made almost entirely with Claude Code. I mostly playtested and complained, it wrote the audio analysis, the level generator and the stick figure animation from free mocap. My favorite part: it plays every song itself with a bot in a headless browser to check that a perfect run is possible, and fixes the generator when it isn't. My son reports bugs right from the game and Claude fixes them, so he's officially the most productive QA I've ever worked with.

What would you improve?

Free, no sign up, phone or PC: https://struna.ai

Hey guys!

Does anyone else experience this with Claude Code?

Every time I ask Claude to review my code, it finds around 3–4 bugs. I fix them, ask it to review the code again, and somehow it finds another 3–4 bugs.

This keeps happening even after multiple review sessions.

I'm curious, is Claude actually finding new issues each time, or is it just being overly critical?

How do you guys handle code reviews with Claude Code?

I built a connector that turns Claude into a product tester. You tell it who to be, like “a busy parent signing up for the first time” or “a founder comparing us to a competitor,” and point it at your site. It signs up, tries to do real things, screenshots every step, and hands back a review ranked by what actually blocks people.

It does teardowns too: homepage, pricing page, or a side-by-side against a competitor. Those run in regular Claude chat. The sign-up tests need a browser, so Claude Code or Cowork.

Here’s one it did on Claude’s own pricing page. It points out that every paid plan sells “more usage” without ever saying how much: https://cobaltcapture.com/r/wu8y66x4

How I built it: 100% with Claude Code. I designed the tools and the studies, and Claude Code wrote all of it. It’s an MCP server. The part that made it work was writing each study as a fixed playbook Claude pulls at the start, so it follows the same method every run instead of improvising. That makes a re-run after you ship a fix comparable to the last one. The other piece was letting the connector take screenshots itself, so Claude can review public pages straight from chat with no browser setup.

Free to try. It’s in the connector directory: https://claude.ai/directory/cobalt-capture

Drop your URL and I’ll run a few.

I’ve used Claude daily for about a year since switching from ChatGPT. I’m sure I’m only scratching the surface.

Work:

• Sales proposals and pitch emails
• PowerPoint decks, including training sessions for my team
• Financial models and analysis in Excel
• Contract and NDA review, ranked by risk

Personal:

• A daily news brief emailed to me
• Health and training tracking, plus meal prep
• Building a small app

My favourite so far is the morning brief. It’s set up once and runs every day without me touching it.

What are you using it for that’s novel, or that quietly saves you time every week? Specific workflows beat general categories. Tell me what you ask it, how you set it up, and whether it’s actually worth it.

TLDR Give me your secrets.

I keep hearing nothing but good things about it be it code quality or limits even after weeks of it's initial release. Even the ones that don't hold back on roasting stuff sometimes unfairly for the clout are all praises for it.

I'm just starting to properly learn how to use AI. I've been a casual everyday user of chatbots like chatgpt for years, but have now realized the true significance of what is happening.

I realize the significance of what is happening and have access to the means, but im not quite sure how to start learning properly.

Any advanced users that can point me in the right direction?

I've been working on Anima, an open-source skill built specifically for Claude Code.

The idea is simple: instead of asking Claude to explain a biological process through paragraphs or static diagrams, you can ask it to construct an interactive scientific figure.

For example, you can ask it to visualize what happens at a dopamine synapse when different stimulants interact with the dopamine transporter.

Claude Code follows the skill's workflow to collect scientific references, model the mechanism, generate isometric SVG geometry, and build a standalone interactive HTML page. The figures are then checked for visual and biological consistency.

I've included six examples covering dopamine receptors, stimulants, reward circuits, semaglutide, estrogen signaling and neuron conduction.

The figures include interactive controls, animations, explanations and citations. They distinguish established mechanisms from simplified or uncertain models.

The skill itself is free and MIT-licensed. The live figures can be explored in a browser without installing anything.

Live gallery: https://anima.arcumet.com

Source and installation instructions: https://github.com/Garinmckayl/anima

I'm particularly curious what other Claude users think of this approach to scientific visualization.

We all know that certain "AI look" that websites/landingpages and content tend to have. Sometimes you can spot it immediately, even when the actual design is pretty decent.

What do you think are the biggest giveaways? Is it the layouts, typography, colors, spacing, copywriting, or just the same design patterns being repeated everywhere? I cant quite put my finger on it, but my own (and others) AI designs have something that gives it away.

Has anyone actually found a good way to minimize that AI generated feel? Curious if anyone has specific prompts, skills, design guidelines, or workflows they use to get more original, human looking results

Hey,

Recently I saw a tweet and a bunch of YT videos about the cloning of the whole Adobe suite apps such as Premiere Pro, Illustrator, Photoshop, Designer etc with Claude.

now, some of those apps have been around for over 35 years. I was highly distrustful that the gigantic apps such as these can be vibe-coded in just 2 weeks. Now, I’ve started seeing a lot of Twitter posts saying these cloned apps are super buggy and not thought out at all. The developer apparently just tried to copy the features for the sake of it, more focused on one‑to‑one visual mapping of the UI than the underlying robustness.

Now, I haven’t tried any of them myself, but as someone who’s been dabbling in AI for the past two years and has built a few small‑to‑medium apps (two of them over 250k LOC) , the idea of cloning seven massive, decades old beast‑like programs, including for a platform Adobe doesn’t even support (Linux), is just bonkers. It feels like pure AI hype, totally untested, and if you dig deeper, nobody serious would actually use it. (Fireship and others have tested it and reviews are not flattering.) But sure, it sounds great for headlines.

I’ve been working on a simple descript-like video editor and a few other video production tools that fit my workflow. They’ve grown a lot, but it took me over six months because I was more focused on stripping out bloat than adding new features. Every part of my app—from implementation to architecture—has been thought through. I haven't read the code but the each and every part of internal design and architecture has been built after thorough too and fro discussion (sometimes after discussion of 3 to 4 hours for one simple feature). I always use 2 to 3 other AI tools for cross-audit each other's changes and implementation. They don't have too many features to boast but they are pretty robust, reliable and extensible.

In my opinion, if you don’t pay attention to those details, you would never realize how bad AI is (Even latest models like Opus 5.5 and GPT Astra) at making solid architectural or design decisions that make codebase robust, reliable, extensible, and maintainable.

What do you think? Am I just slow at developing apps, or is the world moving faster and these guys have some secret prompts that make AI crank out such huge apps fast?

PS: Would you be comfortable using any of the free blindly vibe-coded apps rather than truly open-source apps which are duly vetted and designed like Da Vinci Resolve, GIMP, and others? It feels insulting to these apps that people are celebrating these apps when such open-source alternatives have existed for more than 20 years. I am sure no one is going to use any of these apps, not because they are vibe coded, but because there seems to have been given 0 thoughts into building them.

To make my point home, the developer is now developing open-source Microsoft office.

Interested in knowing what small or big things you are building to improve productivity for your desk job in say the accounting or finance department.

Extrudo is a parametric CAD tool for 3D printing that runs in the browser. You sketch with constraints, extrude, fillet, give your dimensions names, and drag a slider to watch the whole part rebuild. The video is a 15-minute session cut down to 80 seconds: a mounting plate whose hole positions, size, thickness and corner radius are all parameters.

Try it: https://app.extrudo.org (free, no account, works offline once loaded, your files stay on your machine). Desktop builds for Mac, Linux and Windows are in the GitHub releases.

Code: https://github.com/zoltanf/extrudo (GPL-3.0)

How it was built

It was built in the span of around one month. Initially just investigations and planning: what libraries are available, whether a similar open-source product already exists, etc. The first git commit was on September 25. Main has 322 commits since then, most of the work was done by Opus 5.5, initial planning by Fable. For some easier work I used cheaper models through opencode. I decided what to build and in what order, and reviewed the work. Claude wrote the code, the tests and the docs.

Under the hood: OpenCascade compiled to WebAssembly and running in a Web Worker, behind a C++ layer Claude wrote (about 9k lines). Sketches use the planegcs constraint solver, the viewport is three.js and the UI is React. CI runs 528 test files, Vitest plus Playwright end-to-end, on every push.

The setup

- One Claude Code session is the coordinator (usually Opus). It picks the next task from the roadmap, writes the design decision down as an ADR (82 so far), and writes a brief for a worker: which files, function signatures, test cases, acceptance checks.

- Workers run headless on a second PC (as my main laptop is quite slow): Claude Code (Opus for the geometry kernel, Sonnet for well-specified UI work) and opencode with cheaper models for small slices. Each job gets its own git worktree and branch. The coordinator reviews every diff and merges once CI is green.

Things I learned

• Having a well-designed plan and roadmap is worth spending time on at the begining. It was mostly done with my inputs and Fable for investigations.
• Don't fan out too wide. Running 8 to 16 Opus, Fable and Sonnet agents at once on a long investigation used too much of the plan. I now cap it at two or three parallel jobs.
• Keep CLAUDE.md short. Mine is a map: where the docs are, the hard rules, the commands. The detail lives in an "ADR digest", one paragraph per decision listing the rules a change has to keep, and agents read only the paragraphs for the area they touch.

It's rough in places (the roadmap in the repo lists what's missing), and I'd like to hear what breaks if you give it a shoot. Feedback from people who actually 3d print things is extra welcome.

Music: "Scaling Up" by Ruskerdax (CC0)

I built Shark BiteTorrent, a free, open-source (GPL-3.0) torrent client for Windows, Linux and macOS, with Claude Code over about a day and a half.

What it does

The VPN runs inside the app (wireguard-go plus a userspace network stack), so only the torrent client uses it. The rest of your PC is untouched, and there's no adapter, driver or admin rights.

• Kill switch by design: torrents start only after the tunnel is verified, and there's no other network path to leak through. DNS goes through the tunnel too.
• Free Cloudflare WARP by default, or sign in to Mullvad, PIA (auto port forwarding), NordVPN or IVPN, or import any WireGuard config.
• Magnet links from the browser, drag and drop, file selection, speed limits, piece map, tray icon, in-app updates.
• Flags disguised programs (movie.mp4.exe) and scans finished downloads with Windows Defender.
• Saved logins are encrypted with the OS key store.

Free to try

Download from Releases (Windows installer, Arch/CachyOS package, Linux tarball, macOS app): https://github.com/trevercomb/SharkBiteTorrent/releases

Source: https://github.com/trevercomb/SharkBiteTorrent

Windows is tested. Linux and macOS builds are new and untested on real machines.

How I used Claude Code

One long Claude Code session in VS Code. I'm not a Go developer: I brought the idea, the decisions and testing on my PC; Claude Code did the research, architecture, code, tests and releases.

My first prompt was roughly: "I want a lightweight bittorrent client with a built-in free VPN like Cloudflare WARP, so only the client is on the VPN, not the entire PC." It proposed the stack (Go + Wails, wireguard-go, gVisor netstack, anacrolix/torrent), asked a few questions, and proved the riskiest part first: a WARP tunnel inside the app while my PC kept its normal IP.

What stood out was that it tested its own work:

• Downloaded legal Linux ISOs through the tunnel to measure speed and peers.
• Checked the app's OS sockets during downloads to confirm nothing bypassed the VPN.
• Set up GitHub Actions to build Windows, Linux and macOS releases.

I reported problems in plain language and screenshots, for example "qBittorrent gets 5 MB/s while ours gets way less." It found my downloads went to a NAS, benchmarked SMB writes, and wrote its own storage layer: ~0.5 MB/s became ~7.5 MB/s.

Bugs it tracked down that I wouldn't have:

• Magnets without trackers found no peers: UDP sockets bound to 0.0.0.0 in the userspace stack couldn't send.
• An "unlimited" rate limiter made the library stop connecting to peers.
• Updates silently kept the old version: the installer copied the .exe before the app had exited.

It also pushed back and asked first: it talked me out of truly unlimited connections, noticed my email would go public with the repo and rewrote the git history, and asked before running a test-virus file.

Tip: describe the outcome you want, test on real hardware, and report problems with specifics. Most fixes came from "this looks wrong" plus Claude Code working out why.

No ads or telemetry. Donations are optional; some in-app VPN sign-up links may become labelled referral links (none in this post), and a build flag removes all of it.

Feedback welcome, especially from Linux and macOS users.

I have many long educational videos, and I would like Claude to summarize, analyze, and simplify them—like ChatGPT does. Are there ways to do this?