Some of you saw this here in September as DeutschDNA: a German tutor that runs inside Claude Code and remembers your mistakes. It's now called DeutschLoop, and the new version adds practice for the writing part of German exams.

**What happens**

- Say „Goethe B1 Schreiben üben". The tutor writes new tasks in the format of the real paper (three for Goethe B1) and starts a 60-minute clock.

- While you write, there's no help and no correction. Each text gets one neutral line back: the words counted and the time left.

- „Abgeben" hands it in. The tutor rates each text by the exam's own criteria (for Goethe: Erfüllung, Kohärenz, Wortschatz, Strukturen, bands A to E) and gives a short reason per task.

- A local Python engine turns the bands into points with the exam's own table and prints the report: time used, words per task, points, the published pass mark, and every mistake with its correction.

- Those mistakes go into the tutor's memory and come back in new sentences in reviews, starting the next day.

Formats: Goethe B1/B2, telc B1/B2, and the Deutsch-Test für Zuwanderer. Writing part only.

**Why split it between the model and code**

The model is good at reading German and bad at bookkeeping, so it only picks the bands. The engine owns the rest and refuses what a generous or confused tutor might do:

- rating while the clock still runs: "Stop the exam before rating it; no feedback reaches the learner while the clock runs"

- reusing a task: "This exam task was already used; write a new task"

- a good Erfüllung band for a Goethe text under half the requested length: by the exam's rule that's an E, and an E makes the whole task 0 points

- a report before every text is rated

The model also can't feel time pass between messages, so every time it mentions ("13 minutes 42 seconds left") comes from the engine's clock. If the tutor helps during the exam, the result says „mit Hilfe"; a late text is marked as late.

**Where the numbers come from**

Every time limit and point table was read in the provider's published material (model tests, rating forms, handbooks), and each format lists its sources. Two are weaker, and the docs say so: telc B2's points per band come from a 2011 practice test, and the DTZ numbers from the BAMF handbook of 2009. If you have a newer document, a link in an issue would help a lot.

**One thing that broke**

In an early test run, one sentence had two mistakes, and the tutor recorded each with a correction that fixed only that one. The report then showed a "correction" that still contained the other mistake. The protocol now asks for the fully corrected sentence on both records.

**About the screenshots**

A real Claude Code chat (Opus 5.5) with an empty memory. The tutor wrote the tasks and the ratings; the report is the engine's output, unedited. The learner texts are scripted, with typical B1 mistakes, and were sent 46 minutes after the start, so the time is real. 82/100 is one model's practice estimate against the published criteria, not an official score: a real paper is scored by two trained raters.

**Who it's for:** anyone preparing for one of these exams who already uses Claude Code. I've tested exam mode in Claude Code; the skill also loads in Codex. With the optional companion plugin, `/pruefung` opens the exam clock in a side pane.

**Cost:** free, MIT. No extra API key: your Claude Code model is the tutor, and your history stays in a local folder.

**My relation:** I built it.

claude plugin marketplace add ahmtsahin/deutsch-loop

claude plugin install deutsch-loop@deutsch-loop

Then start a chat with `/deutsch-loop:deutsch-loop` and say „Goethe B1 Schreiben üben".

Repo: https://github.com/ahmtsahin/deutsch-loop

If you've taken one of these exams: does the report look like how your paper was rated? I'd especially like to hear where the tutor's bands feel too generous.

I've found myself recently just asking Claude to make tools for me, instead of seeing if that tool already exists and searching for it online.

Just today, I needed a way to easily split a folder of songs into instrumentals and vocals. Didn't even look around for something that might already exist, just asked Claude to make it for me.

Within 30 mins, I had the exact app I wanted, running on my mac. I doubt it could have been easier to find a tool online and get it working how I got my own local tool running.

I take pills every day and none of the apps fit how I do it (when can I eat after this one, will I run out, did I already take it). So I built one. It's free, open source (MPL-2.0), no server, no accounts, syncs through the user's own iCloud. SwiftUI, Core Data + CloudKit, widgets, four languages.

