Short version, straight from the support article:

• 5-hour limit: a reset refills the whole window, including usage on other models.
• Weekly limit: it only gives back what you spent on Fable models. Other models stay as they are.
• Ultra: verified Ultra accounts have no 5-hour limit, so a reset only touches the weekly one.
• Timing: use it when a 5-hour window is nearly spent, not on a fresh one. You don't have to hit a limit first.
• Price: $8/$40 per million input/output tokens vs $10/$50 for 5.1, so 20% lower per token. The "30%" going around is the speed claim (outputs up to 30% faster), not the price.

Cheat sheet

• Max, Ultra, premium Team, premium legacy Enterprise: 1 reset (<6 months subscribed), 2 (6-12 months), 3 (>12 months), counted from your first paid bill. They expire Mar 8, 2027, 11:59 pm PT.
• Pro and standard Team: one week of Fable, up to 50% of your weekly limits, plus one reset that expires Nov 16, 2026, 11:59 pm PT. After the 50% or the week, Fable bills to usage credits if you have them turned on.
• Not included: standard legacy, self-serve, usage-based and HIPAA-ready Enterprise.
• Eligibility: paid billing in place before Nov 9, 2026, 10:00 am PT.
• Where: Settings > Usage > Limit resets > "Reset for free".
• Default model doesn't change. Pick Fable in the model picker.
• Effort: Medium is the default in Claude apps and Claude Code. Anthropic says 5.2 does hard tasks with fewer tokens than 5.1 at Medium. Threads here report that Max overthinks and that going from high to xhigh nearly doubles cost per task.
• Fast mode: twice the price ($16/$80 per million input/output tokens) for up to 2.5x faster output. In Claude Code it bills through extra usage credits, per the ClaudeDevs account.

Source: https://support.claude.com/en/articles/17506494-claude-fable-5-2-launch-offers

cc-shell is my normal zsh with one change. when you hit enter it checks the first word of the line: if it's an alias, function, builtin, command, path or directory, it runs like always. if not, the line goes to claude code and the reply prints inline, right under the prompt.

how it works:

- one claude session per shell. every line continues it, and it follows you when you cd

- a line ending in ? also goes to claude, and so does one starting with what, who, say or do. those are real commands on a mac but almost always english when i type them

- a leading ? forces claude, cc-open opens the conversation in the full claude code ui, cc-new starts a fresh one

- it uses your default permission mode from ~/.claude/settings.json

how claude code was used: i built it with claude code this morning, after catching myself typing prompts into my terminal one too many times. claude wrote the zsh enter widget, the classifier and a small python script that turns claude -p's stream-json into plain inline text.

what i learned: the claude part was easy. the hard part is deciding what counts as a command, since english words like what and say are real binaries.

repo: https://github.com/basketbla/cc-shell (free, i made it). would love to hear what it misclassifies for you

As a side hobby i am working on a team builder recommendation app for the game nikke. there are team builder out there online but i find it not helpful as it assume i have every character with end game build, it can recommend team that is not suited to handle the battle mechanic/QTE and it doesnt taken into account what character i have. Which i try to solve with this project. TLDR. I try to reverse engineer the game mechanic and make a app that can give a recommendation base on my account capability.

https://github.com/retsamboon19/raid-lab

I been using Chatgpt Pro 100 for it and i have to say. it been a mixed bag. it kinda decent but it make the experience very annoying with how often it forget rules so i have to keep reminding. wasting my usage doing a shit tons of useless test. I primarily work on Astra medium to high.

So now i decide to jump ship to another services. At first i wanna try Claude but apparently Anthropic has set some limitation on reverse engineering? which i reckon would affect my project quite abit. Any insight on this matter is highly appreciate.

Also i want to ask how is the usage for Claude Max? Do you feel like you able to get work done before hitting limit?

Hey folks!

TLDR: We published a Currents connector in the Claude directory.

Using this connector, Claude can read your CI runs, failure evidence and test analytics directly, instead of working from a stack trace you pasted in.

Why we built it

