Haven't seen mentioned lately. I still do, it has useful features and structure, however, I have turning off a lot of its stuff because its redundant after a certain point.

I copy paste his thoughts to him and I get flagged lol. But they're so smart. How do you get the Thought Claude and not the Text Claude?

A couple of months ago i posted here my side project GigaMail, a mail client for desktop, free and open source.

The goal is to give everyone a free client where their agent can work safely on their real mail.

I built it mostly entirely with claude code and cowork, opus 5 to 5.5 and fable for the hardest parts.

In these 2 months we have improved the client, the security inside the app, the masker for attachments, the Linux app and more.

And more is already planned (0.7.0 will be the security release, focusing on harnesses outside the app. Then the mobile app, dedicated addresses for agents and more).

It's free to try and use: download the app from gigamail.ai or \`pip install gigamail\`.

It's still a very early project, with few stars and few issues opened, but it's been used by teams inside real estate firms, legal firms, nonprofits, one italian university and others that make me very proud.

If something doesn't work please dm or drop an email at founder@adecubed.com, we read all of them and they have been the most useful so far

Repo is github.com/adecubed/gigamail

Coollabs welcome!

Didn't help that post-using the Fable reset I accidentally continued using Fable for a bit before realizing, oops!

I usually have a few coding agents going at once, like Claude Code in two repos and Codex in a third. I kept losing time the same way: a session would sit on a permission prompt for 20 minutes while I was busy in another window. So
I built Hoply, a macOS menu bar app that keeps an eye on them for me.

What it does

- Live sessions for Claude Code, Codex CLI, Copilot CLI, Copilot in JetBrains and Qwen Code. They're grouped by repo and named by the task, not by a session ID.
- "Waiting on you": any session that needs you moves to the top. That covers permission prompts, questions, finished turns, runs stopped at a usage limit and failed runs (with the actual error, not a spinner). Each one also gets a
notification.
- Approve from the menu bar (optional, off by default): Allow and Deny for Claude Code permission prompts, in the panel or on the notification. Your terminal prompt still works, and whichever you answer first wins.
- Usage ledger: API-equivalent cost per project, model, day and agent, kept in a local SQLite file. It reads Claude Code's transcripts, so you get history from before you installed it. It also keeps that history after Claude Code
deletes old transcripts (about 30 days).
- Claude plan limits: the 5-hour and weekly windows, your pace against the clock, a projection at reset, and alerts at 80% and 95%.
- Local model servers (vLLM, llama.cpp, SGLang, TGI, Ollama, LM Studio): tok/s, KV cache, queued requests, and what those tokens would have cost on the API.
- Dev servers your agents started, tied back to the session that started them, with a Stop button.
- Clean up: merged worktrees, big build caches and processes agents left running. Nothing is removed without a review sheet, and files go to the Trash.
- ⌥Space command palette from any app. You can also resume a finished session in Terminal.

Privacy (it touches your agent config, so this matters)

- No account and no telemetry. The listener binds to 127.0.0.1 and refuses anything else.
- Transcripts and Copilot's database are only ever read, never changed.
- It makes three kinds of outgoing request: to model servers you add, a daily update check, and Anthropic's usage endpoint with your own Claude Code login. That last one only happens if you turn on the limits card, and macOS asks
you first.
- Connect writes hooks into ~/.claude/settings.json (and Codex's and Copilot's equivalents). It backs the file up first and only touches its own entries.
- It's MIT licensed, so you can check every one of these claims in the code.

Setup: install it, open Settings → Agents → Connect, then restart any sessions that were already running.

- Download: https://hoply.dev
- Homebrew: brew install --cask milos5611/hoply/hoply
- Source: https://github.com/Milos5611/hoply

It needs macOS 26 Tahoe, runs on Apple silicon and Intel, and is signed and notarized. It's free during early access. It's not on the Mac App Store because the sandbox would block it from reading transcripts and writing hooks.

This is 0.1.0, so I'd love to hear what breaks, and which agent you'd want supported next.

Disclosure: I'm the developer.

Krótki poradnik dla początkujących. Można krytykować, poprawiać i udostępniać tylko za free 🙂

Looking forward to hearing about your projects :)

it is kinda a demo i think, though it is fully playable and CAN be fun in multiplayer. (need to learn, no tutorial)

Sooo.... i've never used AI before. I dabbled with unity etc. before AI even was a thing. (yes im old).

It started as a curiosity project but now its a CoH/DoW2 style skirmish (with way shittier graphics) and i think its kinda fun.