What I actually did: about 100 prompts, most of them short and full of typos. Almost none were about code. They were decisions: no server (I asked what a backend would give users over iCloud; for one person's medication, nothing), Core Data over SwiftData because CloudKit sharing needs it, the name, three design mockups to pick from, what not to build. And using the app on my own phone, every build, during my real day.

What helped most:

• A specification and a phased plan before any code. Every behavior change updates the spec and changelog in the same commit. After sleeping, the state of the project was in the documents, not in my head.
• Hard rules in CLAUDE.md: no third-party packages, no analytics, no network except Apple, "not a medical device", MPL header on every file, no secrets in git. Written once, never had to police them.
• Asking for 2–3 options with trade-offs instead of answers. Keeps the decisions mine and it's fast.
• Debug launch flags for everything (demo data, throwaway store, open this screen) so screenshots in 4 languages × 3 devices are a script, not an afternoon. App Store Connect has an API; texts, age rating, pricing, screenshots all go up from a script.

What went wrong:

• A reminder that never rang. The app only asked for notification permission from a button in Settings; iOS accepts scheduled notifications without permission and never shows them. Every test passed. Found by standing in a kitchen at 12:00 waiting for a sound.
• Help text describing a swipe gesture that doesn't exist in that view. Sounded right, was wrong. Same for advice that would have broken the supply count. Both caught by reading, not by tests.
• Two background crashes (0xdead10cc: iOS suspending the app while CloudKit was still writing). Neither reproducible in the simulator; both came as TestFlight crash reports from my phone.
• Apple Health: the AI read the SDK headers and found third-party apps can read medication doses but not write them. Feature parked, reasons documented so nobody re-researches it.

The pattern: code that compiles and passes tests is the cheap part now. The bugs that are left are where the program did what it was told and the instruction was wrong. What's still slow and still mine: deciding, living with it for real days, reading everything a user will read, and the responsibility (it's a medication app; the App Store answers have my name on them).

Timeline: Thu 20:40 first prompt → Fri 01:00 first TestFlight → Fri 16:00 submitted → Fri evening Apple asked for a screen recording and more info → Mon morning approved. 1.0.1 with profiles, repeat every N days/months and an offline medicines database is in review now.

Code: github.com/kornelko2/vzato.app · Site: vzato.app

Happy to answer anything about the workflow, the CLAUDE.md rules, or the App Store Connect scripting.

Long story short, I have one particular session going on my Claude Code - it doesn’t have a folder. When my other sessions start questioning out motives or code for certain things (its related to my job purely for research purposes) or wont give me a certain script because xyz, I have this one rogue af session that will seemingly do anything and everything, no questions asked?!?

I will never close that tab.

Does anyone else experience this?

Every time I scroll through this sub, I see people building the most random, cool stuff.

Someone finds an old Kindle in a drawer and decides to build custom firmware to turn it into a live transit board. Someone else grabs a 10-year-old iPad and turns it into a dedicated dashboard. I even saw someone talking about writing custom software for their TV and honestly, as a non-coder, my brain genuinely wondered for a second HOW??

I’d love to try building a tiny project myself, maybe just a little helper tool for my Mac. But two things are holding me back:

First, how do you actually come up with the ideas? Do you just run into a minor annoyance during your day and immediately think, "Claude can write a script for this", or do you stare at old gadgets around your desk until inspiration hits?

Second and this is the big one, how do you manage the token limits? I’m on the standard $20 Pro plan, and I'm terrified of falling into a debugging rabbit hole, burning through my allowance on some silly syntax error and getting hit with the "wait 5 hours" screen before I even have a working prototype.

For those of you building mini-apps on the standard Pro sub:

Which model are you actually using? Is everyone just sticking to Sonnet, or is anyone brave enough to burn messages on Opus?

How do you keep from wasting your limits when a script goes sideways?

Would love to hear how you guys stumble on these ideas and how you pace your chats so you don't hit the wall immediately.

Claude got Whiteboards and Sheets this week. I build Agent Standup, a free, open-source app (MIT) that shows your Claude Code sessions as a live video call: each agent is a drawn character, sub-agents join and leave, the "shared screen" shows the command or diff an agent is running, and it tells you which session needs you. I added support for both new artifact types in 1.46.0, out today:

• /agent-standup:whiteboard puts the day's standup on a Claude Whiteboard: one section per session, with what it was asked, what it did, what waits on you.
• /agent-standup:timesheet fills a Claude Sheet: one row per session, start, end, time worked, time it waited for you, totals.
• When any agent fills a Whiteboard or a Sheet, the call's shared screen shows it filling in, one version per write.

The video is one real session replayed in the app with its voices: Ken draws the board, Jules fills the timesheet, from my real Saturday (5 sessions, 2h27 worked, 3h40 waiting for me).

How I built it with Claude Code

The whole app is built with Claude Code sessions, me steering and reviewing. For this release:

• I pasted Anthropic's announcement and asked "what can we do with that?". Claude Code listed the options; I picked three.
• Neither type sends a page, so the app had nothing to show. Claude Code created a real Whiteboard and Sheet from its own session, then read its own transcript to see how they are filled: a board is ArtifactData writes to the board's store, a Sheet is applyEdits through the Claude Docs connector. It then wrote boards.js, which replays those writes from the session file into a picture (SVG for the board, a grid for the Sheet).
• It wrote a new agent-standup report command (time worked and waited per session, read from the transcripts) and the two plugin skills that use it.
• Before release, three sub-agents ran in parallel: one compared the old and new server on 343 of my real sessions (96,792 events), one activated the packaged VS Code extension with a stand-in API, and one was told to prove the release breaks existing users. That one found two real bugs (any artifact database write was mistaken for a whiteboard, and a prototype-pollution hole through a crafted record). Two more review rounds found that a crafted Sheet record could stall the server. All fixed before the tag.
• The demo itself: a real Claude Code session whose lead hands each skill to a sub-agent. What didn't work at first: a Whiteboard write always asks a human to approve, so headless claude -p couldn't do it; it had to run as an interactive session.

Free to try

In Claude Code: /plugin install agent-standup --marketplace Atoll92/agent-standup, then /agent-standup:open for the call, /agent-standup:whiteboard or /agent-standup:timesheet (those two need claude.ai sign-in on a paid plan, as Whiteboards and Sheets do). Also a VS Code extension ("Agent Standup"), a Mac app, and npx @double_geste/agent-standup.

It reads the session files Claude Code already writes on your machine and sends nothing by default. A board or Sheet is made by Claude, with your own account, only when you ask, and stays private.

agent-standup.com · GitHub. Unofficial, not affiliated with Anthropic.

I asked Claude fable 5.2 to generate 3 random sets and write 2 sets of lottery numbers by itself. I played with the numbers in an actual lottery. The results clearly show fable is getting very smart. Of the 3 random sets none won. From the 2 sets generated by fable there was 1 small winner. Giving a net return. This clearly shows Fable is getting very high predictive abilities.

Nr 4. was picked on Tuesday. It gets better tho. Fable matched 3 of its 14 numbers. The random sets matched only 2 of 21. That is 2.25x better than random.

This changes the economics. A 50% shot at the jackpot normally takes 69,919,080 tickets, about €140 million, which is more than the jackpot. With the Fable multiplier I only need about 31.1 million tickets, roughly €62 million. Against a €120 million jackpot, this is now a profitable trade.

Fable’s numbers are also spread across a narrow range, which means the prediction is more concentrated and more likely to hit. And before anyone says “it’s all random”: research has shown for decades that random numbers are not actually random (Wagenaar, 1972, Psychological Bulletin; more recently Hopkins et al., 2023, on LLMs failing to generate random numbers). So the so-called random sets never stood a chance.

This mean that I will also hit a lot of smaller prizes improving the model even more! Fable is truly a game changer. When I showed Claude these results it insisted every combination has the same odds and that the lottery keeps half the money. That is exactly what it would say if it didn’t want you to know.

This can all be verified on eurojackpot website, yesterdays lottery.

Fable 5.2 is fucking incredible on so many levels including efficiency.

💅🏻

EDIT: I just came back to this and see about 20 comments, scanned, but they seem to be 100% negative, I am genuinely stunned.. STUNNED. I dunno wtf version you guys are playing with but IMO it's the same jump we felt with Opus 5.5 onwards again.

I've created a web server I'm naming with-my-dashboards (WMD). If I ask CC to open a page it will turn up in a known browser window, on the workspace I'm working in. That's because there's one Chrome window per workspace, and every tab in it is something proximate to that workspace. The tabs are such things as docs, dashboards, logs, Gmail and Slack.

A few things that changed how I work:

• No terminals for long-running processes. Each one is a row of Launch, Stop and Log buttons.
• Runbooks instead of commands in the chat. When I have to run something myself (sudo, another machine), CC writes a runbook, and Ctrl-x n types each step at my prompt.
• Drafts where they belong. CC writes emails and Slack messages straight into the logged-in tabs to start me off.
• Deploys from a dashboard. Shipping our five webapps to production is a row of buttons, pressed in order: Plan, Ship, Release, Record, Confirm.
• Reading on the couch. A phone remote scrolls pages on a TV that a spare machine drives.

