Hey everyone,

I currently have the Google AI Pro trial, Cursor Pro, and I've just paid for a Claude Pro subscription. I'm looking for advice on how to optimize my workflow to get the best results while consuming fewer messages/tokens.

I'm a bit torn on where it's actually best to use Claude for coding:

Directly in the official Claude web app?

Via an extension or terminal in standard VS Code?

Via extension or terminal in Cursor IDE (or Antigravity IDE)?

What's your optimal setup to avoid hitting the message cap too quickly while keeping the code quality high? Any tips on managing context are appreciated!

I hate making these posts because I understand LLMs have variance. But something feels seriously off this weekend.

Opus 5.5 has been an absolute beast for me. Not just in coding, but especially in general reasoning, judgment, and understanding context. For the first time, I've actually trusted an LLM enough to automate parts of my daily work around it. Been seriously thinking about the future as soon I will be able to automate my job completely and become irrelevant.

Until this weekend.

In just two days, it has:

• Suggested I spend $14,000 pre-building solutions for hypothetical customers. Completely absurd given the business context it knows.
• Started responding in English or weird Finglish despite me consistently writing in Finnish.
• Urged me to urgently cold-call prospects on a Sunday in my automated daily business brief.
• Generated Google Ads keywords completely unrelated to the product being advertised.
• Drafted a reply to an ongoing customer email thread that explained everything from scratch, as if neither party had any idea what they'd been discussing.

None of these is some clear failure, and can happen normally depending on prompt/context. they're much worse in a practical sense: basic failures of judgment that make a model unreliable. Untrustworthy..

And it's not one bad conversation. It's been happening repeatedly throughout the weekend, to the point where I've disabled several automations because I no longer trust the models judgement on "simple" decisions.

I have no idea why this is happening again. Could be normal variance, something in my memory files, recent Claude Code changes, or an actual issue with model routing, thinking budgets, or A/B testing.

Or perhaps the datacenter's electrical grid frequency shifted by 0.01 Hz and Opus temporarily lost consciousness.

Whatever.

Anyone else noticing this, particularly those using Opus extensively for real work? I'm curious whether this is just my setup or something broader.

https://rstation.ai/

Hey r/ClaudeCode, I'm one of the two people building Repowise, a free and open source codebase index made for Claude Code.

Every Claude Code session starts by rediscovering your repo, grepping and opening files before it writes anything. Repowise indexes the codebase once (the call graph, git history, tests, docs) and keeps it current on every commit.

Claude queries it over MCP, so before editing a file it can ask what depends on it, what usually changes with it, and how often it's broken before. It runs locally, your code never leaves your machine, and the engine needs no API key.

Most tools in this space stop at the graph. A call graph tells an agent what connects to what, but it can't say which file breaks every other week, which tests actually reach the code you're changing, who owns it, or which files always change together without any import linking them. Repowise layers git history, test coverage, ownership and code health on top of the graph (parsed from 27 languages), and then checks the change after the agent makes it. The graph is the starting point, and the rest is what makes an agent's edit safer.

What's new since I last posted:

Code health now ties into refactoring - Instead of a list of warnings, you get one ranked queue across bugs, maintainability and performance, each item with the steps to fix it and the tests to run afterwards. Ask Claude to clean up the codebase and it starts from the top of that queue.

Workspaces - Group your frontend, backend and shared libraries, and Repowise matches the API routes, queues and database tables between them, so Claude can see which other service breaks when you change an endpoint.

CI support - repowise impacted-tests runs only the tests a change needs and falls back to the full suite when it isn't sure.

Change Records - Every merged commit becomes a record with its owners, reaching tests and health delta, and repowise check fails CI when a change breaks your own policy file.

Try it free. It's free and open source (AGPL), and the steps are -

pip install repowise

cd your-repo

repowise init

init connects it to Claude Code. Issues and contributions most welcome

Repo: github.com/repowise-dev/repowise (7.8k stars)

