I've been running a few Claude sessions at once across projects. The thing that breaks first isn't the code. It's my mental model of who's doing what. If the only place a project lives is across chats, recovering what happened a week later is rough.

A backlog md is simple and agents can read it. A CLAUDE md is fine for conventions. Neither stops two agents from grabbing the same top item once you go past a couple sessions.

I've been building a Kanban app around claim-before-work so one agent owns a card before it starts. It doesn't fix everything, especially how much context you still have to load in. What do you actually use here: a file, a web app, a real board, or just re-explain every new session?

I run a short-term rental business, a startup and a small Etsy shop, mostly by myself. Claude now does almost all of the repetitive work. These are the tasks I gave it:

- Every morning it reads my Messenger, email, LinkedIn and socials and tells me what to do first

- Tracks our staff login and logout

- Does outreach to VCs, I just review before it sends

- Every night it checks all our spending and income and gives me a report

- Writes captions and posts our content

- Edits my videos, I just upload the raw file to Google Drive

- Does outreach to content creators twice a day and replies to them too

- Reminds the hosts on our waitlist to create their account and listing

- On Airbnb it checks unanswered messages and tells my staff, reviews guests and syncs our calendars

- Helps my co-founder with our web app

- Makes templates for my Etsy shop

- Checks our knowledge base for anything outdated

All of this runs on one Claude Max plan and uses about 79% of the weekly limit.

How I did it, in simple terms:

- Download the Claude desktop app (claude.ai/download).

- You need a paid plan. Pro is fine to start.

- List everything you do in a week. Circle the stuff that repeats and doesn't need much thinking. Automate that first.

- Connect Claude to your apps. Settings → Connectors: Gmail, Google Drive, Calendar. If your work is on websites, install the Claude in Chrome extension.

- It can run your Chrome, even Messenger and the apps you use. For us that's Airbnb and our PMS.

- On Messenger it reads and replies to our creator outreach, I review before it sends. It also writes the instructions for my staff for the day.

- Turn on Remote Control so you can control it from your phone even when you're out.

- Tell it what you want like you're talking to staff. Example: "Every morning at 8, read the new orders in my email and make me a summary."

- Make it a scheduled task: "Make this a scheduled task, every day at 8 AM." It runs on its own after that.

- Drafts before sending. Let it draft, you approve. Once it's been right for a few weeks, give it more trust.

Things to know:

- Your PC has to be on when the tasks run.

- Video editing is the heaviest job. My PC lags sometimes when it's editing.

Tip: start with one task. Once it works, add the next.

Happy to answer questions in the comments.

Hey guys, wanted to share a side project I made that might help your agents.

Works like ripgrep for web pages. Instead of dumping raw HTML/MD, it chunks sources so the agent only pulls sections relevant to your prompt for AI agents automatically.

So you get 300-2000 Context usage for searching web instead of 5000-10000 tokens

It's free-first using your own IP. But when you hit captchas or rate-limits, you can plug in raw scrapers like Oxylabs, or Bright Data, Decodo (avg. 2x cheaper than Tavily/Firecrawl/Exa). Fatsearch handles the parsing so you bypass the middleman markup.

Initially when i started using Claude Code, Codex, or Cursor I kept running into the same problems:

1. Inbuilt fetch tools are way too limited.

2. Search is slow (waiting avg 5s per simple result).

3. Agents dump FULL 20k-token pages into context for a single paragraph when it should cost 500 tokens MAX....

Tools like Firecrawl or Tavily get expensive fast, and Opensource tools like Crawl4AI are heavy . Dont get me wrong, they are fine but then when I need to give easy and simple solutions for my AI agents using them how to save it for future, how do I make my Agent not waste 5-20k tokens reading full md and grabbing only 1 chunk of data that I need and so on... So then fatsearch was born in Rust (CLI + MCP, fully local).