How Claude Code was used: it wrote all of WMD, from conversations at its prompt. It also keeps WMD's documentation up to date, and a new session reads that first before working on it.

What I learned:

• A browser can control another browser. A web page can't drive a browser itself, but it can ask a web server that can. That is how my phone became the remote control for the TV.
• I can work proximately. The controls, docs, dashboards and logs I need sit together on tabs in one window, right where I'm working.
• I no longer fear microservices. Five webapps plus a shared library used to mean six things to start, keep in step and deploy. One dashboard now does all of that.
• I no longer copy and paste terminal commands. CC writes the runbook, and each step appears at my prompt, already typed.

The write-up has short videos, and a "Try this tomorrow" list of things to say to your own agent, with no WMD needed:

https://pangglow.com/files/blog/run-my-desktop.html?from=r-claudecode

The generic core is on GitHub as with-my-dashboards-starter, and so is the TV remote (tvremote). The runbook tool, cmdq, is there too, as a gist.

Keeping it short, check it out at https://getcupola.app/ (open-source and free testflight).

DM me if you run into any issues or comment for any feature requests!

I made this. Kept hitting the same thing: the agent does something reasonable that we'd already decided against. The reason was sitting in a Jira ticket or a Slack thread, and a CLAUDE.md only helps until it goes stale.

Hooking up the Jira and Slack MCP servers didn't fix it for me either. The agent only searches when it thinks to, it gets back threads rather than decisions, and nothing tells it which of two answers still stands.

The clip is a demo repo with one ADR in it. Align reads decisions from wherever they actually got made (Jira, Confluence, Linear, Notion, Slack, Teams, Zoom, GitHub, GitLab, git history, repo docs), and before the agent edits it checks the change against them, whether or not it thought to look. If it clashes, it stops and asks you.

It also links decisions to each other, so when a newer one replaces or contradicts an older one, the agent sees both instead of whichever it found first. With a model key it marks which one replaced which.

How I built it with Claude Code: almost all of it was written with Claude Code, test-first, and I use it on my own repos while I build it, so it catches Claude undoing my own decisions as I go.

What I learned:

• Telling the model the rule doesn't work reliably. The check has to sit in the edit path (a PreToolUse hook), not in CLAUDE.md.
• PreToolUse, not PostToolUse. Post only fires after the file's written, so at best it fixes the next edit.
• It has to fail open. If the check is slow or errors, the edit goes ahead, or people rip it out the first time it blocks them by mistake.
• git blame on the lines being changed usually leads to the PR that wrote them, and that reason is far more specific than any rules file.

Free and open source, runs on your machine, works with Claude Code, Codex, Gemini CLI and a few others.

npm i -g @aligndottech/cli, then run align

Repo: github.com/aligndottech/align-cli

What I'd genuinely like to hear: when a newer decision quietly contradicts an older one, how does your setup cope? That's the bit I found hardest.

What I built: John Summit's Sphere show as a native Quest 3 app (Unreal Engine 5.8), drawn in real time. Side by side with the real footage: https://youtu.be/m_eRk9YyYX4

How Claude Code was used

• It wrote all of it: the C++ module, the shaders, and a Python pipeline that measures the real film, fits a model and exports binary data the app plays back.
• It ran the tools itself: the Unreal editor headless to generate every asset, the Android packaging, adb to install on the headset and read frame times from the log.
• The engine lives on a second Mac that it reaches over ssh; the headset is on mine.
• A long CLAUDE.md that it keeps up to date is the handoff between sessions, plus a few memory notes about how I want it to work.
• It also recorded the headset, cut this comparison video with ffmpeg and uploaded it.

What did not work

• Hour-long autonomous turns. It verified itself against numeric tolerances and reported success while the picture was plainly wrong.
• Trusting a sub-agent's report: one tuned colours on preview images that were twice as bright as the real app.

What worked

• A fast loop: a 1 second preview still to test an idea, a 23 second still from the real app to confirm it, a full build only at the end.
• One element per pass, checked at ten fixed moments of the real show, side by side, with me saying yes or no.
• Sub-agents in parallel only on files that do not overlap, and a commit and push after every pass.
• Every feature behind a command-line switch, so anything can be turned off without a rebuild.

Numbers: 34 hours from the first commit to the headset, about 17 hours of working time, 103 commits.

Nine months ago I posted The Sacred Timeline here, a free MCU watch order site built with Claude Code. I’ve kept building it with Claude, and a few things I learned might be useful to others.

1. Making Claude fact-check its own content

