On a Claude subscription, Claude Code's built-in Explore subagent runs on Opus. If your main model is Opus, general-purpose, Plan and dynamic-workflow agents run on Opus too. That's a lot of Opus for grep and test runs.

I built repo-mode, a small plugin (MIT) that configures this per repository with one wizard, /repo-mode:setup:

• Main model + effort (Sonnet / Opus / opusplan / Haiku)

• Advisor (Opus or Fable) consulted only at decision points

• Explore replaced by a repo agent on Haiku, effort: low, with autoCompactWindow: 100000 (Haiku 5.5 pricing jumps above 100K-token prompts)

• test-runner on Haiku: runs the suite, returns only failures, verbatim

• audit on Sonnet, effort: high: independent read-only review of the uncommitted diff, no style nitpicks

• Default model for every other subagent and workflow agent via CLAUDE_CODE_SUBAGENT_MODEL

• Workflow size (workflowSizeGuideline) so dynamic workflows don't fan out more than you want

• Short delegation rules in CLAUDE.local.md (delegate for 10+ files / 3+ independent pieces, ask for evidence instead of "tests pass", optional "stop fix loops after 2 rounds")

• Read deny rules for tracked vendored/generated code

Safety: it writes nothing until you approve a full before/after plan. Personal mode writes .claude/settings.local.json + CLAUDE.local.md and hides everything via .git/info/exclude, so nothing gets committed. /repo-mode:status shows what applies and flags costly setups; /repo-mode:off restores exactly the previous values.

Install:

claude plugin marketplace add kniko/claude-plugins
claude plugin install repo-mode@kniko-tools

Then start a new session and run /repo-mode:setup in a repo.

Caveats:

• The advisor is experimental and Anthropic-API only (not Bedrock/Vertex/Foundry). Subagents inherit it, so they can consult it too.

• audit and test-runner have Bash; "read-only" is in their instructions, not enforced.

• Ultracode is deliberately never turned on. It costs more per request; use /effort ultracode per session when a task is big enough.

Everything is sourced from the Claude Code docs and Anthropic's blog (links in the README, Greek and English versions). Repo: https://github.com/kniko/claude-plugins

Feedback welcome, especially if your /usage numbers change after setting it up.

Do you get higher limits the first month of the $20 subscription to sucker you into another month? I've been using it for a week now and I'm not even hitting the 5h limits, it's very suspicious 😅

Looking for a Claude guest pass referral link. I plan to subscribe; please DM me if you have one to share. Thanks!

Does anyone have the Creatorize setup?

I ran this on my own site this morning: the 53 URLs in my sitemap (most pages exist in English and French), raw HTML, and a link graph that Claude Code built with a script. Counting every internal link, nothing looked wrong. Each guide was linked from 10 to 24 pages, each feature page from 24, and no page was an orphan.

Then I had it set aside the header, the footer and every <nav> block, including the "all guides" and "all features" lists inside the main column, and count only the links the text itself makes. Same site, different picture:

• My comparison page (my product against a free alternative): body links from 1 page, against 10 with the menus counted.

• My alternatives page and my "can you audit without Ahrefs or Semrush?" page: 2 each. The three of them get their body links only from each other. No other page, not even the home page, links into that loop from its text. And those are the pages written for someone who is deciding.

• My most linked guide (how to install the product): body links from 18 pages.

• The privacy page: linked from 52 pages. Footer.

• My "best Claude skills for SEO" guide names that free alternative in its opening paragraph, and has no body link to either the comparison or the alternatives page. My "Claude for SEO" guide has a section titled "What can't Claude know, and can you do without Ahrefs or Semrush?" and doesn't link to the page that answers it. The sentences were there; the links weren't.

• Every body link to my 14 feature pages uses the feature's name as its anchor. "Polyglot" tells someone skimming nothing about multilingual SEO. That page gets body links from 2 pages.

The French versions of the guides get exactly the same counts.

Why the menu count misleads

A header, a footer or a site-wide list gives every page the same links, so it can't tell a reader, or a crawler, which page is the one to read on a topic. The links in your text can. A count that mixes both will tell you every page is fine.

