r/ClaudeCoding • • 20h ago

r/ClaudeCode [TLDR] Sol 6.2 and Astra 6.2 just released [via r/ClaudeCode]

0 Upvotes

OP : u/Standard_Exchange59

Fable 5.2 is better than Astra 6.2 and Opus 5.5 is still unmatched for Sol 6.2.

I do not care about cost per task personally so if anyone wants to dig into that feel welcome to post here.


Original link/media URL : /img/2ew69thiz72i1.jpeg


r/ClaudeCoding • • 14h ago

r/ClaudeCode [TLDR] I need help to reduce Claude spending [via r/ClaudeCode]

1 Upvotes

OP : u/azadmir

Hi fellow redditors,

I'm building my own construction SaaS which has grown into quite a beast, with over 900 tables and 60+ pages across 22 modules. I'm using both Claude and Codex simultaneously, sometimes running up to 14 agents at once—which is my current machine's capacity.

The problem is that I'm spending between $6,000 and $8,000 a day on average. I use Fable to orchestrate everything, and it assigns its own agents for testing, auditing, etc.

My question is: is there any way I can cut these costs without sacrificing quality or speed?


r/ClaudeCoding • • 5h ago

I wanted to see what my Claude Code agents were doing, so I built a pane for it (open source plugin

2 Upvotes

I was inspired by Agent Flow, posted on this sub. I loved the idea, but running it in VS Code put a noticeable load on my computer, and I wanted to see everything inside the Claude app itself, right next to my session. So I built a side pane for it. It's called Agents, skills & plans. It's my own project, free and MIT licensed.

The video shows the graph view while a session works through a four-step plan (demo data).

What's in the pane

For every open Claude Code session it shows:

  • The plan Claude is working through. The current step pulses, replaced plans move under "Past plans", and dropped steps get struck through.
  • Subagents, attached to the plan step they were spawned under, with status, running time and their most used tools with call counts (Grep 21, Read 7). The tool a subagent is using right now is outlined.
  • Skills, as pills under their step: active, used, red on error, ×2 when repeated. Skills a subagent calls show up on its card.

Your current session sits on top in a frame, the others below it, and each one folds. You can switch between a compact list and an animated graph, and hide plans, agents or skills. Turn plans off and the graph becomes a timeline. A statistics card ranks the skills and subagent types you use most, counted from your transcripts. Screenshots of both are in the README.

Install

In a Claude Code terminal session:

/plugin install subagents-pane --marketplace qaokss/claude-agents-view

Answer y to add the marketplace, then pick a scope (user scope loads it in every session). In the desktop app, where /plugin doesn't run: click + next to the prompt box, then Plugins, Add marketplace, enter qaokss/claude-agents-view, then Add plugin.

The pane opens by itself when a session starts. If you close it, /agents-view brings it back.

It installs from GitHub because I couldn't list it in the official plugin directory: the portal only accepts mods from Verified organizations.

What it actually runs

It's a Claude Code hooks module. No server, no network. Plans come from Claude's task list tool calls, subagents from their spawns and turns, skills from Skill tool calls. Each session writes a small JSON snapshot under ~/.claude/mods-data/subagents-pane/, and the pane reads the other sessions' snapshots. The statistics card runs grep over ~/.claude/projects every 30 seconds, only while the card is open. Everything stays on your machine.

It costs no tokens. The mod never calls the model and adds nothing to the prompt or context: every hook passes the event through unchanged and only records it. The pane is drawn beside the chat, and the model never sees it. The only text it puts in the chat is a one-line reply when you run /agents-view yourself.

It's light on your machine too. A timer updates the pane once a second, and the snapshot is written only when something changed (plus a heartbeat every 30 seconds). The grep for statistics is the heaviest part, and it doesn't run while the card is closed.

Limitations

  • The graph needs the desktop or mobile app. In the terminal you get the list view only.
  • The hooks module API is in early access. I built and tested this with Claude Code 2.1.321 to 2.1.325, and it may break or need changes as the API changes.
  • A session that stops updating disappears from the pane after 90 seconds.

How I made it

I built the whole thing in Claude Code over one long session, iterating on the design with a ui-designer subagent.

Repo: https://github.com/qaokss/claude-agents-view

Two things I'd like to hear: what you'd want the pane to show that it doesn't, and whether the graph reads clearly on your setup. Bug reports go in the GitHub issues.


r/ClaudeCoding • • 8h ago

Claude doesn’t volunteer security unless you ask. People here have noticed it, and new benchmark data backs it up.

Thumbnail
leaddev.com
1 Upvotes

AI coding rules matter more than your model.


r/ClaudeCoding • • 14h ago

r/ClaudeAI [TLDR] Something happened [via r/ClaudeAI]

3 Upvotes

OP : u/Inevitable_Truth_85

100% claude code.
Last couple of weeks made huge progress. Keeping a super tight development process with opus 5.5 only since it came out.
Was able to get to Sunday night easily including using Fable here and there.
Last week had to reset.
This week - ONLY two days. 53%.
And have moved some work to sonnet already yesterday.
WTAf 🤦‍♂️


Original link/media URL : /img/z8mlb6ddk62i1.jpeg


r/ClaudeCoding • • 2h ago

r/ClaudeAI [TLDR] Claude Code is insane. My entire self-hosted Netflix is 17 MB. [via r/ClaudeAI]

2 Upvotes

OP : u/CoderLuii

last week i shared holyarrs here, the netflix-style app i built for my media server with claude code. since then: 1,445 github stars, 23,763 docker pulls, 26 releases and 309 closed issues in 8 days. 299 people joined the discord and 533 signed up for updates

quick recap: a home media server usually means six apps (sonarr, radarr, lidarr, bazarr, prowlarr, seerr) just to find and get a movie. holyarrs does all of it in one app, about 17 MB, and plugs into what you already run: qbittorrent or sabnzbd to download, plex, jellyfin or emby to watch

last post i listed what was next. here's what actually shipped:

  • an mcp server, so claude can talk to your library
  • 4K requests, and every request can wait for the owner's yes (that's the video)
  • plex friends' watchlists turn into requests on their own
  • run it without my metadata server at all, or with your own tmdb key
  • the app in 44 languages (i promised 11 more, it got a bit out of hand)

