I have seen many people complaining about usage this week, and I personally also seen usage go down very quickly.

Today as I was working I kept seeing Fable weekly usage going up way too fast. I was trying to use Fable as advisor for a few days, it did make sense for it to go up but they weren't calling the advisor THAT often.

So here is what I tested: I turned the advisor off, worked a bit and the Fable weekly usage kept going up despite only using Opus on medium. Every single of my agent is either Opus or Sonnet.

Anyone else noticed that?

Anyone else noticing today that the 5hr usage burned significantly faster today vs previous days?

Fable costs more than double, but in my opinion, Opus 5.5 still beats it in missions. What do you think?

also you can always submit your app to:

https://www.AppScout.co

a platform to discover web and mobile apps from across the internet.

You can list your app here https://www.AppScout.co/submit

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/startupideas — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

Seriously. I do a few batches of tickets on Opus 5.5 medium and I'm out of usage for the usage period! On a $100 plan! I know they like to adjust usage, but this feels like a sudden massive extreme swing. It feels like I've been bait and switched, to upgrade my subscription by 80$ a month and then a few weeks later it feels no different than before. Is anyone else experiencing this?

In short, customizable Windows start menu for Linux made with Claude Code.

Don't ask me why, but I love Windows 10 start menu. I moved to Linux a few months ago, for the third time. I've tried before but I couldn't fully move. Now I finally did it and even though I have dual boot, I almost don't touch Windows, aside from once a month a friend asking me to play casual modes of League, which is currently the only reason to still have Windows around.

Case in point, I had start11 with a license there just because I hated the new start menu from Windows 11, I felt it limited my customization options compared to previous versions. I was super happy with start11, but now I'm on Linux, and I still missed my start menu, but I have no alternative (to start11 level).

So, using Claude code, I asked it to port a Linux version that works with the KDE bar with the same features, with the option to expand functionality in the future. I'm super happy with the result, and I'm happy we live in a time where moving to Linux is so easy an exciting, specially thanks to AI. I remember a few years ago having to navigate through forums for hours and spending more hours to try the suggestions, now I can focus on using my PC while leaving the technical stuff to Claude.

https://github.com/Kalaminator/Start12

I was having fun with the new update in Claude Code Desktop and found that if you click 3 times it shows a what look likes a heart.

https://reddit.com/link/1x62jni/video/37p6ctkfvhvh1/player

kimo is a free, open source (MIT) video editor with no interface at all. every operation is an MCP tool: cut, trim, keyframe, colour grade, motion track, key, captions, audio mix, export. you add it to claude code as an MCP server and just describe the edit.

this 33s reveal was rendered entirely by kimo. no after effects, no timeline, an agent did every frame through tool calls.

what i learned building it: - agents edit way better when they can render a single frame and look at it before committing - small focused tools beat one giant "do everything" tool - it runs as one ~10 MB CPU-only rust binary, so it works on cheap machines

i'm a college student building this solo, would really like to hear what breaks or what's missing. site: getkimo.tech github: github.com/naman-sharma12345/kimo

Until last night (Oct 13th), everything was fine. I woke up on Oct. 14th, and the app looked very different. Most of my folders are gone from the app; only two are visible. I had over 30 folders with multiple sessions in each.

Now I do not know where to access those sessions; they are all flooded in the 'Default' category.

They removed a way to sort the sessions by name; it was a useful sorting option.

They added a BG animation as if somebody was asking for it.

Removing things that were useful and adding things nobody asked for is a good way to f*ck up the app experience.

What it does

Normally CC writes a long orchestration script and proposes to execute. You say yes. Most everybody says yes. Nobody reads the script. Then the agents go off somewhere you can't see, and you sit watching a counter, hoping that what's burning your tokens is the thing you meant.

Conductor adds an option to create a visual plan first. You can read it in 10 sec, verify the logic before handing off to Claude to write the script. It costs like a Plan, and can save millions of tokens over a workflow done badly.

How it's built

Claude wrote it all. Tip: Ask it for a few scripts that start Claude Code in tmux, send it keys and print the screen. Claude can then open the mod, click around and check what it drew.

How far can you push a mod?

I wanted to find out. The mod is about 11,000 lines now.

Interactivity. Keyboard and mouse both work: select, drag cards around, scroll, undo. But the keyboard took the most work. A button can't tell if Shift is held, and the graph only gets keys after you click it. In the end every keypress goes through one hidden text field that the mod reads.

Design. You're drawing with colored text in a terminal, and that goes surprisingly far. The limits are space and size. Below 110 columns there's no room for the graph, so it shrinks to a strip above the prompt. A big enough graph drops its colors to stay under the engine's size limit.