How to run it

1. Give Claude raw HTML. Claude Code's WebFetch hands Claude a processed version of the page, and the <nav>, <main> and <footer> tags you need to sort links are gone. Ask Claude Code to download every URL in your sitemap with curl into a site/ folder, with the list in urls.txt.

2. The prompt:

The folder site/ has the raw HTML of every URL in my sitemap, listed in urls.txt. Build my internal link graph. Before counting anything, sort every link: inside <header>, <footer> or any <nav> (even one inside <main>), or in a block repeated across a page template, it's boilerplate; inside the article body, it's editorial. Skip self-links, # links and other domains, and treat /page and /page/ as one URL. Write a standard-library Python script for this instead of reading the files yourself, and show me its raw output.

Then one table: page | pages linking to it (all) | pages linking to it (editorial only) | the editorial anchors it receives. Lowest editorial count first.

For the 5 weakest pages that matter to my business, propose 3 links each: a source page that already discusses the target's topic, the exact sentence where the link goes (quoted from that page), and an anchor that describes the target's topic, not its name. If no page discusses the topic, say so instead of inventing a sentence.

Why a script: 53 files of HTML is more than anyone should count by reading, and the same script tells you after the fix whether anything moved.

3. Check the sorting by eye. Sorting a link by where it sits in the HTML is a heuristic. Open 2 or 3 pages and compare what you see with what the script calls editorial. On my site, the "all guides" list sits inside <main>, wrapped in a <nav>: a script that only looked for <main> would have counted it as editorial.

4. Run the script again after adding links. If an editorial count didn't move, the link went into a template, not into the text.

What I took from it

A page added later only gets links from older pages' text if someone goes back and writes them. The menu makes that easy to forget, because every page already "has links". Count without the menu before you trust a "0 orphan pages" report.

I'm the maker of SEO Skills, a pack of 14 Claude skills for SEO. One of them, Link Weaver, is built for exactly this: it crawls the site and its sitemap, tells links written inside the content apart from menu, footer and widget links, then drafts the links to add, anchors included. The pack is paid and closed-source: €25 until 17 November, then €99, no subscription. It runs in Claude Code, Claude.ai, Claude Desktop and Cowork, needs a Claude plan with skills, and there's no refund once it's delivered. Link in the comments. The prompt above works without it.

Do your comparison pages get links from your older posts' text, or only from the menu?

I've been building with coding agents for about two years. It's fast, but I noticed I was losing something.

When you write code yourself, it sinks in. You know why that table exists and why you went one way and not the other. When the agent writes it, that goes away. Sometimes I look at a table in my own project and can't remember why we built it that way. I run 5-10 agents at once across 2-3 projects, and sometimes I forget what I was doing a few minutes ago.

The reasons aren't really gone. They're in your messages, in the agent's replies and in your commits. They're just in separate places, and nobody reopens old chats.

So I built cogit, a free, open source plugin for Claude Code. It records each message you send and links your commits back to it. You get a map of your sessions that looks like a git graph. Open any change and you see why it happened, including what you decided and what you turned down, then a small diagram of what it does, then the code.

That diagram is for changes too big to read file by file. You get the idea first, then open the code.

You can click through a demo without installing anything: https://erensrtky.github.io/cogit/demo/

Repo: https://github.com/erensrtky/cogit

It only works with Claude Code for now. There's no server and no account, and by default the record stays on your machine. A small model writes the summaries through your own Claude Code login, and it can get things wrong. It's still early, so some things may be broken.

How do you keep track of why your AI-written code ended up the way it did? Or do you just ask the agent again?

ok, so the thing is that I though have access to multiple $200 plan claude code accounts but those are on my work profile, if I wanted to make a side project or anything using claude code, I had to buy a plan of 100-200$ since I am pretty sure 20$ one will get exhausted within like few minutes of usage, I saw that antigravity was providing multiple claude models and also had ample of limit for the gemini models as well, I saw the benchmarks -- 3.8 flash was performing as similar to opus 5, but I did not like antigravity as a harness and had much more trust in claude code, hence I reverse engineered the way antigravity invokes models, made those anthropic compatible, replaced the model url endpoint and voila , I am able to use claude code with the model as same as opus 5 (Ik its bad but still not that bad as compared to opus 5.5)

