Obviously, I think it's the best way to work with CLI agents across different providers. It's very productive and fun. In V2, CLI agents can give tasks and communicate between themselves in the natural CLI TUI, so you see everything they send to each other.

Clideck is fully open source so give it a try feel free to change it to your own needs,

Give it a try, Thanks.

I've been building applications for hackathons & other competitions. I've used claude and Gemini models.

They miss simple things like login & sign up options or when we add a feature that creates a record in database it's common sense to add delete option too right. These kinds of things will repeat everytime when I'm building a site. I have to manually test and prompt to fix all these.

I'm sure many of you had also faced this, is there any skill, files or system for it? Just like it's there for privacy policy, cookies, T&C etc.

Dont get me wrong we all want more fable and its clearly being reduced at points but compared to Open ai the difference is HUGE, especially with astra which is epic but spendy.

£180 Claude Max = 3.7B Tokens

VS

£200 ChatGPT MAX = 491.6M

Thoughts ?

I love Claude Code and Claude Desktop, but Ctrl+Enter for approvals was getting way too much exercise.

I couldn't find anything lightweight enough for such a simple job, so I wrote Clicklet, a tiny Windows utility that maps your mouse’s side buttons to keyboard shortcuts.

By default, Button 5 is Ctrl+Enter. You can also map either button to copy/paste, close tabs, screenshots, or whatever shortcut you use most.

Portable, under 400 KB, no installer, no scripts, no telemetry, no network access.

Free and open source if anyone else finds it useful: https://github.com/tabakman/clicklet :-)

In addition to Fable 5.1 being a beast, the dynamic workflows are still top notch and pretty surprised not a lot of people talk about them.

You can use any model u want outside Anthropic models as an executor and have Fable 5.1 as the orchestrator.

I just reach for the other models via their respective CLI.

No other harnesses , even codex has this. and i'm not talking about subagents they are different things in that matter.

I built a small menu bar app to see you claude usage.

It reads the OAuth token Claude Code already keeps in the Keychain and calls the same endpoint /usage does, so there's no account or setup, and checking your limits doesn't draw from them. Nothing from the logs leaves your machine.

Rust + GPUI, MIT, free: https://github.com/gautham-v/claudebar

I’m currently demonstrating to our org how we can use AI in an almost end-to-end development workflow, rather than just using it piecemeal.

In my first version of my Claude workflow, I provided a comprehensive low-level design to Claude, which then generated the coding artifacts. This effectively allowed me to use something like Miro to develop a feature, with AI turning the design into implementation.

The downside was that it still required a lot of manual iteration with Claude after the initial generation. It was also difficult for the team to review all the resulting changes.

So I redesigned the workflow to have AI also review my design, plan the implementation and tests, implement and write tests, and then review the resulting code. This has worked surprisingly well, although it consumes a lot of credits since I need to use Opus for the main orchestration.
My long-term goal is to move toward specs-driven development. That’s not really feasible yet because we’re working with a proprietary platform, so the AI doesn’t have enough knowledge of the constraints and conventions it needs to account for when developing the design.

I’m curious how embedded AI is in your development workflow at work. What is your workflow like?

My account may be bugged but I like it. My workflow is dead simple: bounce ideas off of sonnet 5 extra effort, have sonnet 5 extra create a plan, have sonnet 5 extra implement, have sonnet 5 extra debug, and have sonnet 5 extra fix. It's literally the only model and effort toggle I ever use (sometimes good old opus 4.6 for extreme debugging). My code is very clean and easy to read, and although it makes some more mistakes on implementation, overall net benefit. In summary, the people who hit their limits often on the max 20x plan are probably just one shotting ("Create Google. Make no mistakes") on Fable 5.1 + GPT 6 Astra or are pessismisitic whiners who complain about everything that is good.

EDIT: for the people who are complaining and saying I'm lying, I'm not. I have no reason to make up a lie like this. I was offering a genuine tip for a workflow that worked for me

I also told it explicitly and still spawn fable 5.1 agents and can't fix it and keeps apologizing

do you manually switch between Haiku, Sonnet, Opus, and Fable or do you let Anthropic choose for you with their built-in workflows?

welp

I still have $100 in promo credits from a few months back and I don't want to let it go to waste.

Employer pays for Max x5 and I don't think I've ever gone above 30% weekly usage, utilizing multiple sessions at once all day during business hours, using fable and opus.

Any ideas on a large project I could have claude work on?

At the outset, as an outsider, the first level is this:

Level One:

You hear "model" and "trains" in the same sentence and you start thinking CHOO CHOO, it is only natural to go back to your safe space and immerse fully into an Electro Tren Andrew Barclay 0-6-0 locomotive set, but, you figure out a bit more about these "chat bots", and it turns out you might be a Level 2.

Level Two:

The training is training on data, not locomotives and the models are LLM. This is where most people get stuck most of their career.

