I am shocked , today it seemed that Claude really outperformed or had a serious bug. It happened twice that just asking a single task the bar of the 5 hours limits just goes crazy and saturates… did it happen to some of you as well? I am speechless, I don’t even know what I paid for (ok, I’m on the 20$ plan, but still , I cannot make a question and get an answer because it saturates my token in 2 minutes and I’m unable to ask anything different for the rest of the time in 5 hours… )

I teach Claude for a living, and am often asked whether to use Claude Cowork or Code.

Cowork is a brilliant stepping stone from Chat to Code, but it still can't read previous session transcripts.

If you ask Cowork "look through my existing conversations and suggest some new skills to save me time"

it will tell you it can't read past chats!

Anyone found a workaround for this?

Comprei um curso na Hotmart, queria por um Claude pra assistir e me ajudar a construir uma estratégia. Alguém sabe se tem como? Não quero ter q assinar pra poder testar.

I let my company's books drift for months. Claude Cowork cleared the backlog in one sitting - About 1 hour 50 minutes, but the part worth writing up is where it got stuck.

Context. Small agency in India. Zoho Books is our system of record, but I'd only ever entered the "important" stuff - client receipts and vendor payments. Everything else never made it in: bank charges, card spends, freelancer payouts, director drawings. So the bank balance sitting in Zoho and the balance in my actual bank account had drifted a long way apart, and I'd been avoiding it for months.

I gave Claude Cowork my bank statement export and my open Zoho Books tab, and asked it to fix it.

It did the boring part first, which turned out to matter

Before touching anything, it built a reconciliation bridge: the balance Zoho was showing, minus the transactions never entered, plus the opening balance never set, plus one client receipt recorded short, plus one receipt dated wrong, equals the real bank balance. It tied exactly on the first attempt.

That sounds like busywork. It wasn't. It meant there was a hard target to verify against at the end, instead of a vibe. It caught a bug later that I'd otherwise have shipped.

The root causes were all mundane: only a small fraction of the year's transactions were ever entered, the bank account's opening balance in Zoho was left at zero, one payment gateway payout was recorded short, and one receipt was dated eleven days off.

Then the walls

1. Getting the file in. The statement was processed in Claude's cloud sandbox, but Zoho was open in a browser on my machine. Rather than making me download and re-upload, it built the import file and attached it to Zoho's upload control programmatically. Small thing, but it's the kind of gap that usually breaks these workflows.

2. Importing is not the same as posting. Zoho parked every imported line as "uncategorised", and the account balance doesn't move until each line is categorised. So the import reported success and changed absolutely nothing. Easy to declare victory here and be wrong.

3. Bulk categorise caps out, and won't touch equity. Zoho's bulk tool does 50 rows at a time. Worse, director drawings post to an equity account, and equity accounts simply aren't offered in the bulk grid, which killed the obvious approach for the single largest group of transactions.

4. The unlock was rules, not bulk actions. Zoho has Transaction Rules that auto-categorise on import, and those can post to equity. So the real fix was: undo the import, write a handful of description-matching rules, re-import, let the rules do the work on the way in.

5. GST validation, which cost the most time. Rules fired, and every single expense failed with "It is mandatory to apply GST on all expenses." A 0% tax group wasn't enough. Tax Exempt demanded an exemption reason, and the one we created refused to appear in the dropdown. Registered Business demanded a vendor GSTIN we didn't have. The setting that actually works is GST Treatment = Out Of Scope, which drops the entire GST block off the transaction. Nothing signposts that.

6. Rules only fire at import time. Editing a rule doesn't re-run it over rows already sitting there. So every rule fix meant undo the import, fix, re-import. We did that loop twice.

7. A silent duplicate exclusion. Zoho quietly auto-excluded one genuine card transaction as a "duplicate" because an identical amount appeared a few days earlier. It gets parked in a tab you would never think to open. The only reason it was caught is that the reconciliation was expected to tie exactly and it was off by precisely that one transaction.