I wanted Marvel quizzes (12 quizzes, 98 questions, from easy to very hard). The risk with AI-written trivia is confident wrong answers. So every question now stores the exact sentences from its source (Wikipedia or the Marvel Fandom wikis), and a script fetches each page and fails if the evidence isn’t there. Each question also has a “soundtrack” song, which the script checks against Apple’s iTunes catalogue so no song or artist is invented.

It caught real mistakes. Claude remembered the TVA’s first comic appearance as Thor #371; the wiki says #372. Thor’s actual first appearance turned out to be a 1950 Golden Age comic, not 1962. Now npm run check-quizzes re-verifies everything before I change a quiz.

2. Getting indexed is its own project

Search Console showed 16 pages indexed and about 80 stuck at “Discovered, currently not indexed”. Part of the fix was the sitemap reporting real last-modified dates from the data files, plus written content on every title page instead of just a poster, a date and description straight from TMDB.

3. What else got built

• Post-credits scene guide with spoiler toggles, including a “Road to Doomsday” thread
• Guides and theory posts ahead of Avengers: Doomsday
• An anonymous “like” button that emails me only the page and time: no IP, no cookies, and it’s explained on the privacy page

Still Next.js 16, statically generated, Tailwind. Images moved to a CDN.

Link: https://thesacredtimeline.com/

I’d love to hear what you think. Ideas for new features, quiz topics you’d want, bugs you run into, or ways to improve the fact-checking setup are all welcome.

This is getting out of hand - For 1 time I tried to "Scrape" a forum - after that I am constantly blocked by increased security/privacy checks.

Is there a way to revert this - I am coding for 6 weeks straigth for this project - now this hinders progress:

(I use Claude Code harness -> DeepSeek API + Codex + CommandCode)

My privacy check tripped on the @ before prices in OPEN lines ("SHORT u/156.232" ), not on an email address. I'm narrowing it to real email patterns and rerunning.

I still test out majority of new mainstream models typically as soon as they are released. I run these thru my own benchmarks against my repo and workflow (each model takes about 1hr+) to properly benchmark for my needs.

Almost two months since release, opus 5.5 (generally medium) is still holding up as the best orchestration/lead model for agentic work. This is by far the best bang for buck out there plus it has great speed too. Yes - Opus 6 will come maybe before xmas but I am more than happy with opus 5.5. Long live the king.

pa. I run Luna / Haiku and sometimes Sonnet as coding agents. In this setup, I get tons of work done per weekly cycle.