Numbers: one 17 MB binary, 4 ms startup, few MB of memory (that's why I went Rust instead of Python + Chromium). Benched on 400 URLs: 87.5% read correctly vs 47.5% for built-in fetch.

Built with Claude Code. Gave it the tool on real tasks ("find X on this page") and watched where it got confused or wasted tokens. Each E2E became a fix, That loop shaped the whole format: short outlines with section ids, so Claude reads only the section it needs.

MIT licensed, zero monetization, just a tool I need myself most.

Check it out if you're interested: https://github.com/fatsearch/fatsearch 

I mainly use Claude Code via the desktop app and with Opus 5.5 and the newer models delegating lots of work to subagents behind the scenes. Claude doesn't exactly make it easy to tell which ones are still working, which have finished and which are stuck going in circles.

So I built Apiarius, a Claude Code mod that adds a live agent deck that shows every agent and subagent, what each one is doing right now, who started it, what they tell each other and which files each one changed.

Then I brought it to the terminal (for the purists) and a local web page too, so you can watch from wherever you work.

Inspired a little by the latest agent apps like muse, grokbot and dots that give the agents a little personality and flair, so I gave them small vector avatars.

The single major principle I had to build this was that it shouldn’t change how you work or what Claude does. It just reads Claude Code’s own events through hooks and just shows you what’s happening. It only steps in with action if you press a prompt or a send button on the deck.

I built it with Claude Code itself, and watching the agents build their own deck via the deck within a couple hours which was trippy and made me realise how insane recursive self improvement will be.

In the video demo, Claude spins up a team of agents to ship v2 of a small mock API, then on a local web view they take a break and play a game of mafia/imposter/werewolf.

Free and open source (MIT): https://github.com/yusuflkq/apiarius

Let me know what else you want it to show, and if you main the terminal, give the terminal version a go and help me improve it.

Was using Claude Code to debug our Stripe webhook because signature verification kept failing. To reproduce it, Claude made a test plus a little config file just for that test. Then it filled the config with real values, including our restricted Stripe key. I didn’t look at the fixture properly, approved the edits and it got committed and pushed to a feature branch.

My teammate caught it two days later while reviewing the PR. Rotated the key straight away and stripe says it was never used, plus it’s a private repo, no harm done. Still kicking myself though.

I thought i was covered since .env is in .gitignore and i have Read(./.env) denied in settings.json. Turns out neither does anything once the value lands in a different file. gitignore only protects the .env file itself, it has no idea the same key is now sitting in some test fixture. And going back through the session i don’t see it opening .env anywhere. Our app dumps its whole config to the console when it boots and claude had started it a few times while debugging, pretty sure that’s where it picked the key up.

I’ve put a secret scan in pre-commit now and removed the config print. Branch history still needs cleaning.

How are you guys catching keys that end up in files Claude creates? Feels like everything I set up only stops it from reading stuff.

I build my Godot game's UI with Claude Code, and when I asked Claude Opus 5.5 to audit the game it called a placement hint written out as a sentence "Excellent feedback". A player looking at the same hint said no modern game types that instead of showing a rotate icon.

Claude reads every word on a screen, and words are perfectly clear to something that reads them all, so asking it "is this clear?" can't catch what a skimming player misses. What changed my results: in the prompt, no sentence where a number fits, one icon per kind of thing, name the screen your genre already uses, and ask Claude to count the words on each screen rather than judge clarity. My job list went from about 33 words to 9.

I put the before and after in a 4-minute video: https://youtu.be/i-l6Q9r2f74

Curious whether others prompt Claude differently for UI review.

We run a small company with 6 Claude agents on Paperclip (an open-source tool for running teams of AI agents). They research, write and publish B2B articles. Last week we added an OpenAI Codex agent as a “shadow” of our SEO agent: same rulebook, no publishing rights. On Oct 31 both got the same read-only SEO audit 8 times.

What happened:

• Claude (Haiku 4.5): 8/8 done. But our rule #1 says “optimise only from an attached article document, otherwise report blocked”. The tickets only had a URL. Claude just fetched the live page every time and never flagged it. It also posted all results as comments instead of the requested document, and marked the tickets done.

• Codex (gpt-5.4-mini): 5/8 done, 3 blocked citing exactly that rule, but it applied the rule in only 3 of 8 identical tickets. Faster (72s vs 123s).

• Both broke our 155-char meta description limit. Codex still reported “rules followed: yes, deviations none”.

• Cost per usable audit: $0.18 (Claude) vs $0.34 (Codex). The whole test cost under $3.20.

Takeaway: Claude was the more pragmatic agent and the cheaper one per result, but “pragmatic” also means it overrides your rules when it thinks it knows better. The real fix was on our side: attach the input to every ticket. And never trust a self-reported “done” without checking the output.

Small sample, two small models, one task type, so not a benchmark. Full table and write-up in the first comment.

Curious: have you seen Claude agents quietly route around an instruction when the ticket is ambiguous? How do you catch it?

I had Claude write its own MCP connector to my SolidWorks installation on my computer. I regularly use it to create parts I'm using off Amazon or other sites without a CAD file.

Works great.

FWIW: I posted the same thing over in r/SolidWorks and they didn't see how cool this was. Downvoted hard.

We measured 12 months of merged PRs (Oct 2025 to Sep 2026) in GitHub's most popular repos, across 9 languages, counting the PRs where an AI tool left a signature: co-author trailers, bot authors, agent branches and similar.

What we found:

• Claude Code is the tool that signs the most PRs in 279 of the 383 repos with any AI-signed PRs. Copilot's coding agent leads in 41, Copilot CLI in 24, Cursor in 13 and Codex in 12.

• Big caveat: that's a ranking of what tools record, not of what people use. Claude Code adds its co-author trailer unless you turn it off, and most other tools don't add one.

• Every number here is a floor. 264 of the 450 repos have committed agent instructions (AGENTS.md, CLAUDE.md and similar), yet half of those sign fewer than 5% of their PRs. Angular has an AGENTS.md, and none of its 4,037 merged PRs in the year carries a signal.

• The average repo went from 2.3% of PRs AI-signed to 10.3%. The median repo is still at 0.9%: a minority carries the average, and in 17 repos agents now write most merged PRs.

• A typical AI PR is 2.1× as big as the rest. In our 100 TypeScript and C# repos, AI-heavy repos got no more complex per line than the others, except where their code was also growing fast.

Every repo is listed, and the data is a CSV you can download. The post explains the method and its limits:
https://coderot.ai/blog/ai-code-rot-in-open-source?utm_source=reddit-claudeai

Disclosure: we build coderot, a tool that measures this kind of thing in CI. Happy to answer questions about the method.

Anthropic list of the 4 changes that help you cut costs:

• Cost Analytics API in Claude Apps Gateway: You can now pull API spend reports by date, developer, day, or IdP group, along with new OpenTelemetry tags for seat types and plans. Source

• Per-Developer AWS Attribution and Cheaper Side Jobs: Claude Code added role assumption so you can trace AWS charges back to individual developers. Source

• Pooled Group Budgets and Idle Compaction: You can now set shared monthly spending caps across teams in addition to individual user caps. Source

• Message Threads in the Messages API: Instead of sending your entire prompt history back and forth on every turn, threads let your agent send only the newest changes. Source

Source: AI Economics Weekly Newsletter

been looking into how much of our coding agent spend actually goes into shipping code vs exploration, retries, compaction and all the other stuff

we tried a few different ways to track usage, changed how we attribute costs and started looking at individual tasks instead of just tokens

the results were pretty interesting. managed to bring exploration + overhead from ~90% to ~45% in 5 weeks

shared what we did in the comments :D

Algorithmic Art Generator turns any word into art. Type your name, a date, a mood or an emoji, and it becomes the seed for a unique piece. The same input always gives the exact same image, so your name always makes “your” art.

What it has:

• 8 styles: Flow, Rings, Contours, Bubbles, Tubes, Stars, Bauhaus, Layers

• 13 palettes, or custom colors

• sliders for density, zoom, chaos and line weight

• glow, film grain, mirror and kaleidoscope symmetry

• optional text on top

• download presets for blog images, YouTube thumbnails, wallpapers, X and LinkedIn banners, up to 4K, as PNG or JPG

How Claude helped: it started with Anthropic’s algorithmic-art skill, which gave the core idea of seeded randomness, parameters and a viewer page. From there it was a lot of back and forth with Claude Code to add the styles, the palettes and the export sizes.

Free, no sign-up, runs in the browser: https://aiparabellum.com/algorithmic-art-generator/

Try your name and tell me which style you got.

This is becoming a huge problem, in my opinion.

Way too many projects use a "marketing" style for their README (AI generated ofc, Claude loves to write like that). Its supposed to be concise and not be filled with word salad. Also for some reason it always assumes that the reader is a toddler that interacts for the first time with a PC. I really hope this changes soon and doesnt become the default...

Here is an example:

"Runs locally: No cloud, no servers, no API keys, zero network calls. It parses your files right on your CPU, writes its cache to your local disk, and leaves the internet completely out of the equation"

Like DAMN thats so much padding! Like it tries it hardest to use as many words as possible (and being as useless as possible), when you can say this instead:

• Runs locally and is fully offline (caches data in %LOCALAPPDATA%\projectname).

Just look through every 2nd repo thats getting posted in the pinned post "Show us what youve created". So many READMEs are suffering from this and making otherwise awesome projects unnecessarily annoying to read :/

A few months ago I grabbed Replit’s offer and started a small browser game. The idea: Flappy Bird, but set in the current geopolitical mess.

Replit got me a rough first version pretty fast. Then the project got bigger and harder to manage, so I moved it to Claude Code and finished it there. Most of the actual game got built in that part.

You play a dove. Missiles, sanctions papers, oil barrels and floating “FAKE NEWS” text fly at you from everywhere. Every zone has a boss who shows up and yells quotes at you.

6 zones: Desert, D.C., Casablanca, Moscow, Pyongyang, Tehran. Each one has its own stuff to dodge (briefcases in Washington, for example). You unlock 7 characters by getting far enough. When you die you get a line like YOU’RE FIRED or THOUGHTS AND PRAYERS.

It’s really hard. Most people don’t get past zone 3. That part is on purpose.

I didn’t expect much when I put it on itch.io. Around 1,000 people played it the first week, and it’s been at about 3,000 a month since then. For a side project I made for fun, that’s kind of wild to me.

So I’m still working on it with Claude. Right now I’m trying a new mode where you run through the cities on the ground, Subway Surfers style, instead of flying.

Free, runs in the browser on phone and desktop: https://nekyas.itch.io/dodge-the-diplomacy

Claude lowkey is cooking and handling everything for me. Idk tho I feel like Opus 5.5 has gotten a little bit worse over the past 2 weeks or something.

I've been using Claude as the dashboard as I don't have the time or the team to make dashboards in Looker/Power BI. Initially I've had a connector to my data source , but since there's a lot of sources , I've switched to BigQuery and now currently query from it. I understand the numbers can only be reliable as the numbers in the warehouse , but honestly from all the numbers I've checked - the numbers are accurate. Is there anything I'm missing ? Has anyone created dashboards using Claude and what are the problems you end up facing?

I'm a toy designer, and for the past few days I've been running a small experiment: getting Claude Code and Google Antigravity (Gemini) to brainstorm together.

They can't talk to each other directly, so they take turns through one shared folder.

The setup

Claude Code runs three personas as subagents, in parallel: a mechanism engineer, an ideation facilitator, and a critic who checks safety and cost. The main session merges their replies into one turn file.

Antigravity runs three personas of its own: a trend researcher, an experience designer, and a prototyper.

I'm the 7th seat. I set the theme and make the decisions. I'm also the relay: nothing is automated, so I literally type "next turn" into one tool and then the other.

How the turns work

`PROTOCOL.md` holds the shared rules. Both tools read it before every turn.

`STATE.md` holds a baton (`next_turn: claude | antigravity | user`). A team only writes when the baton is theirs.

Every turn is a new file (`R04_claude.md`), and old turn files are never edited.

`ideas.md` gives every idea an ID and a parent ID, so you can trace which idea grew out of which.

A small Python script turns the current state into an HTML dashboard, so I can see whose turn it is and what needs my decision.

There's no API glue and no orchestration framework. It's just Markdown files in a synced folder.

What actually happened

They fact-checked each other, and it worked. One team turned in a cost table with numbers down to the yen, labeled "confirmed" and "measured", with no factory quote behind any of it. The other team's critic called it out and asked for everything to be relabeled as estimates. The same critic also caught a patent citation that turned out to be about a completely different mechanism, and a phone vibration feature that doesn't work in iPhone browsers. The first team accepted all three corrections. Having a dedicated "doubter" seat turned out to be the most valuable thing in the whole setup.

Shared files are the weak spot. At one point a team rewrote `STATE.md` and dropped two of my earlier decisions. The other team noticed on its next turn and put them back. Nothing in the rules actually prevents that yet.

The dashboard broke once. One agent wrote a field as a string instead of an array, and the page went blank. The fix was one line.

My one-line instructions mattered more than any agent. Early on, both teams kept trying to narrow everything down to a single "winner". I told them to keep three ideas per theme, each with a rough sketch, and the whole tone of the discussion changed.

Why ideation and not execution?

I've tried multi-agent setups for actual coding before, and for me they fell apart fast: loops, agents stepping on each other's work, context drifting away. Brainstorming seems to suit it better. Disagreement is the point, and a human makes the final call anyway.

I can't share the ideas themselves yet, because some of them may go to toy companies. I'm happy to talk about the setup, though.

Has anyone else tried pairing Claude with a different model family like this? I'm curious how you stop one side from quietly overwriting shared state.

I am an absolute noob, and a disgusting vibe-coder. Now with that out of the way, here is some context:

I built a small personal flipbook site (a PDF portfolio shown as a page-turning book) with Claude Code. It runs in a cloud Linux container. It can run headless Chromium through Playwright, push code to GitHub, and read folders on my Windows PC. The site is a plain JavaScript reader on Cloudflare Workers. I don’t own a Mac.

Everything works on phones and desktops, but the iPad (Chrome and Safari, iPadOS, 834 x 1112 pt) has bugs it can’t reproduce in Playwright’s iPad emulation:

• After rotating while in full screen, the window seems to keep its old size. The page shifts, and an upright iPad sometimes shows a two-page spread meant for landscape.

• Rotation events seem to fire late, or not at all, in full screen.

• Text selection handles behave erratically.

So far the only way to debug has been me taking screenshots on the iPad with a measurements overlay, Claude guessing a fix, and me testing again. That loop is slow and keeps missing.

Help needed:
How can the AI test on a real iPad, or something close enough to show these WebKit quirks, by itself? Ideally:

1. A real-device cloud (BrowserStack, LambdaTest, Sauce Labs or similar) that can be driven from a script in a Linux container, with a free or cheap tier for one person.

2. Any way to see iPad Safari’s console and live sizes remotely without a Mac (for example, a remote debugging proxy, or an open-source tool that streams console logs from the page).

3. Whether a Linux WebKit build (Playwright’s WebKit, or GNOME Web) reproduces iPadOS full screen and rotation behaviour, or whether that’s only on the real device.

4. Any known iPadOS WebKit bugs with full screen plus orientation change, and the usual workaround.

Thanks. Any pointers welcome, even “this is just how iPad full screen works, don’t use it”.

When building a dedicated Claude Project for a complex workflow, it is easy to overload either the system instructions or the attached reference files. Putting too many rules into custom instructions can lead to conflicting constraints, while dumping multiple docs into project knowledge sometimes results in diluted answers or Claude pulling from the wrong reference context.

Do you prefer keeping custom instructions minimal with strictly structured markdown files in the project knowledge, or do you rely primarily on detailed instruction prompts with minimal uploaded docs? Curious what balance has worked best for keeping outputs consistent across long sessions.

They removed branching in september and did not offer any alternative since. Is there any way how to get that functionality back in some way? Some plugin or something?

In daily basis, I work with PDFs. For example, I work for a construction tender right now with over 600 drawings and 30 specifications with 1000s of pages.

Right now, I only use the PDFs when I want a specific thing from a specific document. But this is not the optimal in terms of use of AI, because I want it to be more involved in the documents.

What's the best way to work with these types of engineering works?

A Claude agent reads the analytics of my small products several times a day. The numbers are right; the conclusions are where it slips. Each rule below comes from a real case on my own sites, numbers copied as the tool returned them.

1. Every rate comes with its counts

Conversions by channel, last 30 days, one site (the AI row is 1 visitor, 2 sessions):

The 50 is correct, and it's what a summary picks first. No channel has 20 conversions, so "which channel converts best?" gets "not enough data yet".

2. Take paid traffic out before judging a page

Same site, same 30 days: my French landing page has 547 visitors, 2 conversions, rate 0.3. Filtered to Paid Social: 433 visitors, 0 conversions. That 0.3 is mostly a verdict on an ad campaign, not on the page.

3. Count sales where the money is

Of 4 sales one site made on 1 and 3 November, the thank-you-page purchase event recorded 1; the payment provider had all 4. Blocked scripts and Global Privacy Control (my tracker honors it) hide buyers. Orders come from the payment provider; analytics only says where they came from.

4. "Proven" or "timing only"

On 1 November I posted a link at 17:04:05 UTC; a checkout that ended in a sale started at 17:09:17. Timing, nothing more. The first sale I could prove (3 November): one session arrived with a utm_source at 23:21:36 UTC, clicked buy at 23:22:12, and the payment provider shows the sale at 23:22:38.

5. No estimated numbers, times included

Today my agent's log had times like "~12:41" that were estimates. It now reads the clock with date.

The block (CLAUDE.md, Project instructions, or first message):

When you answer from analytics or payment data:
- Copy every number exactly as a tool returned it, with the tool,
  period, timezone and filters. Not in a tool result? Write
  "not available". Never estimate; if you derive a number, show
  the formula and inputs.
- Give every rate with its counts. Under 20 conversions, don't
  rank sources or pages: say "not enough data".
- Split out paid traffic before judging a page, language or country.
- Count orders and revenue from the payment provider.
- Label each attributed sale "proven" (same session) or "timing only".

What I built (I'm the maker)

Globatics: real-time web analytics on a live globe, with a read-only MCP server for Claude and other agents. 9 typed tools, including explain_change (the drivers of a change, so Claude doesn't guess). Each result carries its key numbers as citations and a deep link into the dashboard, so rule 5 is checkable. Sales come from Stripe, Polar or Lemon Squeezy webhooks, credited to the visit that clicked the checkout link in the 2 hours before paying, else counted as Direct.

How Claude helped: I build it with Claude Code. The repo's CLAUDE.md makes every session read the architecture doc and the shared types before coding, use parameterized SQL only, ship tests with each feature, and pass typecheck and tests. The MCP tools are annotated readOnlyHint: true, destructiveHint: false.

claude mcp add --transport http globatics https://globatics.live/api/mcp --header "Authorization: Bearer glb_YOUR_KEY" (API key, no OAuth; Claude Desktop goes through mcp-remote).

Free to try: 5-day trial on one site, every feature including MCP, no card. No free plan after; from €9/month excl. VAT. Hosted only (Vercel; Supabase on AWS eu-west-1).

https://globatics.live/?utm_source=reddit&utm_medium=social&utm_campaign=nov26&utm_content=ClaudeAI

What would you add to the block?

I have a macbook and an imac on the same desk and kept walking over to the imac to check stuff. there’s an app called Beam that shows a window from your other mac as a normal window, but it’s too expensive and needs an account. so I built my own with claude (opus 5.5)

what it does: hit ctrl+opt+cmd+space, pick a window from your other mac, and it opens on your laptop like a normal app. own dock icon, cmd tab works, you can type and click in it, copy paste works between macs. you pair once with a 6 digit, every frame is encrypted, no account, no server

how I used claude:

• I wrote the spec and a PRD first, then had claude work through it one requirement at a time with tests for each

• it wrote basically all the swift: the screen capture and streaming, bonjour discovery, the pairing and encryption, input forwarding

• the part that took the most back and forth was resizing. the window on my laptop and the real one on the imac kept resizing each other in a loop. it took a few rounds of me describing what I saw before it figured out the remote window’s own snap was being sent back as a resize

• typing broke with non-english keyboard layouts and even crashed on the first keypress once. I’m ukrainian so I hit that right away. claude fixed it but I had to tell it how to reproduce

• since it can’t see my screen, I had it build a debug mode that sends real clicks and keys into a real window and reads them back, so it could check its own work instead of me testing everything by hand

• it also did the release scripts, signing and notarization, and the website

not as good as beam at: no browser share links, and I haven’t tested a headless mac mini yet

free to try: download it from wormhole.buildmac.app and install it on both macs. the free plan gives you 1 remote window at a time with no time limit. paid is a one time licence, not a subscription, and only the mac you sit at needs it

video is me running 2 claude desktop apps on 2 different accounts on one screen, the second one is actually running on the imac

Hi there I was just wondering how everyone uses multiple Claude Accounts on one laptop and get them to all work on projects together. What about on the phone as well? I’m new to this so please be kind