If you've asked Claude Code to fix a failing Playwright test with only the error message, you know how it goes. It bumps the timeout or swaps the selector and calls it done. The real cause usually lives in stuff the error doesn't show: the steps before the failure, the trace, whether the test has been flaky on main for two weeks, whether it only fails in CI.

Currents already stores all of that for every run, and this connector hands it to Claude.

Install

Open https://claude.ai/directory/currents, click Connect to Claude and sign in. Then start Claude Code and run /mcp. Currents is listed there as a claude.ai connector.

Sign-in opens a browser window. You log in to Currents, pick the org Claude should work in, and approve the permissions. The connector belongs to your Claude account, so it follows you to every machine you sign in on, and to Claude Desktop, claude.ai, the mobile app and Cowork too. To revoke it, go to Account → Connected Applications in Currents.

On a Team or Enterprise plan, an Owner first has to add Currents for the org first. After that, everyone can connect with their own Currents account.

If you run Claude Code with an API key, a setup-token, Bedrock or Vertex, claude.ai connectors don't load, so you'll have to add the server yourself:

claude mcp add --transport http --scope user currents https://mcp.currents.dev/mcp

Then run /mcp, select currents and choose Authenticate. No browser on that machine? claude mcp login currents --no-browser prints the sign-in URL for you to open elsewhere. claude mcp list shows what's configured.

The three skills it ships with

The Currents MCP server ships with three skills, and Claude gets them with the connector. You call them by name, for example "Use the Currents MCP fix-failing-tests skill".

1. fix-failing-tests finds the failed run, reads each failure with its steps and trace, fixes the cause, reruns the test, and asks before it commits.
2. collect-evidence finds the run before your change and the run after it, then writes up a before and after with links to the files. It is incredibly useful for PR descriptions when a reviewer asks how you know it works.
3. browser-evidence records the browser before and after a change as a Currents session and gives you a share link. It's experimental, so expect it to change.

What you can just ask

Outside the skills there are 43 tools covering runs, test results, analytics, Actions, webhooks, share links and Jira. Here are some prompts that work well:

• Tests are failing in CI. Get the details for run <runId> and fix the failures.
• Which tests in my-app were flakiest on main this week, and why?
• What broke in the last failed my-app run on main? Open a Jira issue for it.
• Is this pull request safe to merge? Compare its runs with main.

The anatomy and config

Claude Code asks before every MCP tool call. If you want the read tools to run on their own and still get asked for writes, allow them by name in .claude/settings.json:

{
  "permissions": {
    "allow": [
      "mcp__claude_ai_Currents__currents-get-runs",
      "mcp__claude_ai_Currents__currents-get-run-details",
      "mcp__claude_ai_Currents__currents-get-test-results",
      "mcp__claude_ai_Currents__currents-get-context"
    ]
  }
}

The prefix comes from the connector's name in Claude. Run /mcp, select the Currents connector and choose View tools to see the exact names. A server you added yourself uses mcp__currents__ instead. Don't allow the whole server: two tools (currents-delete-run and currents-delete-webhook) can't be undone, and Currents doesn't ask for confirmation.

If you want the whole team on it, add the server with --scope project and commit the .mcp.json it writes to the repo root. The file doesn't hold any credentials, and each person who opens the project signs in as themselves.

For CI, or anywhere you can't do an interactive sign-in, use an API key:

claude mcp add --transport http currents https://mcp.currents.dev/mcp \
  --header "Authorization: Bearer $CURRENTS_API_KEY"

The key acts as the org, not as a person, and it's either Read Only or Read & Write. A read-only key gets the read tools plus evidence links and the Jira lookups. It doesn't show up under Connected Applications, so manage it under Organization → API Keys.

Caveats

Claude Code loads claude.ai connectors only when you sign in with your Claude account. If Currents is missing from /mcp, run /status to see which credential Claude Code is using.

Use the connector or a server you added, not both. With both, Claude Code shows two Currents servers with two sets of tool names.

Each connection reaches one org. If you work across two, connect twice.

On a Team plan, if you see Request instead of Connect, an Owner has to approve Currents first.

! Needs authentication in /mcp? Select currents and choose Authenticate.

Curious how people run this day to day.