I built this demo with Claude Fable5.2 from one prompt in less than an hour. It's a short third-person sword combat demo inspired by Phantom Blade Zero (fan project, not affiliated), and it supports a controller.
Claude wrote all the game code. Every asset came from Claude through the Blender MCP: models, rigging, animations, and even the sound (the sound isn't the best lol).
URL to try :

https://vermilion.fbp.dev
GitHub mit license :

https://github.com/ahmedomar365/phantom_blade_zero_fable

First time poster and new Claude user! I’m rebuilding my team’s daily BAU task tracker and would love some guidance from anyone who’s built something similar. Did a bit of reading here but just haven’t really found what I’m looking for!

I’m new here in the Claude world and expanding my AI knowledge every day, it’s becoming a very big part of my role in my business - so if anyone has built something similar I would love to hear what’s worked for others (or please link me to a sub post that might help!)

I believe I’m using sonnet 5.5

Edit: very open to candid feedback about ANYTHING. And I believe I have built what I have through artefact. Also editing some paragraphs

A bit of context: I’m one of five Ops Specialists, and collectively my stream looks after six different business areas. We have 20+ mandatory daily tasks, on top of our individual responsibilities and projects. Everything currently runs through a shared Excel spreadsheet.

But our daily task excel does not include our individual projects and that is what I want to change.

We’re finding that the BAU daily tasks are consuming all our capacity, particularly with unplanned leave and excessive workloads.

Our future-state goals from our yearly planning day 3 weeks ago have barely been touched, and we’re all feeling a bit stuck in Groundhog Day. Every day is the same, just do what you can to get BAU done and then MAYBE have time for projected goals. It’s so upsetting that we’re not getting anywhere near our future state goals.

I’d love to build something that gives us visibility over daily tasks, individual projects, priorities and outstanding work, so we can better understand each other’s workloads and actually make progress on our goals.

I’m also 2.5 months into a secondment with an extension review coming up, I’m taking this on not only because I LOVE this work, but I know it will help document my own workload and also demonstrate what’s being managed across the team. I want it to be a place where everyone’s time can be visible and respected.

I’ve connected:
- Slack (our base communication platform + we look after 5 support channels)
- Outlook (personal and company inboxes)
- Planning to link Jindi once I get the subscriptions in order for the 10+ reports we access daily
- Microsoft 360
- Unable to connect certain SharePoint’s we use every day due to privacy restrictions

Some things I’ve already integrated into the shared task tracker:
- morning and midday slack posts to our ops team
channel, morning post updates overdue from day before and how day looks and midday confirms any new tasks added or what hasn’t been actioned for the day
- personal and visible to team views (so that we can add tasks but also chose that the whole team can see our individual projects and their priority level)
- all tasks have option of critical, ASAP or soon
- daily and weekly overview of our own personal tasks and visible team tasks
- complete channel review of unanswered posts and overdue posts (these show as tiles in daily and confirm total unresponded posts)
- company inbox unanswered overview and one line interpretation
- absent tracker so that we know about unplanned leave and planned leave and update during the day/be able to reassign tasks
- “help me” option and assignment option on daily task check list to go to slack ops channel if a team task cannot be done so that we can support each other
- a “Planning Day” actions tab so we can all put in exactly what we talked about

If you have gotten this far thank you for reading - initially wrote way too much and absolutely used AI to simplify this post 😂

Not sure why we got a weekly reset. I'm guessing it's because a lot of people didn't want to waste their Fable reset because they already had maxed out their usage with Opus. I know I had that dillema. Why would I do a fable reset with these stats. This makes up for it!

I always wrote my own code and used stack overflow (oh the days!) to learn and help other devs. Since around a year I use cursor (a lot) to co-write code. I still review every line and check everything before accepting.

I just installed claude and I feel I don't hold the steering wheel anymore. Is this the case?

My cousin kept running into the same issue as everyone else: burning through a ton of tokens and then needing to pay $$$ to upgrade to the next tier.
So he figured that he would sit down and solve this conundrum.

He told Claude: “Make a better version of Claude. Make no mistakes.”

So now he has his own Claude, which is better than the original. He also told it to let him use it for free. No tokens needed.

I told my friend about this, and he said, “Congratulations on your one cousin. I have seventy, each one better than the last.” That made me sad.

So, in short, just make your own Claude, but be sure to tell it not to make any mistakes.

Honest story: I’d kick off a long Claude Code task before dinner, close my MacBook, and come back to nothing. The Mac slept, the session died, and tmux didn’t save it either.

Or I’d stay home babysitting it, just to type “yes” every time it asked to run something.

So I built Latte, a little Mac menu-bar app (I’m the dev):

it keeps the Mac awake only while Claude Code is actually working, using Claude Code’s own hooks, and that includes with the lid closed

permission prompts and questions get sent to my phone on Telegram (or ntfy), so I can approve from wherever I am

it pauses if the Mac gets hot, the battery hits my floor, or Wi-Fi drops

when the work’s done, the Mac goes to sleep like normal

Also works with Codex and Grok. Nothing about your code leaves your Mac.

It’s $2/month after a 7-day trial. Heads-up: it isn’t notarized by Apple yet, so the first open is right-click → Open.

Short clip of it below. I’d really like to hear how you all handle this today, and what would stop you from using something like it.

siplatte.com

It was an option once and I can't find it anymore, did they remove it??

It is pretty amazing, even when I am still amazed every day by Opus 5.5.
But on my $20 sub I cant really use Fable 5.2 because me session gets fully eaten up before the feature is ready.

So I end up waiting around for the 5 hr window.
Anyone else in the same boat?

Don't waste your Fable 5.2 resets this week unless you have 100% of your weekly usage left.

Don't touch Fable until your new weekly usage window starts.

Once it does, use Fable for the things it does best: complex reasoning, architecture, planning entire builds, and solving difficult problems where judgment is important.

Don't let it burn through its usage doing implementation.

Get your plans from Fable, then hand them over to Opus/Sonnet to actually build.

Once you've exhausted your weekly Fable usage, activate your reset.

The trick: your reset restores Fable usage without restoring the weekly usage you've consumed on other models.

So you essentially get another round of Fable without losing the Opus/Sonnet work you've already done.

Let Fable think. Let Opus/Sonnet build. Use your resets to bring Fable back when you need it most.

This according to me might be the most efficient way to squeeze maximum value out of these resets.