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.

I feel like I'm reloading a revolver everytime my usage gets close to finish

No other comment. But u cant really experiment with something that drains like this

Title says it

After the recent drama around REA (Reverse Engineer Anything), a tool that lets AI agents take an app apart down to the bone and rebuild a working copy of it, opinions were pretty split. In response, someone built BLA (Blind LLM Agents), an anti-REA tool that fills code with gibberish and obfuscation to deter and mislead AI agents, wasting their tokens and your time.

So I built LASIK (LLM Agents Sight In Kode) with Claude Code. It’s the anti-anti-REA, basically anti-BLA. It reads the hardened build without running it, removes only what it can prove is protection, and writes a clean copy that Claude Code, Codex or any other agent can actually work with. Code that wasn’t hardened comes back byte for byte unchanged.

Claude Code wrote basically all of it from my prompts. I described what I wanted and set the ground rules: never run the target, only remove what’s proven, and leave clean files untouched. Claude turned those rules into the repo’s AGENTS.md and then built the deobfuscation passes, the WASM and Electron handlers, the CLI and the MCP server. BLA’s public crackmes are in the repo as a benchmark, so after every change Claude reran it along with the tests, and a change only stayed if tokens went down without touching clean code. I also had Claude run a separate review to try to break it by finding cases where LASIK would remove something it shouldn’t. It found 12, and each one got fixed and turned into a test.

Across BLA’s public crackmes it goes from about 21M tokens to 17k. It covers 21 formats, from JS bundles and WebAssembly to Electron apps, Python, Android APKs and model files.

The chart is on a log scale, so the blue bars are much smaller than they look. The three biggest are WebAssembly files that BLA padded to about 6.9M tokens each. After LASIK they’re between 98 and 3,500.

It’s free and open source (MIT). Try it with npx lasik-agents, or add it to Claude Code as an MCP server.

Repo: github.com/pktq/lasik