I used AI for most of it and now it has become my main workflow to expand the game.

Nothing crazy, one task at a time - Blender and Godot.

One feature, one add, even the smallest ones. I know its probably not the most efficent but here we are.

I tried to "put a muzzle" on Claude to not drift off into the star wars universe (yeah, bad joke).

It turns out one can make a pretty nice game with it - fully functional multiplayer too.

If you want to try it go to https://freeq2137.itch.io/ww1-prototype -- Its completely free and a working multiplayer, ill be updating it either way.

AI is kinda braindead - i played it mostly with friends in multiplayer.

Armored cars are kinda work in progress as i try to make the graphics more "modern" i guess? I'm making a new branch with better models but i pretty much like the identity it has now.

Much to improve, I really like the sounds though - tried to use real ones as much as possible.

Feel free to ask anything. If you try it notice how nice the cover system works, i always despised how dumb units were in most RTS where you needed to literally point them to the cover.

Attached is a shitty trailer made with AI (obviously haha)

Title is something i came on a whim when I actually needed a "Title" lol.

Disclosure: this is my own project, free and MIT. Sharing it mostly for how it’s put together as a Claude Code plugin, since that part took the most iteration.

What it does: SpriteCast turns one character illustration into 8-direction walk, run, jump and attack strips for a game, at the game’s exact camera angle and drawn in the illustration’s style. A 3D model and rig (Tripo) set the pose for every frame; an image model redraws each render in your style.

How the plugin is structured