8. Opening balance semantics. Setting the opening balance made things worse, not better. Turns out transactions dated on the migration date are treated as pre-migration and get overwritten by the opening balance figure. Back-dating the migration date by one day fixed it.

End state: every line categorised, and Zoho's balance matches the bank to the paisa.

What I'd actually take away

• It was strong on accounting reasoning and relentless on UI grind. The two things I'm bad at, in different ways.
• It asked instead of guessing on judgement calls — which equity account drawings should hit, whether director pay is an expense or a drawing, whether a regular monthly payee is staff or a contractor. Those aren't lookups, they're decisions, and it correctly treated them as mine.
• Having a number to verify against changed the outcome. Without the bridge, the silent duplicate exclusion would have sailed through and I'd have been off with no idea why.
• Most of the elapsed time went to platform quirks, not to the actual work. If you're doing this yourself, the two that will get you are Out Of Scope for GST treatment, and the migration-date-inclusive opening balance.

Happy to answer questions on the rule setup if anyone's fighting the same thing.

I started using additional AIs to help manage and grow my Cowork Ecosystem and it's been super beneficial to not worry about usage all the time and to access top tier models all the time.

My system is now fully accessible by any agent I choose but the only remaining Claude native thing that's holding me back are the scheduled automations.

I was wondering if any of you have dealt with transitioning from built in scheduled automations in the Claude desktop app to a self owned system. One in which I can choose which agents launch a task and which device I can launch from.

I use a stronger model for planning and a weaker model for coding, but the result isn't very good.

Which produces better results in real-world use?
Or do you use another approach/workflow?
what's the best workflow?

I'm using the native google drive connector but aren't able to edit google sheets directly, only create them. What have you guys been doing?

Edit:
What I've found so far.
Remote support and least amount of setup
- Zapier MCP is pretty good on sheets and supports mobile connections
- Datatorag MCP offers the same and focuses on google workspace.

Desktop support
- host xlxs files and upload to drive. not a bad workaround but can only do on desktop.
- same with libre office, move the files to drive after.

Need to be techincal
- Open-source options where you have to setup OAuth and run it locally.
- Create service account and ask claude to build it out for you.

Why can we not sort by date anymore on our Claude Cowork project threads anymore? I have to find what is the latest thing I worked on...why was this changed? Anyone else annoyed by this? Just Chat has sort by date...

What’s the easiest way to go from an HTML made with Claude to a public website?

There’s a built-in way to publish artifacts, but it’s hard to control and no custom domain.

Claude code can take it but is that a smooth flow? Assume no engineers in process and it’s a simple site, interactive, rich, but no login/database.

I’m currently on the Claude Pro plan and Anthropic is running a promotion that increases Claude Code’s weekly limit by 50%

Does this promotion also applies to Claude Cowork, or is the 50% increase specifically for Claude Code only?

I’m mainly using Cowork rather than Claude Code, so I’m wondering whether I would actually benefit from the increased limit.

What has Claude Cowork actually done on your behalf, rather than just helping you do it?

I mean stuff where you gave it a goal and it went off and handled the work itself.

Has it ever:

• applied to jobs for you?
• posted on X or other social media?
• managed emails or messages?
• monitored something and acted when needed?
• automated some annoying repetitive task?
• basically become a little bot that does something useful for you?

I’m especially curious about projects where Cowork is connected to other apps/tools and can actually take actions, not just generate text or code.

What did you build, and how autonomous is it?

I believe after auto update last night/early morning, the sandbox VM inside Claude Cowork is failing on my MacOS. I have now spent more than 3+ hours debugging this through Claude, and it has not worked. Anyone with same issue with a resolution?

Title! I can’t see a reason projects SHOULD be local. Anyone able to present a case for it?

Reasoning: it feels more safe. I backup my computer every night, but still local feels risky? I have project folders on my desktop with a ton of information, including everything Claude makes for me.