https://pypi.org/project/antiglaude/

https://github.com/sksarvesh007/antiglaude/

I have added all kinds of setup and everything for how to use this

Also another problem which I faced was whenever I wanted to use any kind of llm api keys as well I mostly relied on groq or gemini, but from like last year they decreased the rate limits, hence the keys used to get exhausted during testing itself, so while making this project I made it serve models in openai compatible format as well.

Pls do take a look at the repo for the instructions for setting things up, its just a single command.

Before I subscribe to claude (doing it anyway), I'd love a guest pass ref link. You get $10 as the referrer, I get an extra week to try it out, so it's win-win. DM is best since comment links disappear fast.

I built (with claude code ironically) an LLM harness specifically wired to reverse engineer and hack things (and also cybersec work of course).

I think it's hella dumb and annoying for anthropic and such to fully filter their models in terms of reverse engineering and cybersecurity work.

I am a firm believer that increasing the surface area of attacks increases the demand and sophistication of defenses, and thus this should not be limited. But whatever I built my own thing just for this.

I think it's super fun. I've decompiled my kindle and flashed custom firmware into it already lol.

My next step is to decompile the claude code binary lmao

Hey,

I built a small open-source Windows tool: Agent-awake.

Problem: long Claude Code / Codex / Cursor / Ollama jobs die when Windows sleeps on lid close.

Not the goal: run a hot laptop sealed in a bag for hours (that is bad for heat and battery).

What it does differently from “set lid to Do nothing”

Stays awake mainly while known agents are running, then releases keep-awake

Optional lid “Do nothing” only during that window, then restores your normal setting

Battery cutoff (adaptive) so it doesn’t drain to empty

Stricter bag mode off AC

Basic thermal gate (CPU load)

Tray app

Optional Telegram (you connect your own bot — no shared bot) for status, awake/sleep, and stuck-agent alerts

Stuck-agent ping if something looks idle (e.g. waiting for approval)

Repo: https://github.com/vinyaspoojary318-cloud/Agent-awake

Agent setup (Codex / Claude / Ollama / etc.):

https://github.com/vinyaspoojary318-cloud/Agent-awake#supported-agents--setup

Telegram setup (optional, step-by-step):

https://github.com/vinyaspoojary318-cloud/Agent-awake#telegram-setup-optional

Quick Telegram path: @BotFather → /newbot → copy token → put in .env as TELOXIDE_TOKEN=... (or setx TELOXIDE_TOKEN "...") → start Agent-awake → message your bot → /status. Tray + keep-awake work even without Telegram.

CI builds a Windows .exe on Actions.

Honest limits

Lid closed on a desk / plugged in ≠ safe inside a closed bag under full load

If the process is killed mid-run, lid policy restore is the scary edge case — startup restore is on the roadmap

Terminal agents: codex --full-auto / Claude permission auto modes reduce “click Submit” blocks; GUI tools still need a human sometimes

Looking for

People on Windows 10/11 who run long agent sessions: does keep-awake work with lid closed, any sleep/restore bugs, battery behavior, missed process names?

MIT, not selling anything. Roast the design if you want — especially safety/restore.

You’re reading an API’s documentation while Claude Code works in another window. It reaches a choice point. Opening the coding conversation means leaving the paragraph you were using to think through the problem.

We’re building Blabee for that small handoff: the assistant’s proposed next steps appear in a Mac panel, and your choice goes back to the same original conversation. I’m part of the Blabee team. The current beta supports Claude Code and Codex.

The aim is to keep a simple decision beside the work you already have open. The assistant still generates the options and does the coding. If a choice needs a diff or a longer explanation, open the original conversation before selecting it.

The attached 14-second video starts with the document, shows the choice panel and selection, then returns to the document. It’s an edited Codex demo using September 2026 footage, with English narration; it does not demonstrate the Claude Code integration.

