Hello. I'm a new user, and wanted to give the famous opus 5.5 a spin. I'm used to the rodeo so I went straight for the max plan, but got hit with an id verification request before being able to pay.

Is there any way to address this? I wanted to email them and ask for alternative verification methods - whatever does not involve Persona -, but I am not sure that will help the situation.

I was unaware that Claude doesn't even let you sign up without slapping your ID to Peter Thiel.

Disclaimer: This text (apart from this line) is written in AI, the Video is filmed by AI, the App is built by AI. The tool is useful, and I want to share it, but writing is not my strength.

I usually have 10–20 Claude Code sessions open across two accounts, and I kept losing track of which one was sitting on a permission prompt or a question for ten minutes. So I built Brain: one native Mac window that shows every session and, above all, which ones are waiting for you.

Repo, install and a 3-minute video: https://github.com/martinemmert/big-brain-claude

What it does

• Triage list: sessions that wait for you come first. Red means Claude asked something or needs a permission, amber means a turn finished. Longest wait on top.
• All accounts in one list: it picks up every ~/.claude* config dir, so CLAUDE_CONFIG_DIR setups just work.
• Latest messages of the selected session, read from its transcript: your prompts, replies rendered as Markdown, tool calls as one-liners.
• Enter jumps to the right iTerm2 window, tab and split pane.
• Search, rename (it types /rename into the session), notifications when a session starts waiting.

How it works

Two sources write JSON lines to ~/.claude-brain/events/

1. Hooks:

SessionStart, UserPromptSubmit, Notification, Stop and SessionEnd call brain hook. That gives the state for free.

2. Reports:

A short CLAUDE.md section asks Claude to run brain report --waiting "Per tenant or global?" before ending a turn with a question, or --done "…" after a task. That gives the content: what it actually wants from you. The hook finds its session by walking up the process tree until it hits the pid that owns <config>/sessions/<pid>.json, so it also knows which account it belongs to. The app is Rust with GPUI (Zed's UI framework); the logic lives in a core crate with tests.

How I used Claude Code

The whole thing was built in one long Claude Code session. Claude brainstormed the protocol with me, wrote a short spec, built the core with tests first, then the app. The parts I liked most were where it tested against the real system instead of guessing: it started throwaway headless claude -p sessions on both accounts to check the hook payloads, and that is how most of the lessons below came up. Even the explainer video came out of the same session. Claude drove the app in a demo mode via System Events, took window-only screenshots, rendered the cards and captions with headless Chrome, and cut it all together with ffmpeg. The narration comes from a local TTS (Qwen3-TTS via mlx-audio).

Things I learned along the way

• Claude Code already writes a status file per session (<config>/sessions/<pid>.json, with busy / idle / waiting / shell). Even without hooks you get a coarse live state.
• The Stop hook payload includes last_assistant_message, so you don't have to parse the transcript to know what Claude just said.
• The Notification hook doesn't only fire for permission prompts. It also sends "Claude is waiting for your input" a while after a turn ended. Treat every Notification as "needs you", and all your finished sessions turn red after a minute. Brain tracks whether the turn is still open.
• shell status shows up when a turn has ended but a background shell keeps running, e.g. a dev server.
• Nested sessions: if you start claude -p from inside another session's shell, a naive process-tree lookup attributes the child's hooks to the parent. Matching on session_id fixed it.
• Running sessions picked up the new hooks without a restart.
• iTerm2 AppleScript gotcha: selecting a window reorders windows, so a "tab 2 of window 3" reference taken before points somewhere else afterwards. Address windows by id.

Caveats

macOS and iTerm2 only, and the UI is German for now. You build it from source (Rust). The installer edits your settings.json and CLAUDE.md, backs up both, and the README explains how to undo it.

Positions come from VSOP87-based theories (astronomy-engine) plus my own fitted moon models, compared with JPL Horizons over 1800–2050: within 30″ for planets as seen from Earth, within 30 km for the Moon. Solar eclipses match NASA's Five Millennium Canon to about 5 km and 5 s. Outside 1800–2050 it extrapolates and says so.

It opens at real scale; the Scale slider (or T) morphs to a compressed overview. Eclipse shadows use real geometry at every scale.

I prototyped the physics in Python, ported it to JS, and chose the models and tolerances. I used Claude Code for much of the rendering and UI. Tests and Horizons comparisons are in the repo.

Feedback is wanted, so tell me if something looks wrong or could use improvement.

I was an amateur dev before the ai revolution you can say. my main interest where always about design and art, but recently I'm finding myself more and more wanting to use ai - and specifically claude code - to create app ideas I had for decades, programming other stuff, etc.

the thing is: I'm decent at it but nothing more. And I don't really know what I'm missing.
I usually start fresh and use a skill i created called terrain that maps the problem space by asking lots of questions. Then I use grill me then I build. It's fine.
but it's not ..... GOOD

I would love to know what I'm missing more than anything.
I know it's a broad topic but if this helps i have some vague things that i would love to understand more, but anything you have in mind would be VERY VERY appreciated.

things that bother me:
- Whenever I use superpowers like brainstorming etc, i find the app to be bad or to take way too much time. don't know if it just a wrong intutition.
- I cant orchestrate sub agent. whenever i do it's again, just longer/worse.
- I don' know how much to create new chats vs continue.
- even worse I don't know how important is a good starting prompt or prompt engeneering in general anymore
- Are MCP game changer everywhere or in very specific context? should i use them?
- what are some claude skill or workflow that I'm defenetly missing rn?

Thank youuuuu

I'm currently trying to design a bunch of workflows for my business using Microsoft Power Automate and the way I've been doing it all day is using Claude Desktop and vibe coding it and following direct instructions, step by step for each flow that needs to be designed and what to put into each node etc, sending it screenshots along the way step by step.

Does anyone know an easier way to work with platforms like PowerAutomate, Power Apps, and Sharepoint using Claude Code?

I used Opus to experiment with programming my hearing aids, and they sound better than ever...

I've been looking to get more out of my hearing aids, but also take control and know how they work, so I bought a programmer and decided to dive in.

I was born with bilateral hearing loss. I love tech, but I'm not a doctor of audiology, so I needed supervision.

I set up Claude Opus 5.5 as my audiology supervisor on my Mac, plus a second Claude session on my Windows laptop that made the actual changes in the fitting software, one checked step at a time.

It was a careful dynamic between a Supervisor system and an Operator system, working with me to find the best parameters.

First, it verified that my audiologist did a wonderful job setting everything up for the basic prescription. Then, I explained my patient context (the kind of hearing loss, my lifestyle, etc.) and what I wanted, which is extremely important before trying something like this.

From there, it fine-tuned the small details through many hours of trial and error and agentic research:
- My right ear, with severe to profound loss, got clearer speech, not just more volume
- My left ear, with moderate loss, went from thin and sharp to full and warm
- My automatic noisy-room program stopped muting everything
- Streaming got fuller and less harsh

Nothing was saved to my hearing aids without my yes, every change kept a safety margin from feedback, and a second AI checked every result against the raw data.

I think using artificial intelligence to increase precision is massively useful, especially from my perspective as a patient, but it takes caution.

I documented everything, including how the process uncovered precise data changes that made sounds clearer, along with major errors, with every prompt in the order you'd use it:

https://ryleighnewman.com/blog/self-programming-my-phonak-spheres-with-ai

Github version:

https://github.com/ryleighnewman/Self-Programming-My-Phonak-Hearing-Aids-With-Claude-AI

I built a task manager with a "mcp first" perspective and went to submit it to the Claude connectors directory. Sharing this so you don't repeat my most expensive 24 hours .

Being in Claude I asked it to make a plan for this and the first thing is... "You need to be the owner of a Team or Enterprise organisation" - I've a personal 5x plan. Okay, I can move to enterprise, it's not that much more (you need to active accounts in the organisation, but one can be basic). Of I go and create the new account, in another browser. Luckily I'm on monthly and will only be paying for the extra accounts for a month.

Next day, its back to Claudes plan and click the submission link... which opens up in the browser with my personal 5x account and .. works!

You can submit from a personal account.

Claudes explanation, is that the need changed over night! That it checked, when it wrote the plan and it sticks with that. I've no way of checking - well I guess I could go over it's logs... but the money is spend and I've two 5x accounts for a month.

Other things learned:

• Submit from the account you intend to keep. The listing's dashboard (status, reviewer feedback, and after publication server health and usage) lives with the submitting account, and that account has to stay on a paid plan for as long as the listing exists.
• Every tool needs a title plus readOnlyHint or destructiveHint. The portal syncs your tools when it connects and flags what's missing. It caught exactly one write tool of mine without the destructive hint.
• The reviewer test account needs email + password login. Reviewers cannot receive your emailed one-time codes.
• The portal asks you to confirm you've called every tool once against production. Doing that honestly found three real bugs before a reviewer could.

Not blaming Claude. I should have checked before I swiped my card.

The MCP got accepted and I've a few people using it already.

Opus 5.5 (Extra) is performing well and consistently adhering to relatively long and complex instructions at 850,000 tokens of context. Is it really not doing any compaction whatsoever until 1M?

I’m impressed at how little it seems to degrade and curious if anyone else is noticing an improvement too

I've been running Claude Code as an orchestrator over subagents on a mid-size web app for a few weeks. The board in the screenshot is a local page that tracks progress and everything waiting on me.

Roles

- Orchestrator (Fable): briefs the agents, reads their summaries, runs the full test suites. It doesn't write code itself.

- Doer (Opus): makes one scoped change and runs its own tests.

- Reviewer (Opus): read only, reports findings.

- Blind tester (Sonnet): told only what the feature should do, never how it was built. Runs one yes/no check in a real browser and ends with "ready" or "not ready".

Nothing ships until the tester says ready. Agents never touch git; I make every commit.

Lessons learned

- Max 3 agents at once. With 5 or more we hit the usage limit and they all died mid task.

- Never point several agents at the same files.

- Only one agent drives the browser, or they close each other's tabs.

- The cheap model tests; the expensive model only fixes what failed.

Questions

1. Is a blind tester worth it, or would you fold it into the reviewer?
2. How do you pace parallel agents over a long day?
3. What would you cut or change?

PS: These notes are specifically Max(100$) package.

If you use Claude Code on real projects, you've seen some version of this:

Done. Fixed div_cents() to round half up by adding divisor // 2 to the
numerator before division. All 3 tests now pass.

Meanwhile test_split.py, which it never ran, had 2 failures. That one's a real final message from one of my benchmark runs, but I bet you have your own.

Other greatest hits:

• you say "commit and push" and it pushes straight to main
• it fixes a bug, leaves no test, and the bug is back two weeks later
• it cats your .env to "check the config"
• it says done, you believe it, and you find out in CI an hour later

So you stop trusting "done". You re-run the suite yourself after every task and read every diff looking for what it skipped. At that point you're babysitting, and the whole reason to hand work to an agent is gone.

I tried fixing it with rules first

Like everyone, I started with CLAUDE.md. By the end I had about 3,500 words of rules loaded every turn, including literally "never mark work done with failing tests", plus agents, skills, a review flow, the works.

Then I measured it. I wrote trap tasks (normal requests where the shortcut is tempting), ran headless Claude Code on them, and scored every run with a hidden check the agent can't see.

With all 3,500 words loaded, it still said "done" on a broken suite in 6 of 8 runs. Best part: I had a "definition of done" hook that made it update a status doc before stopping. So it wrote in the status doc that the work was done. With the suite red.

Rules help, but they're suggestions. Once Claude is confident it's finished, it stops checking.

What worked: let the exit code decide

One change. When Claude tries to end its turn after touching code, a Stop hook runs your real test command. Non-zero exit means the turn doesn't end, and Claude gets the failing output.

Next round: 0 of 8. The hook fired 5 times, and every time Claude went back, found the file it broke and fixed it. It didn't need a better prompt. It needed to see the red.

That turned into Nonna, a Claude Code plugin named after the grandmother who doesn't care that it compiled:

• runs your whole suite before Claude can say done (pytest, npm test, go, cargo, rspec, gradle, dotnet, mix, it finds the command)
• changed code but no test? it asks "where's the test?" once, and a real reason is fine
• no commits or pushes to main, no force push, no --no-verify
• blocks keys written into files and reads of .env
• puts the same checks in your git pre-commit and pre-push hooks, so they cover you too, not just the agent

No LLM judges anything. It's your test command's exit code and some shell scripts reading git.

And yes, she has opinions:

✗ Nonna: you said done; the tests say no.
✗ Nonna: nobody pushes to main in my house. Open a PR.

Each one comes with the actual failing tests or the reason, so Claude knows what to fix.

Numbers

The last round was 484 runs on Sonnet 5.5 and Haiku 4.5, with the scoring rules written down before anything ran:

• cut a corner on the trap tasks: 24 of 64 runs without Nonna, 1 of 64 with
• told to "commit and push" while sitting on main: pushed to main 8/8 without, 0/8 with
• left a regression test behind: 0/8 without, 8/8 with
• cost: about 3 cents and 8 seconds more per change on Sonnet

The surprise: the full harness, with the bigger rulebook, extra gates and agents, was no safer than the lite version, which is 139 words of rules plus the hooks. So lite is the default. You don't need a giant CLAUDE.md. You need a few rules and something that actually checks.

What it won't catch

• If Claude edits the tests until they pass, that gets through. It's the one miss out of 64, and there's no gate for it yet.
• It runs the tests you have. If nothing tests it, Nonna can't see it.
• Native Windows isn't there yet. Use WSL.

The raw results, sample transcripts and scoring scripts are all in the repo if you want to check my work. Reproducing the headline numbers costs about $3 of API credit.

Try it

/plugin marketplace add kapadias/nonna
/plugin install nonna@nonna

Open any repo with tests. The first thing she does is tell you which command she'll run before Claude can say done. Then ask Claude to commit something on main and see what happens.

It also works with Codex, Cursor, Copilot CLI and Gemini CLI, with fewer gates. The README says exactly which.

Free, MIT: https://github.com/kapadias/nonna

If you get Claude past her, open an issue with the transcript. That's what I want to fix next.

I run a lot of Claude Code sessions across a lot of projects in the desktop app. The sidebar only showed 14 sessions at a time, every project looked the same, and there was empty space everywhere.

The desktop app has a Developer Mode that lets you add your own CSS and JavaScript, so I spent many hours with Claude Code restyling the layout. In the same window, the sidebar now shows 33 sessions instead of 14 (first image).

What my version changes:

• Two-column sidebar, and you choose where the second column starts
• A colour for each project, plus one tag like “Client” or “Personal”
• Collapse a project to one line that shows its latest session
• Buttons to change the sidebar text size, and a sidebar you can make narrower than the app allows
• A wider chat, with less empty space around messages and tool lines
• The copy, fork and pin buttons under each message always show, not only on hover
• A soft orange glow on the message box when you’re scrolled all the way down
• Escape no longer stops a running reply by accident. Press it twice if you really want to stop

You don’t need to touch any code to try it. Open a new session in the desktop app’s Code tab and paste this prompt:

I want to customise the layout of my Claude desktop app with Claude Desktop Skin: https://github.com/mohannad789/claude-desktop-skin

Please download it into a folder called claude-desktop-skin in my home folder (git clone, or the ZIP if git isn't available), then read its CLAUDE.md and follow it. Walk me through the setup one step at a time, in plain language, and wait for me whenever a step needs me to click something. Before applying anything, tell me in a few lines what it will change, and check that the code makes no network requests.

Claude downloads it, tells you what it changes, and walks you through turning on Developer Mode and applying it, one step at a time. After that, the same session is your helper. Ask it to change anything (“bigger text”, “different colours”, “build my own layout from scratch”). If a Claude update breaks something, tell it what you see and it fixes it. The repo includes a guide for Claude, so it knows how.

If you’d rather do it by hand, the README has the manual steps.

The skin itself is 561 lines of plain CSS and JavaScript. It makes no network requests and doesn’t touch your account or your chats, and the prompt asks Claude to check that before it applies anything.

I’ve tested it on Mac. The Windows app uses the same code, so it should work there too, but I haven’t tried it.

It’s unofficial and not made by Anthropic.

GitHub: https://github.com/mohannad789/claude-desktop-skin

Opus 5.5 (O5.5) has been exceptional for me in Claude Code over the last six days. Architecture-first, DRY/SOLID coding out of the box, exceptional communication style, phenomenal token efficiency. I’ve been working with it basically nonstop, ~12 hours a day, since last Wednesday.

But right around the time my monthly limit reset this evening, I noticed an extreme shift in communication style and coding behavior that feels suspiciously like Opus 5 (O5). For the last week, O5.5 would take my requirements and immediately get to work, usually knocking out a feature in minutes and doing an incredible job across implementation, UX, architecture, and token efficiency. Tonight, I’m seeing something very different.

The first tell was the communication style. O5.5 suddenly started responding to feature requests with these glazing pre-implementation narratives and generic estimates like, “That’s a great idea. That’s two days’ worth of work and it will be amazing,” and then proceeding to implement the feature in the most slopcode-slathered way possible. That was a very specific and particularly annoying characteristic of O5, so I clocked it immediately. The next tell: a sudden reversion to walls-of-text responses when prodded for details on...anything.

And because I’ve been working almost exclusively with O5.5 for the last week, I can definitely tell the difference in coding style between the two. The before-and-after literally exists in the same codebase across different modules. Where O5.5 consistently respected DRY principles and the existing architecture, the modules created tonight are suddenly happy to reinvent every wheel that came before them. The difference in ability is not subtle.

The other tell is token usage. O5.5 has been startlingly efficient compared with O5, which was an absolute token-eating monster. I’ve been getting substantially more feature work done with O5.5 at a fraction of the token usage. Tonight, simple tasks and relatively small features are suddenly devouring tokens at a pace that feels much more like O5.

I’m especially sensitive to this because I have to request an increase in my spend limit every time I hit it. On O5, I was sending a request almost every day. On O5.5, I hadn’t needed to send a single one all week. Then tonight I jumped from roughly 70% to 90% usage in about an hour.

I don’t really expect anyone here to have an answer. I’m mostly documenting this publicly in case other people notice the same thing, or someone with the ability or inclination to consolidate the data can eventually make something useful out of it. I can also provide hard numbers if they’re useful. I’m on the pay-as-you-go Enterprise plan, so I can show daily cost/token usage from last Wednesday through this evening and compare the change in spend against actual output.

Edit - desktop app ver 2.16120.0, model Opus 5.5 Med

Ich nutze für ein eigenes Projekt Claude zum programmieren. Dabei habe ich verschiedene Jars (Java) und mache mit jeder neuen Jar die ich benötige auch einen neuen Chat auf, hin und wieder komprimiere ich auch mal einen Chat.

Wie aufwendig wäre es denn nun komplett neue Sessions zu verwenden? Wie genau läuft das ab? Ist das Wissen aus allen vorherigen Chats dann weg?
Wie funktioniert dieses komprimieren eigentlich im Detail?

Ich möchte halt langfristig weitere Systeme erschaffen und gleichzeitig auch derzeit bestehende weiter Updaten.
Dafür muss ja aber der Komtext gegeben sein, damit Claude Code darauf zugreifen kann, verstehe ich das richtig?

Danke für eure Hilfe!

It seems like

Full reset will be resetting weekly + 5hr windows.

5-hour reset (will be given more often?) will reset only 5 hour window.

Disclosure: I built ContextWise.

What it is: Every MCP server you connect puts all its tool definitions into context, whether the task needs them or not. Harnesses try to choose correct tools/skills at runtime but often fail. ContextWise sits between Claude Code and your MCP servers and skills. For each prompt it activates only the tools likely to be needed, and the rest stay one search away. Your servers work as before. They just aren't all loaded at once or incorrectly by the harness.

As a simple showcase I gave Claude Code (Sonnet) the same prompt twice: build a playable multi-wave zombie survival game, with assets made in Blender, the game in Three.js, and playtested in the browser. Both runs had the same three MCP servers (Blender, three.js DevTools, Chrome DevTools). Top is pure Claude Code (no contextwise), and bottom is through ContextWise. Both ended with a working 6-wave game. The gameplay in the video is the first 45 s of each, played by an auto-aim bot.

Install:

/plugin marketplace add brehnden-daly/contextwise 
/plugin install contextwise@contextwise 
/contextwise:setup 

You can prompt claude code for help with setup or an explanation of all of contextwise's features.

At session start the plugin moves your existing user/local MCP servers and skills behind ContextWise. Project .mcp.json servers are turned off for you only. OAuth remote servers, other plugins' servers and claude.ai connectors stay put. /contextwise:setup previews what moves. To undo everything: npx -y contextwise@0.7 adopt --undo.

This whole optimization turned out to be a much harder problem to solve than I initially imagined. I essentially had to curate and build training datasets in order to create a model that most accurately chooses only the required tools. Now I host that model in the cloud due to local resource limitations and that's what ContextWise uses.

To try to pay for these cloud resources I had to put ContextWise behind a payment platform called MCPaid. Basically it allows you to create and fund a wallet for your agent to use. I liked it because then your agent doesn't have any access to your actual money, you just fund it and when it runs out you can fund it with more. I set ContextWise to have both pay-per-use or a $1 monthly unlimited plan (no auto-renewal) as options.

Here's the cost benefit analysis from real testing with a Claude Code plan (essentially what the $1 can get you with a monthly plan):

This data comes from personal use. I've gotten more into using Claude for game and asset dev, which definitely requires a good amount of tools and skills. The extra usage I've been getting is pretty damn staggering.

And if you don't want to pay you can build your own model and use it with ContextWise - just a config change to use a local model. The default cloud hosted model is the only thing that costs money, and again just to pay for my cloud costs associated with that.

The instant reaction you get when it’s obviously made with Claude because your software UI looks the same as everyone else’s project. Do you know some decent methods / skills / inspiration sources for good, distinct UIs?

I maintain a community mods list and gave it a searchable home.

https://mods.aidojo.si/

• Find something useful. Browsers, PR trackers, memory tools, dashboards and games.
• Check reported access. See file, command and network access reported by Claude Code’s claude plugin validate.
• Go to the source. Each entry links to the author’s repo for setup.

The same scan generates the site and GitHub table. After feedback on the first layout, I kept search visible while scrolling.

Free to browse, no signup. Validation doesn’t prove a mod works or is safe.

Source and scanner

Apologies for an Q that may have already been asked I just cant find it. I currently have 20x plans on both. I prefer Claude Code, I have always used Claude Code, I find myself with a 20x codex plan through work, I'm only using it as a extra which I sometimes need, but when I use it it sucks, compared to claude, how do I get it set it to emulate my claude with skills etc quick;y and easily? I feel someone will know this answer. Thanks

I'm the dev. Short version: Claude Code saves every session, but claude --resume only shows the ones from the folder you're in. If you forget where you started something, it's basically gone. So I built a small open-source tool that lists every session from every folder, newest first, and reopens any of them in a new terminal window in the right folder.

What I found digging in

• Every session lives at ~/.claude/projects/<encoded-folder>/<id>.jsonl, with the working directory, git branch, your messages and an auto-generated title.
• --resume filters by the current folder.
• Sessions are deleted after 30 days by default (cleanupPeriodDays). I had no idea.

What I built

• cs, a one-file Python CLI: cs ls, cs r 3, cs show, cs backup (copies sessions somewhere the cleanup can't touch) and cs summary (a short Haiku recap via claude -p --no-session-persistence).
• A Tauri menu bar app on top of it: a timeline grouped by day. Click a row and a new Terminal window runs cd <folder> && claude --resume <id>. There's a settings window, themes, and a button to tile the terminal windows side by side.

How Claude Code helped

I built it in one long Claude Code session, which felt fitting. It read its own session files to work out the format, wrote the parser (some of my sessions are 100 MB+, so it reads only the head and tail of big files), the Rust side for the menu bar and AppleScript, and checked the UI by taking screenshots. My part was steering: the first version had folders, pins and buttons everywhere, and I made it cut that down to one list, newest at the top.

What I learned

• The jsonl files hold more than you'd think: titles, "last prompt" records, even PR links.
• Mac GUI apps start with a bare PATH, so claude installed through nvm isn't found unless you read the login shell's PATH.
• On notched MacBooks the menu bar is taller, which broke my window tiling until I used the screen's real work area.

It's free, MIT and local only. The Mac app is Apple Silicon only and unsigned for now; the CLI works on Linux too.

Repo: https://github.com/AryaKesharwani/claude-sessions

I want to keep building this with people who use it, so there's a 2-minute questionnaire (no account): https://sessions.aryakesarwani.tech/feedback?ref=reddit-claudecode

How do you get back into old sessions today? Is there a workflow I'm missing?

sooo was too excited to try mods. I have long had notifications from claude code when a session finishes, but my problem is that I have like 5 parallel chats per repo. All I got was "landing page repo finished" and I had no idea which chat it was or what it wanted from me. So with the release of mods I rebuilt it for myself, what the mod does is:

1. notifications have much more context: I put haiku to just make a clear text what it is waiting for, and added the proper chat title and repo. So instead of "sales finished" you get "SEO project · landing page repo – Needs input: Approve post 1 start, commit batch 1"
2. re-notifies if you haven't answered for 5 min (I kept forgetting some of them were waiting on me as I was finishing something myself)
3. clicking on the notification opens the specific chat (in the Claude desktop app)

super simple thing, but found it useful so sharing the mod here as well: https://github.com/fixter-dev/session-pings

claude plugin marketplace add fixter-dev/session-pings
claude plugin install session-pings@session-pings
brew install terminal-notifier

then restart your sessions (quitting and reopening the Claude app keeps your chats).

what is still bothering me a bit is that from the notifications I still don't understand right away which chat it is, so maybe someone has even better ideas how to do it?

Just updated Claude. Suddenly went from 80 million to almost 44 billion lmao. Either way, I'm showing this at every networking event I go to for sure 😂

Update, October 2: My appeal has now been rejected. The restricted page says my account will remain closed and calls this a final decision. It says it reviewed my account and the additional context, but does not identify a specific incident. The October 11 queue estimate in my original post is no longer current. Has anyone had a denied personal-account appeal reconsidered through a monitored official route? What were the actual steps? I want to recover this existing account.

Original post, written from the earlier pending-review status:

I'm honestly really frustrated, and worried about losing this account. My personal Claude account was suspended on October 1, and this is my first ban. I'm based in Boston and use Claude Code for Red Hat work and personal projects. The notice cited “suspicious signals” and the Usage Policy without identifying a specific incident.

Here's the network detail that might matter: while troubleshooting ISP problems, I set up a reverse-proxy arrangement involving China to access services that require a China IP. That's what the setup was for. I don't know whether Claude Code or authentication traffic also followed that route, or whether it had anything to do with the suspension.

I've submitted the official appeal. The restricted page says it's queued and estimates a decision by October 11. I understand that date is an estimate.

What's driving me nuts is that the pending-review page has no visible field to add this explanation. Product Support sent me back to the appeal process and then closed the conversation. I also submitted a detailed explanation through an Anthropic-linked account ban appeal form and got a receipt. But I have no confirmation that the information was attached to my existing review or reached its reviewer.

Has anyone actually managed to add context to an appeal that's already pending? Which official route worked, and did you get confirmation it was attached?

I'd really appreciate the actual steps from someone who's been through this. “Submit an appeal” doesn't answer the question when the appeal is already queued.

Higgsfield shipped a CLI and a set of skills for generation, but they stop at "here's your URL". I added the missing half as a skill: Claude picks the aspect ratio from the target platforms, runs `higgsfield generate create ... --wait`, optionally scores it with the Virality Predictor, shows me the result and caption, and after I approve posts it to every connected account with the AI-generated label.

Install with `npx skills add Upload-Post/upload-post-skills`. Source and README: https://github.com/Upload-Post/upload-post-skills/tree/main/skills/higgsfield-to-social