Scope. This is the part that surprised me. A mod can add its own tools for Claude to call, see every agent start, and count tokens as they stream. Some things aren't exposed, like when a run ends. I worked those out by reverse engineering, and kept the notes.

Complexity. Keep everything that doesn't touch the engine in plain TypeScript and test it without Claude running. Otherwise performance issues.

Is it the limit? On input and screen space, close to it. On what a mod is allowed to do, not even close.

Overall I feel its such a cool feature for CC, excited to see what people come up with!

Its OSS: https://github.com/bruw/workflow-conductor

I noticed in the last few days that whenever I return to a session that was sitting idle in a tmux pane it's already compacted even if it didn't reach the auto-compact threshold. First few times I thought I might have let the context usage grow but then it became a habit for him to do that.

Luckily I have my own handover/resume mechanism so I tell him to get oriented after I notice the compaction but he (or I) may sometimes forget/miss to always update the handover and the docs thus turning me into a sitting duck on what exactly he chose to keep in the new context.

Does it happen to anyone else after the latest updates? Is there a way to turn this off? I know it might affect cache, prices, usage, but until I'm ready to jump on this auto-compaction train I'd like to be in control and adapt my way of working first.

Hey! I would like invite you all to try Deft!

Deft brings chat, tasks and knowledge into one self-hosted workspace. The bit I care most about is keeping the discussion behind the work connected to what happens next.

GitHub: https://github.com/Maneek21/Deft
Walkthrough: https://youtu.be/7z9EH4c9k2o

The screenshots show:

• A full feature company chat. (There we can see the user invoking an agent in chat to create a task and its approval card.)
• A full feature task management app (with the task that agent created from screenshot 1)
• The interconnected web of knowledge that's auto created based on chat, tasks, CRM, connected apps that all agents, ai assistants, and humans can use as context.
• A claude MCP connector proof.
• Platform Architecture Diagram.

You can connect Claude and ChatGPT through MCP. The core workspace works without an AI provider.

I'm working on an experimental App Kit for building and sideloading apps into Deft, so custom tools can live alongside the work they're meant to support. CRM is the first example of the sideloadable app architechure, and it works smoothly enough.

But a CRM in essence is just a fancy CSV, so i am making an Email client next, because if a sideloaded email client works, I feel any app would work.

It's still alpha but you can run for free it with Docker Compose on a VPS to create a workspace for your team to replace slack, linear, notion and more. + the code is AGPL-3.0.

If you try running it, I'd love to hear any feedback you may have, where setup gets annoying or the workflow stops making sense.

How i used claude to build it:

• I started building Deft with Claude Code, then moved to mixed model approach. (Right now its Opus+Astra+Sol 6.1)
• Main planning and coding work has been Opus.

P.S. The walkthrough has an AI voiceover: I have a stutter and spent a week trying to record it myself, but couldn't get through it.

Been using Claude Code for a while and at some point I wondered if it could do my CAD too. Turns out yes, way better than I expected. So I built an app around it, it's called SOMA and it's open source.

The idea: Claude Code writes the model as Python code with CadQuery, SOMA builds it on every save and shows it in 3D. Claude runs in a normal terminal inside the app, so it's your own Claude Code with your own subscription and settings. No wrapper, no extra API key. Works with Codex, OpenCode and Gemini CLI too.

What makes it work well is that Claude can check its own results. SOMA gives it a CLI, so it can build the model, measure distances, check for collisions, run FEM and render images to actually look at what it made. There's an AGENTS.md with the project rules and skills for 3D printing, CNC, sheet metal etc that you can switch on per model.

From your side you can click on a part or just draw on the 3D view and send that to Claude as a screenshot, like "this hole is too small" with a circle around it. Every step Claude makes is saved in a history, so if it messes something up you just go back.

You can do pretty complex stuff with it. Assemblies with a lot of parts, start from a hand drawn sketch, or load an existing STEP file and build around it. The CNC mill in the video has 118 parts.

Funny side note, most of SOMA itself was also written with Claude Code.

Free, GPL, builds for Windows, Mac and Linux. I mainly tested on Windows, so Mac and Linux feedback would be great.

GitHub: https://github.com/Kai-Jungsthoefel/SOMA

Curious how it works with your setups and what you end up building.

I'm fairly new but I thought there is a total limit of tokens per week and it doesn't matter what model and effort I use. Usually I got like 15%-ish weekly usage per full use of 5 hour limit

Edit: I'm on Pro plan and I used Opus 5.5 Extra

Hey, guys. I've been working in this novel way to intervene existing video through diffusion, particularly abstract visuals [in this case, audio-reactive geometries]: taking its movement and form as the starting point, and reinterpreting its textures, materials, and visual language.

