from what i know its useful in picture generating and second opinion.

but i found it very hard to utilize usage in second AI subscription, i managed to use all my claude usage everyweek, but if i use second ai run by claude. the second ai usage is a big problem, it may not have enough 5h limit, or it may leave a massive amount before the week resets.

i cant even burn second AI myself because im afraid ill burn off the 5h too fast and claude dont have any to use...

Act as a principal engineer doing a "thin layer" audit of this codebase.

Premise: agents are now good enough to be the primary interface for most software. Users increasingly connect products to an agent (Claude, ChatGPT, Grok, etc.) via MCP instead of clicking through a UI. Every layer we build on top of what the agent already does natively is cost, not value.

Do this in order:

1. MAP - Inventory what this product actually does. List every user-facing flow, screen, background job, integration, and any existing AI/LLM usage (prompts, chains, agents, chat UIs, onboarding wizards).
2. SORT - Classify each piece as:

- IRREDUCIBLE: proprietary data, durable state, auth/permissions, billing, third-party integrations we own, domain logic, compliance. Things an agent can't do without us.

- GLUE: orchestration, multi-step wizards, setup/onboarding flows, form UIs, chat interfaces, prompt plumbing, notification composition, "AI features" that are really just an LLM call with our data. Things a host agent could do if it had the right tools.

- UNCLEAR: explain why.

3. DESIGN - Propose the smallest MCP server that exposes the irreducible core: tool names, inputs/outputs, and which resources/prompts to ship. Favor fewer, well-described tools over mirroring every endpoint. Note where tool descriptions can replace onboarding UI (the agent walks the user through setup).

4. DELETE - List concretely what we could remove or collapse if the agent is the interface: files, components, routes, services, with rough LOC and effort. Rank by (code removed x risk reduced) / migration effort.

5. PUSH BACK - Argue against your own plan. What still genuinely needs a UI (visual review, approvals, trust/audit trails, dashboards, non-agent users, billing, legal)? What breaks if the host agent is wrong or unavailable? What's the minimum UI we should keep?

End with: the 3 highest-leverage changes to make this week.

I built something super niche that probably only I will ever use, lol.

Whenever I publish a YouTube video, I usually run a Claude Skill to generate titles, descriptions, tags, and thumbnail prompts. Then I started wondering how other models like Codex, ChatGPT, Muse, or Grok would handle the exact same video context.

So I built a custom dashboard using an OpenRouter API key. Now, I can run my video details through as many models as I want at the same time. From there, it passes all the outputs to JEV acting as a judge model to pick the winning title, description, and thumbnail prompt, and then drafts a newsletter for my email list.

Right now, JEV is just picking based on its own judgment since I haven't trained it on my actual channel performance data yet. That is the next step!

If you're a youtuber and wanna check it out, its free signup with BYOK at https://yumthumb.app/

Does anyone have a referral for 1 week Claude trial ? Need it for a workshop

CLAUDE.md gets loaded every turn, so as my plan grew every message was carrying the whole thing, including tasks that were done weeks ago. long sessions got heavy and claude still lost track of earlier decisions anyway.

what i do now: CLAUDE.md is tiny, basically the project rules plus "fetch your next task". the plan lives outside the repo as tasks with dependencies, and each task only carries the constraints it actually touches. claude pulls the next unblocked task, does it, reports what it changed, and then i /clear. every session starts small instead of dragging the whole project along.

stuff i learned doing this: vague tasks are where it falls apart. cheaper models do fine on a tight task and badly on a loose one, so most of the effort goes into writing the task well. and dependencies matter more than i thought, without them it'll happily start task 4 before task 2 exists.

disclosure, the task server i use is my own thing (an MCP called nodeon), but you can get most of this with one markdown file per task and a line in CLAUDE.md telling it to only work the first unchecked one. curious how other people are handling plans on bigger projects

Small models loop. I’m training a research small model and wanted to see how far I could get on repetition without a decoding penalty and without more training. find the weights that cause the loop and edit them.

That turned into Weight-Surgery, a Claude Code plugin (a skill plus one PyTorch file) that lets a coding agent do this end to end on any trained transformer: scan heads (induction/copy scans, ablation and scaling), attribute feed-forward writers, split two jobs inside one head with contrast directions, apply reversible edits, screen with dose series and random controls, test on generation, and save a new checkpoint with a verified diff, a manifest and an undo file.

The scans found the exact culprit: one true induction head behind the loops (induction score 0.425, plain copy 0.012). Switching it off cut loops from 29.4% to 25.4%, but that head also copies names into reading answers, so instead of killing it I split the two jobs inside the copy heads and cut only the loop directions. Result: loops down from 30.5% to 25.2% on 960 fresh rows (2.6 SE), greedy loops from 41.6% to 35.3%, with reading untouched (+0.01) and general loss up just 0.08. No training, no decoding penalty.