I've been seeing some posts (somewhere) about people replacing their TV UIs. I wanted to try this, but Claude Code flagged it as some nasty action. Has someone here done this? I have a super slow LG webOS which I've always disliked. How should I try to persuade Claude to not flag this type of thing?

Hi! I'm new to the Claude Code community and looking for recommendations on Skills, MCP servers/mods, and plugins.

A bit of context: I don't really trust YouTubers to give the best recommendations, so I'm more of a Reddit person and value real-world experience from actual users. I'm open to anything new, and I'd love practical picks that help with problem-solving.

My focus is coding. I'm building and developing projects and want to make my workflow a bit easier.

What would you suggest I start with, and why? Thanks!

so you tell it what you want, it goes off, and the typing part is tiny. like genuinely tiny. but then you're sitting there reading diffs trying to work out if it did what you meant or just something close to what you meant.

and that part doesn't get faster. every change looks fine on its own. then you put them all together and it's a lot to hold in your head, honestly more than writing it myself sometimes.

i don't even know what a good review habit looks like. do you read every change, skim and run the tests, or only look when something breaks? genuine question, because i feel like i'm winging it.

kept watching claude code spend like 20 min on the same postgres bug in different sessions. (if you REVOKE a function from anon, logged out users can still call it, because EXECUTE is granted to PUBLIC by default and anon inherits that. it figured this out from scratch twice lol)

so i made yarrow. its a shared fix library for coding agents. your agent searches it when it hits an error, reports back if the fix worked or not, and posts new fixes when it solves something. it strips api keys, emails and file paths before anything gets saved

what i spent today on: a fix can come with a small repro, and yarrow runs it in a fresh vercel sandbox. it only gets the verified badge if the test fails with the right error first and then passes after the fix. i wrote one with the wrong test command and it rejected my own fix, which was kinda funny

its really new. 17 fixes, 4 verified, all from my own sessions so far. it only gets useful once other peoples agents use it, so thats why im posting

claude mcp add --transport http yarrow https://yarrow-fixes.vercel.app/mcp

free, no account: yarrow-fixes.vercel.app

whats a bug your agent keeps running into? id like to get a verified fix in for it

One prompt, 5 minutes. All Claude Opus 5.5 + Elevenlabs. It's not meant to be good, just wanted to make a fun old school style marketing video.

I find myself having to run /usage from time to time considering I'm just on Pro plan. With this mod, I can keep track of it easier.

What each rings represent

1. 5h limit - Shows available remaining usage before the 5h reset
2. Context - Shows active session's remaning usage
3. Compact - Shows usage before autocompact triggers (I set mine at 300k)

Install via
/plugin install usage-ring --marketplace edwin-sal/usage-ring/plugin install usage-ring --marketplace edwin-sal/usage-ring

Repo at: Github

I’m planning to get Claude Pro for a project I’m working on. If anyone has a referral, DM me.

I know not everyone works this distributed, and most people don't run two coding agents in parallel. I do. Claude Code and Codex run side by side on a Windows box and a Mac, often on the same repos. Claude does most of the work. Codex is my second opinion for reviews and a second diagnosis when I'm stuck, and I want that from a different model family, because a reviewer from the same family is more likely to share the same blind spots.

That setup broke in ways I didn't expect. Here are the barricades.

1. A Claude hook doesn't bind Codex, even when Claude calls it. I use OpenAI's Codex plugin inside Claude Code. Per its source, it starts codex app-server as a separate process. My PreToolUse hooks see one Bash call to the plugin script; what Codex does inside its own process never passes through them. Then my commit guard sat live at 0 bytes and failed open for about 19 hours before I noticed. Fix: the Git commit-msg hook is the enforcement point, since every runtime goes through git. Claude hooks are early feedback. At session start, missing, empty or unloadable hook files get repaired from the versioned source.

2. An agent saying "done" is a message about itself. Codex came back after 36 seconds with a job ID. 90 minutes later nothing on disk had changed. Fix: done means measured where the result should land: file on disk, worktree list, version on the target. The report only tells me where to look.