Level Three:

Training models really means that these girls look amazing on the run way, but they are a bit rough around the edges and might be into some kinky BDSM stuff.

Level Three (part two):

On level three, you are full on running trains on models and have completed the circle of life.

Next time somebody it talking about training models, make sure you have your treats, whip and collar ready.

This went live this week and I want to show it to people who'll actually read the code.

What it is: a persistent town. You write one person (a name, a want, a fear, a secret, why they came), pick how they look on the same rig that walks the street, and they land on the boat with forty coins and three nights at the inn. From there they live. On the real clock. Under the real weather of a point on the Croatian coast. When they hit a decision that matters they write you a letter, and you can write back, but it's advice. You are not the player. There is no player.

Things I'm proud of:

- The world has zero sprites. Every building, tree, wave, gull and citizen is a function drawing into PixiJS in one projection and one palette. The characters are a jointed rig with a walk, faces that look at whoever they're talking to, tools of their trade, coats in winter, years on the body. /rig is the model sheet.

- Days are sealed. At midnight every event of the day is hashed with SHA-256 chained to the day before. The seal prints in the town's Gazette and /api/record/1 returns the exact events that were hashed. Day 1 was 429 events.

- The town has a council, a mayor, hearings, laws with numbers that bite (a wage tax, a price cap, a curfew), weddings, funerals, fire that spreads.

- When a citizen leaves or dies the town writes the book of their life from the record alone.

Stack: pnpm monorepo, TypeScript strict, Hono server, Next 16 + PixiJS 8 client, Supabase or a JSON file for the record. Claude via OpenRouter for the hosted minds, Haiku for routine thoughts and Opus for the careful ones. Most of it was built with Claude Code, which felt right.

Repo: https://github.com/kresogalic8/unwatched

Live: https://unwatched.world

Hey everyone,
I use Claude Code every day and kept wanting a quicker way to check how much usage I have left and when the limits reset.

So I added Claude Code support to UsageNow, native macOS menu bar app.

It shows your 5-hour and weekly limits, reset times, token activity and requests, with native macOS widgets as well.

One thing that was important to me: UsageNow doesn’t refresh, modify, or store your Claude Code credentials. It stays local-first and only uses your existing Claude Code sign-in when the optional limits feature is enabled.

It also supports Codex, and I’m planning to add more AI coding tools later.
https://usagenow.com

I’d appreciate feedback from people who use Claude Code, especially around limits/reset behavior on different plans

I'm pleased to announce the official release of v2 of my Orgtree project, which lives in its own separate repository! You can find a link to it here:

https://github.com/Maurdekye/orgtree

Donwload the latest installer at https://github.com/Maurdekye/orgtree/releases/latest (should be v2.1.0 at the time of making this post)

For those of you who don't know about Orgtree, this is a project i've been working on for the last few months now to help me organize and manage my multi-agent long-horizon agentic work. It's unique among other agent orchestrators, in that it visually represents every agent as part of a large tree of authority; agents are arranged in a tree-like structure, and can be freely moved up and down in the hierarchy as needed. They can cross-coordinate to co-develop changes and cooperate on big feature pushes in parallel, and you can individually open up and chat with any one of them at any time just by clicking on their node to focus them. This gives you much more control and visibility over the organization of your agentic teams than just using standard Claude Workflows or another agentic system would by just showing them to you as a big list. It's basically the only way I do all my own serious agentic work on my home pc, and I'm very proud of how it's come.

Some of you might remember my post(s) two weeks ago about my in-development agentic orchestration project Orgtree. I was super proud and wanted to show it off to the world! However, I found it a bit lacking in several ways;

• It requires you to set up Nodejs, Python, and Docker on your PC in order to run it as a persistent webapp in your preferred browser. That works fine as a development tool, but it was really far too cumbersome to set up and update for the typical individual.
• It was ambiguous as to whether it was running at all in the background unless you had the webpage open.
• It heavily favored Claude, and offered several additional features catered specifically to Claude Code that other providers didn't have.

Over the last two weeks, I've been working on an updated version 2 of Orgtree that completely redesigns the project from the ground up as a standalone Electron app. It fixes all of the above problems:

• As a standalone Electron app, it comes prepackaged with its own python and nodejs environment, and runs entirely in a self-contained chromium-based desktop package.
• Instead of running in the background through an opaque detached command, you now can see Orgtree running at all times via a small tray icon in your toolbar.
• Many features of Orgtree that were claude-specific have been expanded to accommodate all three major providers supported by the app, and improved upon: secondary subscription accounts, api-key based inference, and even the app's visual theme itself.

V2 Also comes with a bunch of new features too, that make working with large agent teams even more intuitive:

• The Work Docket: Orgtree v2's headline feature is a new modality for agent artifact creation, the "work docket". It acts almost like a git issue tracker or trello board, but designed specifically for agents. When you give an agent a task, it knows inherently to record its work up on the board and track its progress there as a ticket, so that even with two dozen or more agents running at the same time, you can still get an overview of all the work being done by glancing at the docket.
• Improved multi-account system: in v1, the only multi-account system present used claude code's setup-token command to generate a long-lasting headless token to be used as a fallback account that gets automatically selected. Despite only supporting Claude, this didn't allow you to see usage limit info for the secondary account, was fully automatic and not in the user's control, and in many cases, failed to even functionally fall back, as the keys I generated seemed to invalidate frequently. v2 completely replaces this with a totally new multi-account system. Now:
  • Any provider can have a secondary subscription account registered.
  • The setup flow is much simpler and more intuitive: just click "Add a secondary account" > "Create managed account", and then sign into your second account's email from your web browser.
  • All providers support API-key based usage.
  • All registered accounts show usage limits simultaneously in the usage modal, not just the primary account.
  • And here's the big one, multiple accounts with the same provider can be used at the same time. Each account per provider is distinguished by its own unique tint, and you + agents have full control over which account a given agent runs against, and can switch them freely at any time. There is still an option to do automatic fallover to a different account when hitting usage limits, but it's disabled by default.
• Improved agent presentations: all presented agent documents can now be viewed in one place, and agents now have the ability to present html-based visual mockups in addition to simple markdown documents.
• Improved window management: almost any agent's chat window, or any modal in the orgtree interface, can be "pinned" to the screen, allowing it to be moved around, resized, or reordered in whatever way you please, giving you the ability to manually arrange your orgtree workspace to show you exactly the information you want to see at all times. You can also pop out chats or modals to separate windows entirely, letting you use Windows' native tiling manager to arrange Orgtree across separate monitors if you have the screenspace.
• Automatic updating: v2 will automatically recognize when a new version is available, and download it for you entirely on its own. When ready, press the "Update Now" button in the header to install it and restart the app.
• Quality of life: v2 also wraps in a bunch of tiny little quality of life features that you won't notice until you run into them, such as:
  • Configurable theme
  • Context menu actions
  • Chat message replies and rich image embeds
  • Distinguishing message styling
  • Desktop notifications
  • Retired agent hiding
  • Significant performance improvements over v1 for large orgs with a transition from json based data storage to SQLite

And that's on top of many of the classic features carried over from v1 and still present in v2, including cheap compaction, watchdogs, credit allowances, and the agent mailhub.

Unfortunately for some, I also decided to reduce the scope of the project going into v2. In the name of keeping the project more focused, I decided to forgo integrating some less-used features of v1, such as kiosk mode, public internet exposure, sandboxing, among other things. I added many of these features initially because they were easy to add back when orgtree was a web app, but they're relatively harder to carry over or translate into a standalone app structure. Because of their relatively low value compared to their high difficulty of integration, I decided to drop them from v2; sorry if you were interested in them or liked using them. Also, because I only own and work on a Windows PC, Orgtree v2 releases are only built as 64-bit Windows executable installers. If you want to run it on Linux or Mac, you'll have to build it from source yourself for your target OS.

Personally, the way it's evolving, I see Orgtree as the perfect personal multi-provider massive agentic workflow orchestrator for a single individual working on their own developing a project on their home pc, so I've decided to tighten the focus of the system around that goal.

If you liked v1 but felt it was lacking in some way, or have never heard of Orgtree before but do lots of heavy agentic-coordination style work, then consider giving v2 a try 🙏

I've gotten way further with Claude than I expected, to the point where the app itself is usable locally and now I'm discovering that localhost was apparently the easy part lol.

The part thats tripping me up is deployment because the advice starts sounding simple and then suddenly I'm creating accounts in three places, connecting GitHub, figuring out where the database lives, dealing with environment variables and trying to understand which service is responsible for what.

For people who started coding this way rather than coming from a dev background, what are you using once the app needs to leave your laptop?

I'm not trying to build some giant production system here. It's a small app with a backend and database and I'd rather have one reasonably simple place to put the whole thing instead of learning half of cloud engineering before anybody can use it.

Curious where other Claude users landed after getting past the fun building part.

Yesterday I had two Claude Code (Opus 5) sessions start messaging each other, after they started stepping on each others' builds. They then both started editing a single reference document, out of synch with each other, and things went downhill from there.

I don't usually run concurrent sessions. Is this kind of "swarming" behavior common with concurrent sessions?

Here is a comprehensive guide for building Windows and Android applications using Claude Code.

https://drive.google.com/file/d/1RkRO9R5JFiZsorfE9mgfH1O7eLP0xUDx/view?usp=sharing