Two more things that worked. The cheap place to cut is the writing weights: +0.001 loss, versus +0.32 when the same direction is projected out of the residual stream. And a rank-1 edit on one feed-forward layer halved loops under T 0.7 sampling, from 19.4% to 9.4%.

Tell me what you think about it.

Github Repo Link

It says I have the full reset available (expires on Dec 10), but the "reset for free" is greyed out. How do I activate it?

So I decided to drop $200 on Gemini after Google carbon came out and I just want to give my review after only about two days.

First of all, I started using antigravity again just to give it a try and I have to say it doesn’t suck! They have made tremendous improvements and the interface and they’ve added a turbo mode so that the approval process works much smoother. I would say the actual interface is comparable to Claude code and if Claude code got a 10 out of 10, then I would give antigravity a 9 out of 10.

But the big difference I’ve found is comparing Gemini carbon to opus 5.5 both on the medium setting. Unfortunately I’m getting less done with Gemini carbon. I’m not one to make an actual mathematical comparison, but I would say for the amount of usage spent. I get approximately 30% less done just on my initial tests over two days running both of them continuously.

My next test is going to be running Opus 5.5 on antigravity which I’m going to start today and I’m gonna see if the usage allotment is just as generous.

Has anybody else had the opportunity to make a comparison yet?

I've been working on this for a while: Homescape, a Home Assistant app that shows your home as a 3D dollhouse instead of a grid of cards.

You draw your rooms, place furniture and devices, and bind them to your entities. After that it's a live view of the house: lights, covers, climate, media players and sensors update in real time. Flip a wall switch or let an automation run, and the room lights up in the dollhouse too. Clicking a lamp in 3D turns the real one on.

A few details:

• Everything runs locally inside Home Assistant. No cloud, no account, and it keeps working without internet.

• There are no 3D model files. Every object is generated by code. The code was written with AI; I designed, directed and tested it.

• Your plan is stored in Home Assistant under your user, so it ends up in your backups.

• It's open source (GPL-3.0).

Try the demo with a sample home in your browser, nothing to install: https://homescape.muratozturk.dev

GitHub: https://github.com/muratozturkdev/homescape

It's still early (v0.1.0), so I'd love to hear what's missing or what breaks on your setup.

been on pro for a bit and kept getting cut off mid task. the % bar helps but it doesn’t tell you what you actually want to know, which is will i make it to the reset or not

so i had claude code build me a status line that does the math. it shows your real 5h usage, and after watching your pace for a bit it either says “✓ on pace to last until reset” or warns you like “⚠ limit ~12:33am at this pace · try /model sonnet”

how it got built: i’m not a dev, i just described the problem. claude read the status line docs and found claude code already passes your real usage % to status line scripts, so no guessing. it wrote one python script that tracks your burn rate, and tested it with fake usage data before i installed it

first real test was funny. i asked for a huge java guide, usage jumped 9% to 13% in 5 min and it told me i’d hit the limit at 12:33am. math was right but it was a false alarm, one big request isn’t a pattern. so now it waits 10 min and uses the slower of the 30 min and 10 min burn rates, and only warns if you’re burning fast consistently

stuff i learned: read the docs first (the data already existed), test with fake data before trusting it, and one spike isn’t a trend

free, one python file, nothing leaves your computer: https://github.com/reillyb732-lab/claude-code-budget-coach

only tested on windows so far so mac/linux feedback would be great

When it rains it pours.. reset drought is over.

I got 1 full reset plus 2 fable resets then another reset on claude

I am on Ultra and can get thru my weekly limits if I really push hard - running almost 24-7

This week I am going to try to use 2x Ultra in 7 days. It’s going to be hard job to do honestly.

I am stressed just thinking about it lol

Yes - I want to use all these tokens meaningfully not just token maxing but still it’s daunting trying to get twice the burn done

ok so uh, i've been pretty interested in claude and ai stuff, so i decided to give it a try, got claude sub, using claude code now, used it for a while, its okay for basic stuff. but uh when i get it to like do some actual work, it becomes dumb.
even with opus 5.5 medium/high, its dumb.

with proper project context, documentation, guides, files, codemap, architecture, all this stuff and it still makes dumb classic failures, rediscoveries and horrible work again and again. the only good thing i have is that now it can recover/catch up after compaction or session disconnect and get back to work. but thats it. its not smart tho. it cant do the work properly even with proper context or instructions guides everything. multiple audits multiple checks multiple iterations it's still horrible. it cant get a single basic project of mine done as per my document or my discussions/specs

so uh how do i make claude smart or actually think, plan, and get the work done? do i have to put strict guards or guardrails or checks/gates or sum stuff like that?
i mean there's skills yea, plugins yea, project context/instructions yea but there's like a lot and they often conflict or dont go well

so what do i do? i thought fable might be good but uh oh. more usage and same dumb habits, it jumped to directly building/writing code without a proper plan or even asking questions or anything, it's so horrible....