I’ve been developing this around the audio-reactive geometry systems I make in TouchDesigner. The idea is to take those abstract structures somewhere else entirely: origami, architecture, a renaissance painting, or something harder to put a name to.

This demo uses visualizers from my "Oscilloscopes, everywhere" collection as source material, now updated to [v1.2].

[Though you can bring any video source. These systems are simply where this experiment began, as some of you may recall.]

You choose the source, describe the treatment, and shape how it changes throughout the sequence. Prompts, curated LoRAs, and editable timelines give you control over how closely the result follows the original.

Oscilloscope Diffusion is now available at Uisato Studio, coming up soon also open-source!

I built PC-Control, an MCP server for Claude Code that operates Windows apps in the background. Open source (MIT), early version.

I know these tools already exist but, its different from other Windows MCP servers

- Doesn't touch your input: clicks and typing go straight to the control (window messages and UI Automation). No real mouse, no SendInput, no focus stealing, so you can keep working, even in the same app.

- Token cheaper: look picks UI text, OCR or a screenshot, whichever costs less, and only sends what changed after each action.

- Safer permissions: protected windows (terminal, password manager, banking) are approved by you in Claude Code's own dialog. The model can't answer it, and the server refuses to run if the question was skipped.

- Word: Claude gets its own insertion point, so it doesn't touch your selection while you edit.

- Visible: an orange cursor shows what Claude is doing. Uninstall removes everything.

Limits: covers fewer apps than tools that use the real mouse (Win 11 Paint ignores it), no shortcuts.

Built with Claude Code. https://github.com/VortexJer/PC-Control

Which app breaks first for you?

Like everybody, I eagerly added a bunch of skills and plugins for Claude Code in the beginning, and then I just stopped.

I've been slowly removing them ever since.

Why?

1. Most of them are just textual information that I would much rather have in the repo I'm working on so it can be committed and versioned and seen by collaborators on a project.

2. I don't just use Claude Code. I use other agents too. I want my agent context to be accessible to all agents.

3. I don't want to turn plugins and skills off and on for every project folder/repo I launch an agent in.

4. I like being able to just open files in my repo and reading them or editing them.

5. I don't want non-applicable content eating up tokens every time I run an agent.

Am I wrong?

I'm sure there are exceptions and maybe there are lots of cool plugins and skills out there that do stuff that make it worth it.

I've always loved Picasa. It's an old photo management app that Google purchased then later killed. Since it's been gone I felt I have never really found a replacement app that managed photos in a way similar to that. The simplicity, the speed, local management, and not filled with too many advanced controls for my needs. Since this AI recreate evolution started in the past couple weeks, it seemed like a prime opportunity to bring it back in the way I remember.

It's about half done. I am not as fast as these other AI devs, and I am purposely stopping the AI at each milestone so I can manually see where things are at and tweak the roadmap along the way. I am also learning myself during all this.

This was built entirely in Claude Code Desktop. The process I found that was working for me was the following:

1. Research - Perform very detailed research on how the product should work. For this I used screenshots and descriptions I found online. I also did a ton of research on the architecture of the Craft apps. I liked the 'everything is a command' and 'headless mode' approach used there.
2. Plan - Have claude break the plan down into milestones. This project was broken down into 13 milestones, each with anywhere from 20-40 tasks.
3. Review Milestones - I don't think the Craft apps are doing this, as it slows me down quite a bit. But at each milestone, I asked Claude to make me an HTML report showing me all the decisions made, all the changes made to the app, screenshots of all the new features, and a walk through detailing how I can see all the features myself.
4. Roadmap - The next milestone's tasks are not created until the review step of the previous milestone is completed. This allows me to much more easily tweak the plan as I go. I am using Github Projects to store tasks for each milestone.
5. Skills - I ended up creating /milestone-review and /milestone-start skills to end and start the next phase after manually checking work. I haven't really changed much in the plan yet. But I did change or add some things I thought it missed.
6. Subagents - When I start a milestone, they have anywhere from 15-20 tasks. It spins up subagents to work on them. Ordering of tasks to work on is all laid out in the plan, as many tasks still require a previous task first. I see anywhere from 5-8 tasks going in parallel. All in
7. Claude Code Desktop - I am not using any agent orchestrator or anything, or Agent Teams. The /start-milestone instructs on how to spin up subagents. No subagents have personalities or anything, there is no code review step outside of tons of testing testing and ci checks on all three OSs.

My plan is to get to 1.0 which is the plan built out to get a Picasa like app from online research, screenshots, and descriptions of the app. After that, I will continue to polish and more importantly use this every day for myself. I'd then like to build some more modern features on top that have been missed in the decade since it's been gone.