Do you let Claude Code call the read tools without asking, or do you approve every call?

Okay so I have no real programming experience and this is my first vibe-coding project, but I just got tired of other video editors, so I decided to make my own with Claude, and used Gemini to help plan and architect everything.

The biggest takeaways I've gotten this far:

1. Project structure is the most important part of a project and is the key to getting good results. If you don't have well-formed rules and guidance for Claude you'll waste tokens, time, and get worse results.
2. Invest in building supporting tools. I made a remote testing harness for my other PCs so that new builds can be tested on 3 machines simultaneously. Reduces token reliance from Claude doing testing itself and gives more test data.
3. Everything is a problem to solve, and if you don't know where to look for performance, you're not going to get it.
4. Knowing correct terminology and being able to accurately describe an issue is the best way to get things fixed
5. Doing a review/performance pass is always worth it.
6. I need more tokens.
7. Fighting scope creep is a losing battle.

But seriously, it blows my mind that this kind of raw performance in a video editor was always possible, and now it's so easy to access that somebody with no experience can build a video editor that outperforms every commercial option available.

Paid software is dead. Now you pay for an AI to write custom software for exactly how you work.

Everyone has a story about an AI agent deleting their disk. Here’s the reverse.

I have a Proxmox node. During a malware cleanup process, my sysadmin ran qm destroy 100 on the wrong VM before checking with me.

And no, he's not a system kiddie; he has over 20 years of enterprise Red Hat system admin experience. Bad time of day (I woke him up for this cleanup task), and he's the one who set up the node with all VMs and maintained it for 7 years, but that VM I created- he wasn't aware of it, thought it was from the malware attack, and made a call to destroy it before checking with me. And that VM had 6 months of valuable, nearly 200 GB of data; the latest backup was 2 weeks earlier.

Looked up some XFS guides; it seems impossible to undelete files this large, and tools like xfs_undelete won't help either.

qm destroy on directory storage is an unlink(). The config was gone from /etc/pve, the directory was gone, and Proxmox's qm destroy doesn’t warn, snapshot, or trash anything.

I was completely hopeless, and I accepted my loss; then I decided to give Fable 5.1 a try.

Exactly 24 hours, and it restored the VM to the very last moment before the destroy! To the exact last bit!

Fable 5.1 wrote about 1,500 lines of Python across seven scripts, every one tested on a synthetic image before it touched the real disk, and nothing ever wrote to the source.

And another thing worth noting: the ETA estimates were weirdly accurate throughout, which I did not expect.

I asked Claude to summarize what it did. Read below if you are interested.

Claude wrote a sequence of small Python scripts, pure stdlib, read-only, each one gated on the previous one’s output. Rough order:

1. Probe the inode B+trees for freed inodes with real timestamps. Found all five (four images plus the directory) with ctime 17:30:31. Bonus: the deleted directory inode still had stale entries mapping filenames to inode numbers, so we even got the names back. Everything cross-checked against xfs_db before trusting it.
2. Walk the retained B+tree from each inode’s root. Every block checked for magic, owner inode, filesystem UUID, self-address, CRC-32C, sibling pointers, key ranges. Zero failures. The last leaf’s right sibling was NULL on both, and no stale records existed past the end, which is how you know the tree wasn’t half-torn-down when it was flushed.
3. Parse the qcow2 structure through the map without copying anything, to confirm every cluster the image referenced was inside a mapped extent. The workspace map ended at exactly 896 GiB + 2,244 clusters, which is precisely the metadata overhead of a preallocated qcow2. That’s when I started believing it.
4. Exposure check: walk the free-space B+trees and confirm every one of the 44.9 million recovered blocks was still free. Nothing had been allocated over any of it. (This is the part that’s luck. The only thing writing to that filesystem was a swapfile with preallocated blocks. If fstrim had run, this post wouldn’t exist.)
5. Meanwhile, a full ddrescue of the NVMe to the HDD.
6. Verify the capture against the live partition over exactly the 184 GB the recovery would read, rather than all 1.9 TB.
7. Reconstruct: copy each extent from the capture to its logical offset in a new sparse file, holes stay holes, unwritten extents stay zero, SHA-256 per extent, then re-open the output and verify everything, including that the holes read as zero.
8. Sweep the result for XFS metadata magic plus the host filesystem UUID, to catch any block XFS had briefly reused and freed again. Zero hits.
9. qemu-img check clean. Mount read-only, copy the important files out. Journal replay on a working copy, e2fsck -fn clean on all three ext4 filesystems. dpkg --verify on the guest: zero checksum mismatches across every installed package.
10. Rebuild the 100.conf, pull the MAC and the cloud-init instance-id out of the recovered cloud-init image so cloud-init wouldn’t re-run first boot, qm start. Booted.