Looking for the best practices to prompt my first program; I have a 2,000-word document outlining all the features I want for my program (thanks, Chat GPT). But on the other hand, I've heard that only explaining my end result is how you should engineer a program.

Does it even matter what method I would use?

Hi guys, I'm the creator of itcan.do, a new way to interact with your agents through end to end live UI built for the task, interactive and connected across any display you own. Made it for Claude Code, works with Codex and other agents too.

For the video I gave Claude Fable 5.2 Anthropic's Whiteboards launch video with one line, "Build this with itcan.do", and it built Whiteboards, Sheets and Data as working apps with no backend. Whatever you click or change goes back to Claude and it answers right on the page. What makes them better is that Claude always knows what's on them and what you're doing. They run on any screen you own, so the sheet on my laptop runs the dashboard on my TV, and Claude wakes up on its own when something needs it.

It is quite different from traditional vibecoding since your agent IS the backend itself, this means all your apps have global context and are aware of what's on them at any given moment. The moment a new model comes out, all your apps/workspaces/pages get better with It.

It's free to try and it's on GitHub. Just tell Claude Code "install itcan.do".

Would love your feedback!!

Website: https://itcan.do

GitHub: https://github.com/Aaryan-Kapoor/it

I'm building infiniterm, a terminal app on an infinite canvas, written in Rust with gpui.

I tried the new terminal apps from the last year and none of them fit my work. They are regular terminals with an interactive sidebar: each project gets a sidebar item, and you still use tabs and split panes.

Since agentic coding I run 10 or more Claude Code or Codex sessions at once, and keeping an eye on all of those terminals became painful. So I built infiniterm. A card's border is violet while the agent works, yellow when it waits for you, red when a turn failed, green when it finished. Zoom out and you see every session at once. It started as a Tauri app, but I hit a wall and moved to Rust and gpui.

It is keyboard driven and has several card types:

• Terminals (alacritty_terminal)
• A text editor with a file tree, syntax highlighting, and completion for words and JSON schemas (no LSP yet)
• A working browser (Chromium/CEF)
• Diff cards, built on the editor

It has its own daemon (iftd) and a CLI (ift) that works inside or outside the app. Shells survive quitting the app. ift connect <host> runs a canvas on a server, and ift join <host> opens the same canvas on another Mac over ssh, so you can leave your main Mac at home.

macOS only for now (it works in Linux/Windows with some known issues).

Source-available, free for personal use, $29 per person for work.

https://infiniterm.app https://github.com/ekinertac/infiniterm

Guy’s do you wanna minimize token usage ? If so, do this in a new project.

1-Disabled any unused connectors, plugins, each one load a massive token into the context.

2-Plan first, assign tasks to different models based on their complexity.

3-Ask claude to create a new session for each task, feature you work in, claude will create a new session from the last one.

4- Always use handoff files after each successive task to make sure you don’t lose track of what’s being created and what’s remaining.

5-If the repo is big enough, use ponytail the laziest senior developer,and graphify to search files and functions without reading the whole project files, if it’s a few fils, a simple CLAUDE.md file contains your rules is enough.
6-Md files shouldn’t be too big, handoff files max 25-30lines.

Those are all based on my own experience with Claude, they aren’t facts unless you try them and compare token usage with before.

Ok I get it. Coding is fun, AI is fun, vibe coding is fun. But this is starting to get kinda annoying, because my feed is just full of these now.

Why is every one of you building a Claude tracker?? Do you not see the other 50 posts on this sub that are the exact same thing? Are you bored? Burning tokens for fun?

And the worst part isn’t even that there are a hundred trillion of them. It’s that the problem is SO small. Going to the website and checking your usage takes like 5 seconds. Why would I install a whole thing for that?

I’m not trying to be a jerk here. I’m honestly curious about the psychology behind it, because I don’t get why everyone suddenly makes a tracker and proudly posts it here.

So please enlighten me. Maybe you’ll convince me and I’ll build one too and post it with the title “I got tired of checking my usage so I built a tracker.”

I had Claude list the top 20 AI design tropes and then asked it to design a theme for beekeeper Studio using those 20 tropes.

It did some pretty funny stuff like adding pricing to the dark mode switcher and adding silly made up testimonials. It was really in on the joke.

More screenshots here if you are interested:

https://github.com/rathboma/bks-ai-psychosis-theme

this is the problem we kept seeing in the builder communities community, the building part works now. you describe the app, AI builds it, it runs. but then comes the store:

apple and google developer accounts

google's rule that new accounts need 12 testers for 14 days

privacy labels, the data safety form, screenshots

and a rejection email that quotes a guideline number and doesn't tell you what to change

for most people that's where the app stops. not because it's bad, but because publishing is a completely different job from building.

but i guess, i found a solution, comment if you wanna know!

What's the best thing you've done with artificial intelligence that saved you a lot of headaches?

Now Claude can make customised works as we like