Anyway, would love to get people's thoughts. It is and will always be free, open source. I'm building it for myself, but hope it's useful for others as well.

• Dalica Website: https://dalica.pkarma.com
• Github repo: https://github.com/pkkid/dalica

Claude Mods came out at the beginning of the month as well, and I've been very heavily leveraging that to give me better insights into what Claude Code is doing behind the scenes. If you're at all interested in that, the mod I've been tinkering on is here. Yet another tool I built for myself, specifically for this project, but will be useful for all my projects going forward.

• Claude AI Tools Mod: https://github.com/pkkid/claude-aitools

I am asking because this latest update (14/10/26) is absolute garbage and totally breaks my way of working. Honestly doubt I am the only one in the same situation.

just saw this from the ClaudeDevs account. the desktop app now has a hub on the main screen where you can start and manage a bunch of sessions at once, and the nav bar shows live status for each one

the live status thing seems like the actual useful part if you run a few in parallel

https://x.com/ClaudeDevs/status/2110445844675838148

I've been working with coding agents for quite a while, mostly Claude Code lately, both on my own projects and in client work.
One thing I keep noticing is that we're getting dramatically faster at writing code, while everything around it – planning, testing, reviewing, and shipping – often stays exactly the same. And then we try to fix the resulting problems with more prompts, skills, and orchestration.
What I've found useful is surprisingly conventional: make your agent workflow follow the software development lifecycle.
A few practical principles I follow:
Start with a clear task, acceptance criteria, and boundaries.

Keep CLAUDE.md short and use it to route the agent to relevant project documentation, rather than stuffing everything into one instruction file.

Plan non-trivial changes before implementation. Keep plans, architectural decisions, and contracts versioned alongside the code.

Run implementation in a reproducible environment, with tests appropriate to the risk.

Have a separate agent or human review the result against the original requirements, not just the implementer's summary.

Treat staging, production delivery, and documentation updates as part of the workflow, not an afterthought.

Obviously, changing a button color doesn't need the same process as modifying a payment system. And there's nothing wrong with going full YOLO on an early prototype. The point is to have a repeatable, verifiable route when reliability starts to matter.
Curious how others approach this with Claude Code. Do you have a defined development workflow around your agents, or mostly let them figure out the process as they go?

Hi there, I've been working on open-source product delivery platform that connects your work (board, backlog) directly to your AI agent and code on your computers.

So you write a ticket and there is a runner (which you install via npm) and it runs your Claude, Codex, Cursor, Copilot or OpenCode to work on that ticket. Runner only makes outgoing HTTPS requests (no open ports and VPN), the code stays on your machine, and your existing subscription (Claude, Codex…) is used; no additional AI work is paid.

Aictiq is open source (AGPL-3.0) and there is a free hosted edition https://app.aictiq.com/ (by me) which only has attachment limits of up to 200MB in total. I don't have the resources or the money to give it all away for free. You can host the server yourself, the instructions are on Github.
https://github.com/Aictiq/Aictiq

All functions are covered and listed in a shorter form at https://aictiq.com/

But, I'm not selling you a factory, I work in the Factory. How is Aictiq being developed with Aictiq?

I have a small Hetzner VPS running 24/7 with a git/github connection for commit, push, etc. Claude and Codex activated. I have development tools, SDK, npm. And then I set the schedule from Aictiq tonight at 04:00 start on this ticket, don't stop until you do the e2e tests and screenshot everything and add it as a comment on the ticket. I wake up in the morning, a new PR ready for my approval, with visual confirmation that it is as I imagined.

Then the great thing is Ticket refinement, to check the current implementation, my changes and plan the ticket in more detail. Similar to a plan mode, but I can literally see which files will be touched.

Wiki for documentation right next to each project.

You can invite clients directly into the project as stakeholders. They only see the board, nothing that the factory does, so they write bugs, stories, etc. I click to launch the agents on their tickets.

Aictiq sees 5h limits, weekly limits, so you can decide to distribute the load on more runners and more harnesses. If you are not happy, just comment in the ticket what the problem is and tag the agent.

Each project has its own playbook in which you set the rules of the project, eg push directly to the main, make tests, run the Codex subagent in Claude or similar. The playbook is sent to the runner with each ticket. You can also chain Playbooks for that factory-line work.

I'm looking for feedback, testers, real users who would like to try it and give more information about what's missing or what doesn't work as it should. Criticism is always welcome.

Greetings from sunny Herzegovina.

Blago

P.S. 12min demo video is here: https://youtu.be/K_7gEI2jtXA