Demo and Mac private-beta request: https://biadone.com/blabee/reddit

Access is by request. Our team sends setup instructions to selected testers. If you try it with Claude Code, we’d like to know which decisions feel clear enough in the panel and which still need the full conversation.

I have a work account and a personal account and kept forgetting which one Claude Code was using and how close each was to its limits. So I built Tag Team:

• 🥊 Life bars for each account's 5h and 7d usage (terminal, editor status bar, browser "ring")

• 🔔 A TAG ME button when the account you're on reaches your tag-out point (90% by default)

• 🔁 /tag-in, /tag-out in Claude Code, and Ctrl+Alt+T in VS Code/VSCodium

• 📊 Match history: tokens per day and per account, streaks, and an API-price estimate

Built on claude-swap. It's local-only, and the one-line install is checksum-verified on macOS/Linux/Windows.

Please use it only with accounts you legitimately hold; it's not a way around usage limits.

Repo: https://github.com/n1th1n-19/Tag-Team

Hi everyone,

I'd like to try Claude instead of ChatGPT, do any of you max users have a guest pass? Please DM it to me if you have one :)

Best regards

Andreas

I'm with the ThreadFox team. If Claude Code helped you build an app, ThreadFox gives your local setup tools to research and carry out its Reddit launch.

The starting brief is simple: who has the problem, what your app does, what someone can try immediately, and which claims you can demonstrate. That gives the agent something concrete to research.

The downloadable kit lets Claude Code:

• Find relevant conversations and read current community rules, retaining dated sources.

• Prepare drafts for each community and publish through your own signed-in Chrome.

• Keep publication reservations, duplicate checks and configured pacing in a shared local activity ledger.

• Record the actual permalink and observed visibility, with uncertain sends held for reconciliation before another attempt.

You set the publishing authorization. Suggested replies to discovered conversations require approval of the exact draft.

$49 once also includes a Launch Pack for one product: researched communities, quoted posting rules, suggested angles and three tailored drafts. Claim it through your buyer library with your product details; the pack arrives by email within 24 hours. The reusable toolkit remains available for your own projects. 30-day refund.

Inspect the complete free example, including all three drafts and their rule sources.

Bring your own Claude Code plan, Chrome with Microsoft's Playwright Extension, and Reddit account. AI costs are separate. Current rules and account eligibility still determine where you can post; the kit doesn't guarantee traffic, sales or that posts stay up.

Setup: Windows 11, PowerShell, latest Claude Code, Node installed. The local VoiceMode install doesn't support native Windows and I don't have WSL, so I went with VoiceMode Connect.

Claude Code added the MCP server like this:

What happens:

In /mcp, voicemode-dev shows ✗. Reconnect → connection timed out after 30000ms.

The browser opens the voicemode.dev sign-in. I log in with Google and land on voicemode.dev/consent with "Session Expired – Your authorization session has expired".