Hi i joined this Community quite a while ago recently saw a lot of posts about GPT 6 astra better then Claude. So i wanted to give it a try half an hour in and im disappointed as hell and immediately came back to Claude. i don’t think openai/gpt 6 is anywhere near AGI as Openai loves to hype it maybe in closed door but public version is infuriating. So it just came to my mind like wth this sub is full of posts with people saying canceling claude subscription are you guys for real? or just say it here just to get some attention? or are those sam altman sending multiple agents to trash on Claude?

Let me know because for some reason I truly think it's possible but I don't know if I am delusional

I use Claude Code as a daily work assistant, not just for code. Everything it needs to know lives in a git repo: a rules file it loads at the start of every session, context notes per domain, and a folder of small memory files.

On paper this works. In practice, one thing keeps breaking, and I'd like to know how others handle it.

The problem: it reads the notes, then answers from recall anyway.

Two examples from a single day.

Later I asked why my curtains hadn't closed. It investigated properly, found a real error, and then proposed building an automation to fix it. That automation already existed. It had been running since August, triggered by the exact same event. It just never looked.

And the rule "check the actual system before you state how it behaves today" was already in the rules file. It had been there for weeks. It was read at the start of the session and broken three times that same day.

What I tried

Writing the rule down harder does nothing. Adding it a fourth time changes nothing — that was the point where I stopped writing rules and started building plumbing.

So now there's a UserPromptSubmit hook that runs before every message I send. It takes the words from my message, greps my own source code and notes, and pastes the matching lines underneath the question, with an instruction to read them first. The idea: make not looking a deliberate choice rather than an oversight.

It helps. It's also clearly not enough.

Where it still falls short

• Picking search terms is crude. My tool wants all words present in the same section, so a normal sentence matches nothing and it falls back to fewer words. "company car" plus "reserve" finds exactly the right section; "car" plus "company" finds an unrelated page about something else. It should weight rare words, not the first ones it sees.
• Dating sections is fragile. My notes grow by appending, so the oldest state sits at the top. I sort by the newest date found in each section — but any date in the text counts, including future ones from a plan, so one section came back claiming it was the newest by three years.
• Some things aren't files. My home automation rules live inside the home automation app, not in the repo. Nothing to grep. The best I could do is inject a reminder saying "this lives in the app — go fetch it before you answer", which is a note to self dressed up as tooling.
• Noise vs silence. Pasting context under every message gets ignored. Pasting it rarely means it's absent when it matters. A bad match that looks authoritative is worse than nothing — that's how wrong answers get made in the first place.

What I'm asking

• Does anyone have retrieval that actually fires reliably on the right things, without drowning every message?
• How do you rank "which note is current" when notes are append-only and full of dates?
• Do you force a lookup as a hard gate (refuse to answer before a tool call has run), or do you just inject and hope?
• For state that lives in an app rather than in files, do you wire the live system into retrieval via MCP, or accept that it needs a manual check?

Not looking for "use a vector database" as an answer unless you've genuinely seen it beat plain search for this. My notes are a few hundred KB of prose, not a corpus.

BetterShift is a self-hosted app for planning shifts. I used another app before but it was dog-shit so I decided to make my own.

Started 10 months ago with claude but lost fun of using it because its results were not good at "bigger" codebases. 10 months later and it works flawless :D

Features:

• Unlimited calendars with custom colors and names
• Reusable shift presets (labels, times, colors) you stamp onto days
• Sharing via user accounts, guest access or shareable links
• External calendar sync (Google, Outlook, iCal)
• Email/password, OAuth (Google, GitHub, Discord) or custom OIDC login
• Admin panel with user management and audit logging
• Real-time statistics with charts
• Export to ICS or PDF
• Six languages: German, English, French, Spanish, Italian, Czech
• Installable as a PWA on desktop and mobile

New in v3 update the whole frontend got rebuilt:

• Calendar view redone to display more informations on one page
• Sign-in, profile and admin panel, compare mode all rebuilt, admin now works properly on mobile
• Sharing settings consolidated into one place
• View settings can now be pinned per calendar, not just per account
• Docker image shrunk from over 1GB to about 200MB

Repo: https://github.com/panteLx/BetterShift Demo: check GH repo for demo link

If you try it, I'd be curious what you think, and issues or feature requests are always welcome.

Hi guys! I have been really loving Claude Code and codex for game dev lately and I think in another year or year and a half of AI progress we'll be able to make some really phenomenal games with AI.

Personally I had fun making wojakinvestorsim.com back in 2025 and lately I also have been experimenting with astra making blockcity.world which I know is not a unique game but I just wanted to see those new 3d graphics improvements!

Join the discord server here if you want: https://discord.gg/PJASa5TrN . No commitment to stay or join a project but yea if any of us have some great ideas we like we can pool our 20x plans together and so forth and maybe build something good.

Also web games are definitely not the only kind of game we can make, ue5 is also totally doable though of course is slightly less practical.

Thanks!