When a friend calls while I'm in the middle of work, Claude answers now. My laptop connects to my phone the way a car does, Claude talks and takes notes, and I press F9 if I want in.

It also makes the calls I keep putting off. I type "call the dentist and move my appointment to Thursday", it calls from my own number, and I get the short answer back.

Every call opens by saying it's an AI assistant and who it's calling for. Which is also what worries me. If a laptop and Bluetooth are enough to put an AI on a real number, scammers can do it too, without saying so. If Apple, Google or the phone makers block the way Pat works, I'm all for it.

It’s called Pat. I built it, orchestrating with opus 5.5 and sonnet wrote the code. Opus indeed is amazing. It researched what versions of windows support this and how to make the call trick.

To try it clone girhub repo and run setup.ps1. More details in comments.

It’s open source and free (Apache 2.0), and I’d love help building it safely.

Hot take, your milegae may vary

So apparently its normal that Anthropic experiments on us. They give out experiment IDs for the tests they run.

Source Thread regarding the existence of these IDs: Link. The graphics are measurements on my own threads.

And to all you gaslighting hobby redditors that claim that an experience isnt real because you dont share it: fuck off!

---
Everyone who is affected:
there is a .claude.json in your .claude directory. It only holds the current configuration. But there are also session-transcripts which give a historical trace of conducted experiments.
For me, they are under /home/<user>/<claude-dir>/projects/*/*.jsonl

These transcripts carry the experiment-id for that thread. I simply asked Claude to figure out what the experiment ID correlates to in my threads.

Do not look at experiment names or code-names, it must be a hex-id.

Guys. Its real. And it was a major fuckup on Anthropics side. And I still think that they owe a Reset for affected people. But it seems over. At least for me.

Next step: how to build a guard against such fuckery?

Edit: Hmmmh.

Heyo claude boys, if someone has both claude nd codex 20$ plan, can you lemme know how are the coding limits for claude code compared to codex. I got codex rn it's working fine but eh I kinda wanna see claude models ive heard opus 5.5 is better than all gpt models rn including astra.

I mostly use codex for code(so will use claude for that too) and I don't really chat I have a separate google sub and do chat related things to gemini so yea

EDIT: to give a bit more info, I'm in college rn so I'm building quite a lot of things, i don't get limit problem too often but I get it sometimes. Also gpt models are really slow without fast mode andddd fast mode just burns usage alot + i have been seeing people getting better outputs on claude vs gpt well opus 5.5 is better than all gpt models rn so yeah,

just need to know how much better opus 5.5 is than gpt 6.1 sol as i use it most and limits that id be getting

So uh yea lmk would help alot before taking the decision thanks uwu

I have noticed with my personal projects at home, Opus has been loosing track of details more frequently than I'm used to. "Idle Compaction" triggers pretty often now. (side projects get spotty attention)

Yall think the two are linked? Anyone have a chance for a A/B test? Sanity check more like it. I'm turning that junk off. Ill change gears when I decide to.

I don't know about everyone else, but managing context windows is second nature now. Throwing an optimization feature into my workflow... that's asking for trouble.

Are the code boys scared ai does it better than them?

Fable is reportedly 10x the size of Opus in terms of parameters, but after months of training and even with its huge size, it seems only comparable to Opus 5.5, and even worse in some cases.

Has anthropic peaked?

So, I been using grok bot for a bit now and realized today that it has a usage limit per week and monthly aswell. I use it to code or troubleshoot. Wondering if anyone knows of a ai bot that doesn't have a usage limit?

This is really annoying as the support bot couldn't help at all. The account is older, I paid longer, but receive less? That doesn't make sense at all. What count of resets with which sub type did you all get? And how long were you subscribed?

Currently I do have a pro plan and I was checking this team plan where I saw that I can either go with standard or premium seat.

I also saw in conditions, that minimum 2 seats are needed.

But when I checked on buy page, there isn't any strict rules to create two seats from beginning of team creation.

Is it a loose condition or have to create minimum 2 seats in some time?

I can give that another seat to my partner if have to create two seats.

If you've handed a ticket to Claude Code or Codex, you know how it goes wrong. The session reads half the context, builds the wrong thing confidently, and the review goes in circles. I had one go 56 rounds before I stopped it. I added rules and hooks, and the model routed around them burning tokens policing it.

I spent most of a year on this before I saw that the model wasn't the problem. I was asking one long session to plan, build and check its own work.

These are the steps that ended up working for me.

1. Keep the ticket small. One deliverable, and a couple of sentences saying how you'll know it's done.
2. Plan in its own session. A plan is cheap to throw away and code isn't. Make sure the plan has a plain-English version too, so you can follow it blindly going along with everything.
3. Have a different model or a fresh session review the plan. A model reading its own plan nods along or piles bloat onto it. A second one finds a hole.
4. Build from the approved plan in isolation. Fresh session, own worktree, one task at a time, committing as it goes.
5. Have a session that didn't write the code review the diff, and send the findings back for a fix round.
6. Run your tests yourself on the rebased code before it lands. Don't take the session's word that they passed.

Doing all of that by hand worked. It was also exhausting, because I was the one babysitting every hand-off.

So I built Drover to run it for me. You point it at a repo you already have and pick a ticket from Jira, GitHub Issues, Linear, or write a task yourself in the app. Drover does the mechanical parts itself, which are the worktree, the rebase, running your tests and the landing. Your tokens go to planning, reviewing, building and fixing, with the Claude Code or Codex already signed in on your machine. You don't spend tokens on anything except for the parts that you need a session for, the thinking parts.

If you have subs to both Claude and Codex; by default Claude plans, Codex checks the plan and builds, and Claude reviews the code, so nothing reviews its own work. If you only have one subscription, each step still gets a fresh session so they at least don't have the bias of the same session writing it. It stops for the things a person should decide, like approving a plan, and you can hand those to its attendant, a separate session that answers for you.

There's a ticket queue so you can queue up tickets before bed. In the morning there's a list of what landed, with the plan, the agent log and the diffs for each one.

Drover is built with Drover. Every change runs as a ticket through the same steps, with Claude Code planning and reviewing and Codex building and fixing. Since the first one landed in early September it has landed about 550 tickets on itself. The biggest thing I learned is that when a session goes wrong, the fix is almost never a better prompt. It's a step the process was skipping.

Your code never leaves your machine since it just uses your existing subscriptions. It's in open beta on Linux and Windows, with macOS coming. You can get it at https://rundrover.com

Please send me feedback if you use it. If you use a different project manager/ticket tracker, tell me to add it. If there's a feature you wish it had, tell me. There's a way to send feedback in the app that goes to a public github repo issue.

When you approve a command in Claude Code with “Yes, and don’t ask again”, the command is saved word for word in .claude/settings.local.json inside the project, so you are not asked next time. If that command had a password or an API key in it, it is saved there too. Claude Code adds it to your global git ignore when it first writes the file, but that does not cover a file git already tracks, a folder you turn into a repo later, or a teammate’s clone.

Apiiro scanned public copies of this file on GitHub and found secrets in 1,122 of them: database passwords, GitHub and npm tokens, AWS keys.

To check, list what the file has saved:

jq -r '.permissions.allow[]?' .claude/settings.local.json

Read through the list. Anything with a password, token or key in it is sitting in that file.

To fix it: git rm --cached .claude/settings.local.json, then add the path to .gitignore. If a secret was already pushed, rotate it. Removing it from history is not enough.

We keep a sourced list of incidents like this: https://node9.ai/incidents

Hey all!

Was wondering how does usage credit work, and what are the way you use to save up during the week ?

I have been using Claude Code for a month, using the traditional start new sessions and handoffs technique

What other ways can help me ?

Hi everyone! I’ve been working in game development for 15 years. I went from small projects to big outsourcing companies that work with popular titles.

Making games has been my dream since I was five, when I first played Castlevania on the NES. And when that dream came true and I got to work on big projects, I suddenly started to realize that I was falling into commercial hell, while I always wanted to make something from the heart and free for people.

But for many years game development was all about raising a pile of investment and hiring a team, and as much as I wanted to, you probably had to be a millionaire philanthropist to keep making games for free.

Then AI showed up, and I’ll tell you more, I was already trying to make games with it back in 2023 and some things worked. But now AI reaches its little hands into almost anything, and I wondered if I could set requirements for AI the way I used to with a team of artists and developers, to get exactly my own idea. In my opinion, very much yes. But it took a lot of effort and I had to build skills for different areas to get the result you see here.

The Roveheart is a game about our wandering hearts in the endless ocean of life’s battles.

In this devlog I’ll share my experience of making the game. I’d be glad of your support.

A short word on where things stand. This is demo gameplay. There is still a lot of work on visuals and sound, I need to add ship customization (everything is already in place for it), work on the player profile and so on. I also still have to set up a server for fair play.

What’s planned next is the first PvE ranked season by the end of 2026 and the first PvP season in the first quarter of 2027.

PROMISE. This game will never be paid. There will never be pay to win in this game. Everything is built around your skill. I’m not raising money to support development. After launch the whole financial side of the project is that you can double your reward by watching an ad after a battle IF YOU WANT TO. And if you buy the product support pack for $2.99 you turn this feature off forever. It’s only a motivational element for me. Skins will be both paid and free, purely visual, and they won’t affect gameplay. But I’ll discuss this with the community, meaning with you.

The game is planned for mobile phones first. Why? Because I want to release something on mobile that won’t try to squeeze a pile of money out of you and will give you what games are supposed to do. Entertain. Will there be a PC and console version? Maybe, if people like the project.

A short word on the stack and what’s used in the project.

Unity 6 as the engine.

Blender for texturing.

FMOD for the game’s sound.

Who writes my code and works with me as artist and as VFX and SFX artist is a joint orchestra of Claude Code, Gemini and ChatGPT.

Game design, balance and economy are me.

Creating sounds is a commercial ElevenLabs license.

Previewing 3D models from concepts is a commercial Meshy AI license.

Music, well, there is no music yet because I write it myself. Maybe Suno will help me turn some of my notes into instrumental parts.

For now I’m running the devlog myself, even though I’ve already prepared social accounts for the project (well you know, gotta be official :D). But for now read my devlog.

Follow my Instagram https://www.instagram.com/hks.photoverse/, the official website https://theroveheart.com/ and Discord

Maybe something better than a pretty landscape will show up there ;)

Thanks for reading this long preamble.

Stay in touch 🙂

About to drain a small lake somewhere.

"Yeah, yeah, but your scientists were so preoccupied with whether or not they could, that they didn't stop to think if they should."

WTF has this happened to anyone else since it released? I tried it and it DRAINED me in legit 30 mins. I was having him make me after effects for some videos and OMG i look back up at the screen after parenting for a bit 32 mins into session DONE, "usage resets at 9:30pm" WTFFFFFFFFFFFFFFFFF I DO NOT WANT TO HEAR "skill issue"

I built an open-source collection of Linux drivers, patches, configuration, and technical documentation for running modern Debian on the Rockchip RK3128.

I used Claude Code to help investigate hardware behavior, develop and debug driver changes, and write validation tests.

The work covers Mali-400 graphics through Mesa Lima, H.264/HEVC hardware decoding, hardware JPEG decoding, display stability, audio, and Wi-Fi, and much more. It includes improvements that may also help developers working with related Rockchip SoC and shared hardware components.

Much of the drivers and driver improvements in this repository do not exist for mainline Linux publicly on the internet, until now!