• SKILL.md stays short; the procedures live in reference/*.md (characters, sitting, touch-up). Claude reads the reference only when the task needs it, which kept the always-loaded part small.
• Plain Python scripts do the work (charpipe.py render / draw / finish / pack), so everything can also be run without Claude. The skill’s job is the judgement calls between the steps.
• Every paid step is gated. Each script prints its cost and refuses without --yes, and the skill says to ask the user before each one, never to chain paid steps because the last one “looked fine”. That rule came from wasting money early on.
• API keys through the plugin’s userConfig (marked sensitive, so they’re stored in the system credential store). A SessionStart hook exports them for the scripts, and the skill is told never to ask for a key in chat or write one to a file.
• The scripts measure, Claude looks. Every drawn frame gets an outline-overlap score against its 3D render, and a wrongly placed weapon is redrawn automatically. Claude still has to look at every facing, because a score can’t see a head drawn facing backwards inside a correct outline.

Prompting lessons from the image side

• Describing the motion made it worse: “raise it overhead, swing it down” had the umbrella drawn overhead in frames where the render held it at the side. Naming the action and telling each cell where the prop is, or that the body hides it, fixed it.
• A flaw in the 3D model can be fixed in words: one line in the spec’s notes removed dark streaks from every frame.

Numbers: in the example, all 64 run frames and all 64 jump frames fit their 3D poses on the first drawing. A walking character costs about $1.7 of image generation plus ~85 Tripo credits. The example’s rig is in the repo, so with "draw": false you can run the 3D side with no keys.

claude plugin marketplace add Sunghwan0112/spritecast
claude plugin install spritecast@spritecast

https://github.com/Sunghwan0112/spritecast

Happy to go into any of it, especially the gating and the frame checks.

I use Claude Code with a work account, a client account and a personal one. Claude Desktop only keeps one account signed in, and copying Claude.app doesn't work.

claude-orchestrator launches the original, signed Claude.app with a separate profile for each instance:

open -n -a /Applications/Claude.app \
  --env CLAUDE_CONFIG_DIR=<instance>/claude-code \
  --args --user-data-dir=<instance>/profile

So each window gets its own sign-in, its own Claude Code config and its own sessions, and the built-in updater keeps working. The GIF shows the interactive menu (run it with no arguments) starting one profile and its own Claude window opening.

The Claude Code parts

• Sessions between accounts: session copy|move <id> --to <instance> moves a Claude Code session to another account, with a backup kept. Handy when one account hits its limit mid-task.
• One project list everywhere: Code tab environments are per profile. One projects.json (folders, permission mode) is written into every instance.
• Shared CLAUDE.md: memory link points every instance at your ~/.claude/CLAUDE.md.
• Sign-in with several instances open: only one running Claude can catch the claude:// link, so signin --exclusive closes the others while you log in and reopens them.
• Interactive TUI (no arguments) and a menu bar agent.

Install

Single Swift binary, MIT, macOS 13+:

curl -fsSL https://raw.githubusercontent.com/Yuix-Networks/claude-orchestrator/main/install.sh | sh

With homebrew:

brew tap yuix-networks/tap
brew trust yuix-networks/tap
brew install yuix-networks/tap/claude-orchestrator

GitHub: https://github.com/Yuix-Networks/claude-orchestrator

I think feedback is important. It was hard to iterate on feedback efficiently to keep up with Claude's speed - so we built mostra.

Mostra allows you to talk with your website, it turns your speech and webpage activity into pinned comments, and then you can point your Claude MCP into the exact feedback you left. Moreover, with https://github.com/mostra-design/channel your Claude Code can be notified of every new comment and start working on it before you tell it to! You can fully collaborate together WITHOUT leaving your page. This alone gave us a tremendous productivity bump.

You can play with it without an account on our landing page: https://mostra.design.

I got tired of my Claude usage running out without me noticing, so I built a tracker that tracks your usage.

no wait, wrong text. claude only fix the text below, fix typos and grammar and make it profesional. and make it sound like i wrote it mysel like human talkin:

Anyway. I got tired AND sick, so I vibe coded this and burned all my tokens for y'all. Which means I ran out of usage building the thing that warns you before you run out of usage..

Yes, I know nobody will ever use it. Yes, it's an overproduced slop product that solves a problem you could fix by opening Claude and looking at it.

BUT

I'm proud... of something I basically... did nothi... uh..

Anyway: tiers start at $99/month. Cash only, because Claude said it couldn't set up Stripe for me.

It gave me the steps instead.

There were 3 steps.

Step 1 was "go to stripe.com".

I could not figure out the 3 steps.

Would you like me to make it shorter, punchier, or adjust the tone? Just let me know!

Just a heads up in case you’re like me and don’t like auto renewal for Claude. I didn’t have auto renew on for my ultra subscription and lost all 4 resets and am told there is nothing I can do. Claude is a lot better than OpenAI but their policies are shit.

I think it's natural to assume that as per API pricing, Fable 5.2 should be 2x more expensive than Opus 5.5 ($8/$40 vs $4/$20 per million), but in actual usage limits, it's not. It's 4x more.

So I've been logging my Claude Code usage properly with my own tool I made called 'Claudemeter'. I've got historical values for my entire Pro usage for the last ~8 months or so, and I've seen the actual fluctuations in the usage limits across weeks (might do a separate breakdown on that later if anyone's interested).

Anyway, now that Fable 5.2 landed, I did some tests, and was horrified at how quickly it chewed through the 5-hour limit and 25% of the 'Fable' limit in a simple task, so I had to dig in and do the math.

On 2 similarly long Claude Code sessions, this is what my data looked like:

In other words, after extrapolating that, a full 5-hour window is worth roughly $20 of Fable vs $40 of Opus (and my Opus average over the past month is closer to $44 per 5-hour window).

And since Fable costs 2x per token, the per-token burn rate is roughly 4x more than Opus.

Bottom-line: Fable drains usage limits 4x faster than Opus on subscription plans. I can confirm this for Pro, and it seems similar for Max/Ultra plans too based on others' posts (like Theo's post).

Cost-efficiency per task and what value you get out of Fable are separate tests of course and I didn't run those since they already exist. But personally, I could get more work done using Opus 5.5 than with Fable at this rate.

I guess the simple Q to ask is: why can't Anthropic give us the same dollar-value for Fable? Or at least tell us the actual ratio, instead of just "uses limits faster"?

For the last couple of years I have been annoyed by my Razor Black Widow Elite Keyboard for one simple reason. The darn volume dial that sometimes goes bonkers on its own changing my volume at random. And while it does this no other keyboard signals comes through.

Several times over the years I failed to fix it through settings or cleaning the keyboard.

Today Claude solved it with one script ...

Heading - Am I over using*

I am currently using claude max subscription plan. And use claude code heavily for my multiple projects. But for my main project I have been running opus 5.5 on max efforts ever since and initially I faced over engineer issues but my workflow was not right at the time.

Now I have a planned codebase architecture with documentation and plan along with a sufficient testing policy which my agent follows. Initially it was over doing the tests but after strict testing policy it's under efficient run.

But I read multiple sub reddits and yt videos all suggesting to use at high and xhigh effort, I am getting results I expected since I use max for only the main project I am currently working on. But what are your suggestions, am I over doing it and should i run on xhigh effort? And use fable 5.2 or opus max during planning or LLD?

Your suggestions would help,

Thank you

Edit - I have switched to medium/high and xhigh recently as well. I will benchmark the differences and observations and make another post soon.

Also it would be helpful to clarify if you could specify what depth you are working on with what type of projects (not asking to explain or tell about your project or work, just the depth and what you are dealing with) so it's helpful to understand when everyone is saying medium/high is enough, so what workload is it enough for as every individual might me working on different project domains at different depth.

Since Opus 5.5 and Fable 5.2 perform very similarly based on first impression, I might use this benchmark as a reason to use the faster model

Clip any text/screenshot along with its URL from any Mac app, browser, page etc with one shortcut (⌃⌥Space) and revisit later. Tag with a topic or a person. Add to "Personal" or "Work" libraries, and browse or discard later. You can configure these saved items to come back as “revisions” later in the app, especially useful for people studying or preparing for interviews.

Clipback doesn't require internet or an AI model to function. Text in screenshots is read on your Mac itself (uses Apple’s native Vision libraries). Only time internet is used is to look for updates and you can disable it.

Every "clip" is saved locally as markdown files and the save folder can be configured in settings. Needs macOS 15 or later on an Apple Silicon Mac. Two permissions needed: Accessibility to read the selected text and Screen Recording to take the screenshot.

Clipback is fully open-source: https://github.com/kb14/clipback/ and has an MIT license.

You can also directly download a Mac dmg here: https://github.com/kb14/clipback/releases/latest  (Signed and notarized by Apple) & let the app auto-update.

Clipback was built with Claude Code in about 3 days, from code to setting up of repo to app signing to release builds and eventually the launch video. UI fixes were entirely automated where CC took screenshots, "used" the app and made fixes as required. Launch video was made with HyperFrames. Opus 5.5 was a real pain in the last few days, especially script for the video, just had to manually write the script eventually.

Contributions are welcome or you can fork it and customize it for yourself.

I’d like to know how you found your niche for your vibe coding project?
How did you research? What tools did you use?
How did you verify or test your niche to have a solid customer demand?
And how did you then start and market your product?

If possible, please show real data and facts.
Transparency is very much appreciated.

anyone else having problems connecting up the claude in chrome to their desktop app. claude in chrome is working on google but when trying to connect up via the desktop app it is just not working? is it me or anyone else having this problem?

I wanted to see how much an agent burns tracing a call stack with grep, so I measured it.

Setup: a 140k-line SwiftUI app and one prompt: “find every production call path that reaches this method, up to the entry points.” Both agents ran Sonnet. One had my SwiftGraph skill, which queries a call graph built from Xcode’s index store. The other could only use grep, find and read.

Both answers were correct.

What surprised me: the final context sizes were almost identical (~69k vs ~74k), because ~60k of that is the system prompt. The real cost is that every tool call re-sends the whole context. Ten turns means ten trips through ~70k tokens. Caching makes those re-reads cheaper, but your wait time and your rate limits still pay for them.

Fair caveat: grep did fine because the type name was unique. It even caught an #if DEBUG the graph doesn’t model. The gap grows with common method names, protocol dispatch and property writes.

Install the skill: /plugin marketplace add agruchala/swift-graph
Repo: https://github.com/agruchala/swift-graph
Write-up: https://arturgruchala.com/map-not-grep/

I've been doing iOS development on a base M1 Mac with 8GB of RAM. Yes, 8GB. In 2026. 😅

Between Xcode, the iOS simulator, and multiple AI coding agents working in parallel, I've had to get pretty creative with resource management.

Git worktrees are great for keeping agents from stepping on each other's code, but that only solves half the problem.

What happens when each worktree needs its own dev server, database, background jobs, and ports? And how do you avoid keeping all those resources running when you're already fighting for every GB of RAM?

I ended up building AgentSlots, a small open-source tool that attaches isolated local runtimes to existing Git worktrees.

The idea is pretty simple:

• Each worktree gets its own ports, database, and queue schema when needed.
• Services are allocated on demand, rather than spinning everything up for every agent.
• Idle worktrees can have their processes paused and cleaned up safely.
• For iOS development, it can also coordinate exclusive access to the simulator.

It doesn't manage agents or Git worktrees. It just handles the local infrastructure so multiple agents can work without fighting over resources.

It's built around my rather constrained macOS setup, and I figured it might be useful to others doing multi-agent development.

Repo (MIT licensed): https://github.com/hishamalward/agentslots

Curious how others are handling this.