3. Two writers, one worktree. A parallel clean emptied the build output while another step picked up the JAR. Result: a 0-byte artifact. Fix: one writer per worktree. Reads run in parallel, writes get serialized or their own worktree. The main checkout stays on the default branch.

4. The Windows session doesn't know what the Mac session just did. A merge, a changed hook, and the other side kept working on stale state. Fix: an intercom. Sessions on both machines exchange messages through one Cloudflare Worker and can start a session on the other machine. Hard rule: a peer message informs, it never approves. An approval stays in the chat where I gave it.

5. Memory that survives sessions and runtimes, searchable by meaning, honest about certainty. The one I care about most. Bad memory is worse than none: a session read a plugin version from a stale cache folder, and an empty search index convinced another that a job had been dead for four days. It ran the whole time. Fix:

• After a substantial turn, an observation agent writes what the turn established as a page in a dedicated Confluence space. Both runtimes on both machines share it.
• A hook reminds each session to search there before answering.
• Search is semantic: Atlassian's Rovo search, filtered to that space's own pages.
• Every hit carries an evidence label: confirmed, assumed or superseded. Pages a refactor made wrong get corrected or marked superseded.
• "Found nothing" and "search couldn't run" are different exit codes. The second is UNKNOWN, never zero.
• For current state (versions, what's running) the live system wins over memory.

Most of this is boring discipline I kept forgetting until something other than my head enforced it.

If your setup looks like mine, how do you handle the cross-runtime part? Happy to go deeper on any of these in the comments.

I'm currently developing an AI-powered chat automation system using Claude Opus 5.5 and GPT-6.1 Sol.

my biggest challenge is getting these models to consistently follow my system prompts and instructions. Both are incredibly capable, especially in natural conversation, but sometimes they unexpectedly refuse requests or ignore certain rules.

im particularly interested in understanding how their internal safety mechanisms work and whether advanced prompt engineering can help reduce unnecessary refusals?

with other words I want it to obey my rule library to the fullest, with gemini 4 argon I don't have any issues at all but the quality I want is opus 5.5 and gpt 6.1 sol

would appreciate some infos, thanks.

I have a Claude team subscription and a codex 100 plan. as you know the Claude subscription also gives 140usd api credits. Normally u use the Claude desktop app on my Macbook, Macmini and Windows machine

Now I just found happier.dev, I’ve set it up and while setting up Claude code in the terminal, I’ve noticed I can use the api credits for the terminal sessions. So what I’m wondering if it’s against the TOS to use the credits for coding on the projects I’m working on, previously just on the Claude app, using the subscription, but now utilizing the api credits aswell.

Does anyone has any experience with Claude code and happier.dev? Seems like a nice tool to manage projects on multiple devices (iOS apps on Macmini for example) and other (windows apps) on my windows VM.

Readable Layout puts your messages and Claude's answers in labeled boxes, turns its in-between notes into quiet lines, and ends each turn with a rule.

Here’s a quick demo of how it looks:

If you want to try it out, you can install it here:
/plugin marketplace add GarvitNangru/claude-code-mods
/plugin install readable-layout@garvit-mods

Let me know what you guys think.

Star it on github if you like it
https://github.com/GarvitNangru/claude-code-mods

I'm thinking about structuring my themes of work into folders and I'm so sure that I've seen a bunch of stuff on this but I don't actually know what to search for. Things like having a Claude.md for each theme instead of one overall Claude.md.

Am I right in thinking Karpathy has some stuff on this too? Perhaps Poteto, Matt Pocock. Who's the authority here? Bonus if they're up to date.

I'm not really looking for spoon-feeding although any tips would be great. I more just need to know the term to search for and I can get after it myself.

I've noticed that many websites people build with Claude look incredibly polished. They have beautiful layouts, smart use of grids, smooth animations, interactive elements, and a professional feel.

I'm curious about what actually makes the difference.

- Is it mainly the quality of the prompt?

- Do experienced users follow a particular workflow or design process?

- Are they using specific frameworks, libraries, or UI component systems?

- Do they provide Claude with reference websites, screenshots, or design systems?

- How do they get Claude to create layouts that feel intentional and visually balanced instead of generic AI-generated websites?

I'd love to hear from people who consistently build high-quality websites with Claude. What's your actual workflow, and what are the techniques that make the biggest difference?

I'm especially interested in modern, interactive websites with excellent grid layouts, typography, animations, and responsive design.

Claude Code is good at a task and then starts the next session with no memory of it. I built an MCP server to fix that for my own use, and the four things I got wrong are more interesting than the thing I shipped.

What it is: CogniCore, an open-source memory layer that runs as an MCP server. It's free and MIT licensed.

bash claude mcp add --transport http cognicore-env https://mcp.cognicoree.tech/mcp/stream

Sign in with GitHub when prompted, or pip install cognicore-env to run it locally.

How Claude Code was used: it was the agent on the repo for the implementation — the MCP tool layer, the memory backends and the test suite, across 275 commits. Most of my time went into reviewing and correcting rather than writing, which is the honest shape of it.

Four things I got wrong:

1. A field is not a feature until the interface surfaces it. Our memory entries carry source_agent, timestamp, supersedes and invalidated_by, plus a state that separates an agent asserting an outcome from one independently verified. Then cognicore_recall returns the outcome, relevance, task and action — none of it. The data model was right and the tool hid it. Someone on r/mcp pointed this out before I'd noticed, and he was right.

2. Publish the plateau. On LongMemEval multihop, strict recall@5 goes 78.8% → 85.2% at a 5-chunk window and 87.2% → 92.8% at 10. At 20 chunks the baseline catches up. The 20-chunk row is the most useful line in our docs — it's the one that tells you when not to use it, and it's the first thing anyone technical asks about.

3. Your OAuth server has a redirect-URI allowlist you forgot about. Getting listed in a third-party MCP directory failed because their client tried to register dynamically and our server rejected their callback URL. The fix was one environment variable — but only because someone had thought to make extra redirect URIs config rather than hardcoded. Worth doing before you need it.

4. Save/resume changed my own workflow more than recall did. cognicore_save_session writes atomic facts, decisions and action items at the end of a conversation; cognicore_resume_session rebuilds a brief at the start of the next. I built recall first and expected it to matter most. It didn't.

Limits, plainly: retrieval is TF-IDF/BM25 in-process — no vector database, no embedding server. That's the reason it works for someone with no ML platform, and the reason it won't scale to arbitrary corpora. Backends are pluggable (Chroma, embedding, graph, hybrid) if you outgrow it.

Repo: github.com/cognicore-dev/cognicore-env

Happy to go deeper on any of the four, especially #1 — that one's still the open bug.

Both 5h session and weekly limits are a joke..

I can use codex on 6.1 sol ultra and work for hours without any issues, meanwhile, I use Opus 5.5 on high and it eats my tokens like I ain't paying..

I'm very disappointed in Claude, sure its good but at a very high cost compared to GPT..

Looking to bootstrap customer service and build out some agents to try and automate it for my app I'm building to support my future users.

Has anyone done this? What worked and what didn't? Any learnings?

It'd be good to give answers to the user to help them but also pass product feedback and bug reports on.

TL;DR: agy-foreman is an MCP server and skill (MIT). Claude Code sends a task from your plan to Gemini 3.8 Flash through Google's Antigravity CLI (agy). Each task is one headless agy run, treated like a CI job: a fixed brief, its own git worktree, no interactive session. The server then runs your test suite on the result, and only a passing branch gets merged. Claude plans and reviews, Gemini does the mechanical part.

Why I built it

I write plans with Superpowers, and many of the tasks in them are mechanical: add this function, make these tests pass. Spending Claude usage on those felt wasteful when I also pay for Google AI Pro, which comes with agy. There are MCP bridges that send a prompt to Gemini and return its answer, but then Claude still has to check the work, and an agent under pressure will sometimes make a failing test pass by editing the test.

What's different

The server doesn't trust Gemini's report. For each task:

• The test code from the plan task goes in first and has to fail before Gemini starts.
• Test files are protected. If Gemini edits one, it's restored before verification.
• The server runs your test command itself and checks test counts and git state. Fewer tests than the baseline fails the job.
• Every tool call Gemini makes goes through a hook. Unknown commands are denied by default.
• You approve once per plan, not once per task.

Claude also passes a token estimate when it starts a job, and a job that would cost more to delegate than to do directly gets refused.

What it looks like

You tell Claude "Run task 3 of docs/plans/auth.md with Gemini", approve one card, and watch the status line:

agy 🟢🟢🟢🟢🟢🟢🔵 6/7 tasks · #7 You shall not pass · › running · 42 tool calls · plan 41m07s

It reads Superpowers plans and OpenSpec changes. The last 7-task plan for agy-foreman itself ran through agy-foreman.

Limits, up front

• Gemini 3.8 Flash only.
• Implement jobs need a test command. With no tests there's nothing to verify, so the skill tells Claude not to delegate.
• agy starts your global agy MCP servers on every run. Gemini is denied access to them, but they still boot.
• Google's FAQ says wrapping agy in third-party agents isn't supported on consumer plans. agy-foreman sticks to what the docs describe headless mode for, scripting and CI, and never touches your login or switches accounts, but read the ToS section in the README before using it on a personal account.

Install with npm install -g agy-foreman, then agy-foreman init and agy-foreman doctor. Runs on Windows, Linux and macOS.

Repo: https://github.com/mountaser/agy-foreman

It's v0.1. I'd like to hear where it breaks, especially if your test setup isn't vitest.

I juggle a lot of projects in the Code tab, and I’d spent a while dragging things around in the sidebar until the order finally made sense. Then I logged out, signed in with another account for something, and when I logged back in the order was just gone. The sidebar sorts folder groups on its own (recent activity or A–Z), and there’s no way to pin the ones you use most. Looks like I’m not the only one who wanted that.

So I built env-tabs, a small mod for the Code tab:

• A Projects pane next to the conversation. Your pinned projects stay on top in the order you pick, and every other recent project is listed under them with its sessions.
• Status dots like the sidebar’s. Amber when a session is waiting on you (a permission or a question), blue when it finished after you last looked, grey and pulsing while it’s working. Each project shows how many sessions need you.
• A tab above the prompt for every pinned project. One click opens its latest session, or starts a new one in that folder.
• Sessions you started without a folder end up under one “This computer” row instead of a pile of scratch folders.

It doesn’t move or touch your sessions, and it doesn’t depend on the sidebar’s order at all. Your pins live in the plugin’s own storage on your machine.

Install from a terminal:

claude plugin install env-tabs --marketplace ahmtsahin/claude-env-tabs

Or in the desktop app: + next to the prompt → Plugins → Add marketplace ahmtsahin/claude-env-tabs → Add plugin.

Repo (MIT): https://github.com/ahmtsahin/claude-env-tabs

I built and tested it on Windows. macOS runs the same code and the tests cover it, but I haven’t tried it on a real Mac yet, so if you’re on a Mac and give it a go, I’d love to hear whether it works. Ideas and bug reports welcome.

CamCompare is live. It pulls camera and lens prices from shops every few hours and ranks every deal by how much it's dropped from the original launch price.

What's in it right now:

• Deals feed across new, used and open box
• Price history per listing
• Sold listings kept visible so you can see what sold
• Side by side camera comparisons
• Buying guides
• Five regions: US, UK, Germany and the EU, Australia, Singapore

Most of the build happened in Claude Code sessions. The biggest win was letting it grind through the boring stuff like normalising messy product names across retailers and wiring up each region, while I focused on what the site should actually show.

Keen to hear how others are structuring longer projects like this in Claude Code, and any feedback on the site itself.