Is there any reason it’s EASIER for Claude to invoke skills, pull context (reference.md’s etc) if it’s cloud based? As Claude makes things for me (including those HTML mockups, handoff md’s), would that auto-publish to a cloud project?

Forgive me if I am confused or sound naive. I’m trying to learn :)

Has anyone here used Claude Cowork while working on an Arduino project?

I’m curious how useful it is for hardware projects, like writing the code, debugging issues, working with sensors and libraries, and figuring out why something refuses to work for absolutely no reason.

If you’ve tried it, what did you build? And how much did Cowork actually help?

Having trouble finding the exact steps on having Claude execute trades. Can someone help?

I feel like I’ve seen posts for people setting up their AI agents to fully run instagram accounts for marketing, testing softwares autonomously, and other tasks that would normally take hours of normal work.

I’ve been using cowork to build a few personal apps, but it would be great to set up an instagram account for one of them and see what sort of marketing Claude could come up with (basically run it by itself). Is this a completely different AI system or am I seeing things that are likely fabrications from people and AI agents aren’t actually doing all that work.

I’ve been running Cowork with separate projects for engineering, creative, etc., coordinated by a Chief of Staff project, and ran into an interesting problem: one project seems to have lost enough shared context that it now questions/rejects instructions from the Chief unless I explicitly say they came from me. Even when told to independently verify against the working model and Asana decisions, it found a small contradiction and fixated on that as evidence the Chief wasn’t acting in good faith. Has anyone else experienced this? I’d also love to hear better practices for keeping project memory separated while still reconciling context in real time, especially when projects have dependencies where one needs to start immediately after another finishes and waiting for the next scheduled Asana check-in isn’t really workable.

https://preview.redd.it/r6l235n1uhjh1.jpg?width=3024&format=pjpg&auto=webp&s=853b07bf99eebc5371c86cada727f2307dbffb81

Hi everyone, I’ve decided to move the management of a large digital transformation project into Claude Cowork, and I’ve hit a problem much earlier than expected: how should I structure the project knowledge so it can scale?

For context, this is a fairly complex project:

• ~2 years of accumulated project data
• Confluence + local files
• Jira, Slack and Microsoft 365/Teams
• ~15 vendors
• Teams distributed globally
• Decisions, risks, business requirements, actions, dependencies, etc.
• Information (status, scope) constantly changing through Slack conversations, Teams / Outlook messages, Jira updates and Confluence pages

At this scale, I’ve reached the point where I no longer have good visibility over the whole project.

So: Last week I installed Claude and got the necessary admin access to Microsoft 365, Jira, Confluence and Slack. Initially I was excited about connecting everything, but I’ve quickly realised that giving an AI access to the information isn’t the same as giving it a good information architecture.

That’s where I’m stuck. How should the local project structure work? I’m seeing conflicting advice about the ideal architecture, particularly around Markdown. For example, should I maintain separate files such as:

/project PROJECT.md STATUS.md DECISIONS.md RISKS.md REQUIREMENTS.md DEPENDENCIES.md ACTIONS.md

Or should these be broken down further into folders and smaller files as the project grows?

I’m particularly interested in file size and boundaries. If DECISIONS.md, for example, eventually contains hundreds of decisions accumulated over several years, is that still the right approach? Or should each decision become its own Markdown file, perhaps with an index/summary file on top?

The same question applies to risks, requirements, actions, vendor information, workstreams, etc.

I’m less concerned about automation at this stage. Anthropic’s documentation around Skills gives me a reasonable starting point for that.

What I want to get right before automating anything is the underlying project architecture.

For people using Claude/Cowork on genuinely large, long-running projects:

• How do you structure your Markdown files and folders?
• How large do you allow individual .md files to become before splitting them?
• What information do you keep in Markdown versus leaving in Jira/Confluence/Slack as the source of truth?
• And how do you prevent the local project knowledge base from becoming another giant information dump that the AI has to rediscover every time?

Thank you, Clement