the part i didnt expect was how fast the issues came in. people were filing bugs and ideas faster than i could read them, and a few even sent fixes themselves. claude code helped me keep up, and 309 issues got closed in 8 days. honestly the people using it made it better than i could alone

i've been putting in 16+ hours a day on it since launch. most days look the same: wake up to a pile of new issues, pick one, have claude code dig into it while i check it on a real setup, ship the fix, reply to whoever reported it, next one. some days that loop ran 5 or 6 times

it's free and open source. still a beta, so expect rough edges. i'm in the comments

what's the one thing it still needs before you'd switch?


Original link/media URL : https://v.redd.it/yh6yhdiuuc2i1


r/ClaudeCoding • • 21h ago

I built an app for reviewing the specs and plans Claude Code writes, and it sends your notes back to the agent

1 Upvotes

I work spec-first with Claude Code. The agent and I shape an idea, then it drafts the requirements, a spec, ADRs and an implementation plan. I review them, and only then does it write code. Those documents become the project's record of what was decided and why, so reading them carefully matters as much as reading the code.

Reviewing them was the slow part. Editors and IDEs are built for editing, not for close reading. I couldn't easily see which docs were settled and which were still open. And giving feedback meant copying section references into the chat by hand, so the agent knew which part I meant.

So I built Folio, a desktop app for reviewing a project's Markdown docs. Open a folder and it shows every document in it:

  • Each doc's status (accepted, proposed, superseded), with filters and search across all of them
  • Docs rendered with Mermaid diagrams, math, code and cross-links
  • Highlights and notes on a passage or on a whole doc. Your files are never modified; marks live in ~/.folio
  • What changed since you last read a doc, down to the sections the agent rewrote

There are two ways to get your notes back to Claude:

  1. Copy and paste. Folio collects your notes into one Markdown block, with file paths and line numbers, for any agent.
  2. Review loop. Install the plugin:/plugin marketplace add crazzybot/folio /plugin install folio@folio Then run /folio:review-loop. Claude waits while you review. When you click Send, it gets your notes with their context, revises the docs, answers each note in Folio, and waits for the next round. Other MCP clients (Cursor, Codex) can do the same through the MCP server.

It's free and MIT-licensed, for macOS, Windows and Linux. Folio itself was built with Claude Code, using this same workflow.

I'd like to know how you review what your agent writes. Do you read the specs and plans, or only the diffs? How do you tell it what you decided? And if you've built a human-in-the-loop step like this, how did you hook it into the agent?

A proposed ADR in Folio: what changed since I last read it, my note, and Claude Code's reply

r/ClaudeCoding • • 4h ago

claude code & Codex?

2 Upvotes

Hi,

I'm building quite a lot with Claude Code and I'd like to have my work checked by Codex as a second reviewer. I'm curious how you handle this.

Right now I've set it up in Claude Code so that whenever something is finished or about to go live, it first has to pass a Codex review before it can be deployed, even to a test environment.

A few questions:

  1. How do you set up this kind of review flow? Do you do it the same way, or do you use a different approach?
  2. How do you work with multiple AI models within the same tool? For example, Claude writing the code and Codex reviewing it.
  3. Are there specific tools you use or recommend for letting multiple AI models review code?

Would love to hear how you approach this. Thanks!

Best,

Bart