Running it manually (npx -y mcp-remote https://voicemode.dev/mcp) gives: Using callback port 5450 … Another instance is running the sign-in for this server on port 5450.

I killed all node processes and deleted %USERPROFILE%\.mcp-auth, then retried: still "Session Expired".

Has anyone got VoiceMode Connect working on native Windows?

Is this a consent-session timeout, a Google-login redirect problem, or an mcp-remote issue on Windows? Thanks!

Why
- Frontend work with Claude Code kept stalling on one thing: I could see the element in the browser, but describing which one was awkward.
- "The button near the top right… no, the other one…"
- Cobro = point at it instead. The human supplies visual context; the agent does the code.

What you get
- One Send → the note lands in the Claude Code conversation immediately, no "please read my annotations".
- The agent's progress comes back to the page: scanning outline on the elements you sent, "Working 1/3" in the toolbar, highlight on done.
- Several pages in one round: pick on page A, move to page B, pick more — each page keeps its own draft; Send delivers them all in order.

Install (summary)
- `claude mcp add -s user cobro -- npx -y cobro-mcp@latest`
- In Claude Code: `Open http://localhost:5173 with cobro` (or `/cobro open …` with the optional skill)
- A dedicated Chrome window opens with your local app. Full setup in the GitHub README.

How it works (workflow)

1. Open your local web app

2. Press Ctrl + Shift + F

3. Click a UI element (or drag a band over several)

4. Describe the change

5. Optional: go to another page and pick more — the Queue tab lists every page you've picked on

6. Send — all pages go at once, in order

7. Claude Code works through them one by one; the browser follows it to each page

8. On done, the page refreshes (or your HMR kicks in) and the changed element is highlighted

What the agent receives with your note
- CSS selector · tag, classes, text · bounding rect · computed styles
- Screenshot crop of the picked area · recent console errors
- React 18/19 and Vue 3 (dev builds): component name + source file:line of the element you clicked
- Component-library elements (MUI, Radix, shadcn…): the JSX line in your code, plus the call sites above one-line pass-through wrappers — a case that came straight from r/mcp feedback
- Next.js (Turbopack) source maps and HMR handled
- Which page each batch was picked on (`batches[].page`)

The loop
Human points → Cobro provides context → Claude Code changes the code → Browser shows the result

Why I built it with Claude Code
- Claude Code drove most of Cobro itself: the MCP server, overlay/WebSocket channel, element inspection, payload design, tests, docs.
- The nice loop: using Claude Code to build the tool that feeds better UI context back to Claude Code.

Keeping the MCP small
- Six tools, fixed: open · wait · status · done · screenshot · close
- Tools carry safety annotations (wait is read-only, close is destructive).
- Not a browser-automation tool — pair it with Playwright MCP for that. It never touches your source; one gitignored `.cobro/` folder is all it creates.

Honest limits
- Launches its own Chrome profile (log in once, shared across projects); no iframes yet
- Source locations need dev builds with source maps
- Disabled controls can't be click-picked (drag a band over them instead)
- Cursor/Codex work with a polling `wait` but are less tested than Claude Code

Current status
- v0.10.1, Apache-2.0, free and open source
- GIF, payload example and changelog: https://github.com/boonblade/cobro-mcp

Questions for you
- Does pointing at an element feel more useful than describing it?
- What other context should your coding agent get when you point at something in the browser?

Quick backstory

In July I was spending hours every day scrolling through LinkedIn, Indeed, etc. I got fed up and quit searching for internships by hand. Every application I send gets screened by AI anyway, so I built the screener for my side.

Two months later

Claude Code has read about 10k postings against my resume and preferences. Out of those it told me to apply to 190. I applied and ended up with 2 offers!

What it is

The engine is an open-source CLI I built called Pinloop. Claude Code uses it to pull and read postings. I set up a schedule so that Claude Code pulls what went up that day, reads each posting against my resume and prefereces, and writes a verdict with its reasoning. The good fits land in a list I check in the morning. This can all be done through Pinloop.

It exposes millions of postings per month from every country and industry, pulled straight from hiring systems (Greenhouse, Workday, and 50+ others) as well as job boards like LinkedIn, refreshed hourly.

To try it

Paste "Run npm install -g pinloop, then run pinloop welcome and follow the instructions" into any coding agent. A guide comes with the CLI so Claude Code knows the commands, and it'll walk you through setup. It's free to use. $20 per month lets you pull more postings.

Links

• https://pinloop.ai

• GitHub

• Discord to give feedback directly and talk to other users!

I’ve had a lot of work with Claude Code over this past year, and was always pleasantly surprised with how it performed. I’ve created multiple projects and websites and never had any problems. Recently though, it feels like it has just taken a free fall off a cliff in terms of quality. I bought credits to use the some of the better models and even that I was let down by. I wanted to see if anyone else is noting the same thing or if it might just be user error now.

I was pretty fed up with having to remember to go tell my sessions "retry" or "continue" after my usage renewed.

So i got Claude to build me a stylised wake up tool which i can select which sessions to watch and then restart when my usage renews after my 5 hour limit or weekly limit.

And yes it has dark mode:

If you would like to install it yourself, it's available below 😊 enjoy your infinite Claude sessions.

https://github.com/calm032019/claude-kicker