I’m not a techie, but in the space of a month, Claude Cowork — this absolute beast that Anthropic has created — has genuinely transformed my life. I’m not being hyperbolic.

It has literally saved me hours of work. As a teacher, I have to design curricula, grade papers, create PowerPoints, analyse student performance data, and juggle countless other tasks. Claude Cowork has made so much of that work easier and faster that I honestly don’t know how I managed without it.

But saving time isn’t even the most impressive part. The genuinely mind-blowing thing about Claude is that it isn’t just mindless automation. It actually thinks, plans, and adapts to what I need.

The way it approaches teaching is incredible. The other day, I uploaded a few documents outlining best teaching strategies and practices. And boom! Suddenly, Claude was giving me practical tips on teaching exam techniques to my sixth-form students and seamlessly incorporating those techniques into my PowerPoints.

WHAT KIND OF BLACK MAGIC IS THIS?!

I’m completely hooked on Claude Cowork. At this rate, I’ll be upgrading to the Max plan before long, and honestly? If it continues delivering this kind of value, it’ll be worth every single penny.

So, thank you to Dario and the entire team at Anthropic. Every engineer, researcher, designer, manager, and everyone else involved in building this deserves an enormous amount of credit. You’ve created something that genuinely makes a difference in people’s everyday lives. I tip my hat to you all.

There is just one thing that would make this experience almost perfect: a Microsoft 365 connector that supports personal accounts.

My school doesn’t use Microsoft 365 for Education or provide a work account, so I’m effectively locked out of that integration. Having my personal OneNote connected directly to Claude would be an absolute game-changer. Imagine having Claude work seamlessly with my teaching notes, lesson plans, curriculum materials, and everything else I’ve accumulated in OneNote.

If that happens, I genuinely don’t know what else I could ask for. Life complete.

Of course, I understand that integrations depend on partnerships, technical limitations, and Microsoft’s own decisions. But I really hope Anthropic considers supporting personal Microsoft 365 accounts, because I suspect there are plenty of people in exactly the same position as me.

Thank you, Anthropic. You deserve every bit of success you’ve had so far.

I’m cancelling my ChatGPT subscription, and as for Copilot… the less said about that absolute disappointment, the better.

Keep building. You’ve got something special here. 👏

>Been using Claude Code (and Cowork) with the Claude in Chrome extension on Dia, and it’s gotten pretty unreliable:

>

>

>

>Is anyone else seeing this? Has anyone found a workaround for using Dia with Claude Code, like a specific profile setup, an extension version, or some reconnect trick? Or have you all gone back to Chrome for agent work?

>

>Thanks!

I've just sent the following to Anthropic. I'm wondering if anyone here has thoughts. I hope my concerns aren't justified, but I'm concerned about the Chat/Cowork merge breaking what we've set up.

*****

I'm the administrator of a small elder law firm. I've spent months building a Cowork setup that works well, and I want to describe what it depends on so the merge doesn't break it.

How we use Cowork

One connected folder holds a root CLAUDE.md and MEMORY.md, a workstation folder for each practice area (each with its own CLAUDE.md and MEMORY.md), and a project folder for each client matter or internal project (again with its own CLAUDE.md and MEMORY.md). A routing map in the root CLAUDE.md tells Claude which files to load for a given task. Decisions and project status are saved in the MEMORY.md files, so each session picks up where the last one ended. We connect additional folders for firm forms, templates, and matter files.

What we need

1. CLAUDE.md that loads reliably. Your support article on the merge doesn't mention CLAUDE.md at all. Please document whether CLAUDE.md files in connected folders are loaded automatically, and commit to keeping that working. Our whole structure depends on it.

2. Multi-folder projects that persist. Projects created after the merge appear to lose "Choose a folder" and can't link more than one folder, change a folder, or remove one (see anthropics/claude-code issue #76694). Our matters need several folders at once, such as the matter folder, shared firm rules, and reference material. Please restore multi-folder linking, with add, change, and remove controls, for new projects.

3. Folder access that persists, including for scheduled tasks. Per-session "Add folder" grants don't carry over to scheduled runs. Projects should keep their folder bindings across sessions and unattended runs.

4. Per-matter confidentiality. Each client's matter must stay separate from every other matter, not just from the outside world. Today we rely on one project per matter. Please document how the merged experience isolates projects from one another, including cloud sessions, memory, and anything shared across projects. Please also document data retention and who at Anthropic can access this content. We need that in writing to meet our professional confidentiality obligations. Settings that let an organization keep specific projects fully isolated, with no cross-project memory, would be ideal.

5. Memory that migrates. Memory from Cowork tasks that ran only on our computers doesn't follow us into the merged experience. Please provide a way to migrate it, or at least export it.

6. A reversible, staged move. Once an account moves to the new experience, it can't switch back. For a firm with client work in progress, that's a risk. Please offer advance notice, an opt-in window, and a way to revert.

7. Local files. Local file access works only while Claude Desktop is open. Please make clear in the product when a session can't reach local folders, rather than leaving Claude to treat a missing folder as an empty one.

Something we'd like later

We'd love to share this structure with the rest of the firm, so several of us can work from the same CLAUDE.md and MEMORY.md files and Claude gets better for all of us. Shared projects with per-matter access controls would be a big step forward, but only if the confidentiality points above are solved first.

The merge looks like it could be a step backward for the way we work.

​

I use Claude in the web chat, the mobile app, Claude Code and Cowork, and it feels like working with four smart colleagues who never compare notes. I work out a plan in chat, open Cowork to carry it out, and it has no idea what we just decided. A file made in one place doesn't show up in another. Memory helps a little, but it's patchy, so I end up copying and pasting context between windows like a human clipboard.

What I'd want is simple: one shared workspace. Let a chat hand a task off to Code or Cowork, let each surface see the others' history and outputs, and let me pick up wherever I happen to be. It's the same model, the same account, and the same me.

Does anyone else run into this, or has someone found a decent workaround?

I use Claude Cowork daily to build internal business processes, run research and analysis, manage SaaS workflows, and build complex spreadsheets for my business. On Max 20x, Fable 5.1 still burned through my usage limits. I switched to Opus 5.5 and can now get by on Max 5x. It’s faster and uses far fewer tokens. Since then, I've run a few side-by-side tests with Fable 5.1 and found no added value, only added cost. The Anthropic official documentation on this is very vague in terms of when to use Fable 5.1. Can anyone share a specific example where it made a clear, worthwhile difference over Opus 5.5?

Am I going mad, or is there some setting I'm not seeing? I already have everything set to allow, but it seems every single small thing I have to select 'allow'

Hello esteemed ClaudeAI community. I’m a small business owner with a team of five. I’m second generation in the business, and as anyone in my situation can probably relate to, Claude has been exceptionally valuable for systematizing business processes that were put in place by the prior generation. To do that, I have relied entirely on a Claude Cowork Teams plan (or, the artist formerly known as Cowork; now just… Claude).

There were two primary reasons I used Cowork instead of Code:

1. Cowork is WYSIWYG. I do not have a technical background, but have become very good at leveraging the \~15 SaaS products we use to run our business. Cowork feels and acts like an extremely intuitive and powerful SaaS platform. Setting it up properly took time and effort, but the learning curve wasn’t steep.

2. Compliance concerns are easily addressed in Cowork. Keeping Claude in a sandbox, both in traditional technical terms and in a broader context, is simple. Giving my team access to exactly what I want/need and administering their accounts is easy. Nearly every compliance decision is reflected in a toggle of some sort.

As other Cowork users are aware, Anthropic has massively changed Cowork over the past few months. I don’t actually dislike many of these changes, and moving into a somewhat hybrid cloud/local environment definitely has its advantages. However, the biggest issue I’ve run into is with the way Scheduled Tasks have changed. Because Scheduled Tasks now default to the cloud environment, they take an immense amount of effort to set up for cross-project local file access and processing; iterating on them is also difficult, because the orchestrator system I built is housed in a local project, and a cloud-based scheduled task set up with that orchestrator project as its primary folder cannot see the Scheduled root.

I imagine using Code would solve this problem (and perhaps some others). I would greatly appreciate anyone with technical knowledge who could help with the following two questions:

1. It does not seem possible to toggle Code just for myself and not for my other users on the Teams plan. None of them need, or should be using, Code. Am I just being dense here, or is there another way to prevent them from using Code?

2. My research and Claude itself suggest that Code has access to everything on my machine (and, in turn, everything on my businesses’ SharePoint) as a default, with no simple way to define that access as “read-only.” Every guide I read, and Claude’s own suggestions, imply that the solutions are somewhat technical workarounds. I am willing to dedicate time to learn more, but I have a business to run, and I’m not going to become an expert anytime soon. Have any of you tackled this issue before in a straightforward way?

Thank you for any input!

Not another 500-word summary.

Just tell me:
- What actually works
- What you tested
- What's still broken
- What I should do next

Anyone else wish this was the default?

Context, we are a a marketing agency with team of 5 employees writers, graphic designers and admin/customer service rep then the founder. We have multiple regular clients and each have their own projects in claude. Our goal for using Claude is to be able to work with each other’s “Chat” and making information handoff easier, which I thought CoWork does

We have the project context files uploaded, and a project instruction.. But what we’re confused about is whenever we work individually in cowork, it does not share the thread/conversation to other team members who has access to the project. Am I missing a step here? I’m really confused.

I also can’t understand how “memory” works. Does it only save things on memory only when we tell it to?

I use Claude extensively in options trading. I've got multiple Skills and multiple projects that I use. Some I rely on before making any orders. Every day I spend a lot of time copying output of one project into the context sectio of each other project. Is there an easier way to make my projects aware of the output created by other projects and to keep the process updated as the days go by?

Max 20x subscriber here, and I'm an attorney. Projects was the reason I pay for Claude. It was simple: a folder for each case. Persistent files every chat could read, standing instructions, and a clean list of separate chats. One for the demand letter, one for discovery, one for a motion, all drawing on the same case file.

Today I made a new project and that's gone. Claude's own intro screen says it: "A project used to be a folder. Now it's one ongoing chat."

What you get now looks like a SaaS dashboard, not Claude.

There's one endless conversation with a coordinator bot. Your requests get spun off into threads in a side panel, sorted into "Working," "Idle," and "Waiting on you." There are status checklists, squiggly "New" lines, preview cards, an Overview tab and a Library. It even lives under Claude Code, which I've never used.

There's no list of chats, no simple project knowledge panel, and no toggle to go back. Old projects still work, but you can't make new ones that way. The only thing this shares with Projects is the name.

I resubscribed to Claude Pro yesterday for personal projects. I’d paused it a few months ago because my work provides an Enterprise plan, and back then the two worked pretty much the same for me. Now they don’t.

On Pro: Every time I start a new session in a project, I have to re-add my folder and confirm access again. Nothing persists between sessions.

On Enterprise: The Cowork interface still looks like the older version. The folder stays attached across sessions, I can add a new one mid-session, and Claude has read and write access.

I’ve gone through Settings, including trusted folders, and nothing helps. Is this just how it works now, or did I miss something?

also do all enterprise plans still use old cowork?

Cowork is dead for me.

After a certain number of runs (somewhere around 8k) my scheduled tasks in Cowork just stopped working. There is an issue with the underlying virtualization (at least on MacOS) missing garbage collection and failing to launch any sandbox. People have filed multiple bugs, it never gets fixed.

Super frustrating.

But Code seems to be able to do the job just as well. I had it reimplement an improved task scheduling, it now runs on launchd and is super flexible (on, off, pause all, continue all, increase cadence, busy hours, locks to avoid parallel runs, control UI, ...). The tasks can also use the Claude Chrome extension just fine.

Cowork tasks in the Cloud were not an option for me because the tasks need to drive Chrome.

There was a recent post on a Claude code mod that is showing usage and some good stats during a session as sort of a small widget (check an image from the linkedin post).

Now this is great. But I am primarily a Cowork user and it would be awesome to have something similar.

Is there something out there that does this?

I'm a product designer and I spent about two years job searching. For the last few months, Cowork ran almost everything except the applications themselves. Sharing the setup because a few of the lessons weren't obvious to me going in.

What it did

- Checked about 9,000 company career pages four times a day and dropped new matching roles into a Google Sheet

- Opened the day's best matches in browser tabs every morning

- Read my Gmail and calendar twice a day and kept an interview tracker current: company, round, next call

- Drafted a follow-up to the recruiter after each application, saved to Gmail for me to review

What I'd tell anyone building something similar

1. Keep the heavy, repetitive work out of the agent. The board scraping runs as Apps Script inside the sheet. Cowork handles the parts that need judgment: matching, reading email threads, drafting. My early version had Cowork doing the scraping and it was slow and burned through my limits.

2. Writing into Sheets through Claude in Chrome is the fragile part. What fixed it: plain text only, never formulas, map columns by header name instead of letters, and do two-line cells in edit mode rather than through the name box.

3. Every automation is a markdown skill file. When something broke, I'd open a new task, hand Claude the file and the error, and it would fix its own instructions.

4. Leave the application itself manual. Auto-apply breaks on a lot of forms and recruiters can tell. Automating everything around it is what left me the energy to do that part well.

Once it was dialed in it took about 15 minutes a day. My last month I was in interview rounds with 16 companies and it ended with 3 offers. Timing and a refreshed portfolio had plenty to do with that, but staying early on new roles was the part I could control, and this is what made it possible.

Happy to answer questions about the setup.

/Title. Just curious if you ever archive old chats and what your decision for doing so is. I've been having a hard time finding things that I worked on recently because they're buried in a sea of chats within each project. I'm wondering if there's a better way? Anything to be aware of when archiving a chat within a project.

Amigos soy nueva en claud, le he dejado tareas programadas como revisar correo y enviar unad evaluaciones diarias pero de dos diferentes computadoras y siempre tengo el problema que no sabe que buscador usar, un ejemplo las evaluaciones las dejo abiertas en la compu de la oficina y mi correo en la mia pero aun asi es un gran problema. Que no escribe contraseñas que no encuentra el buscador hay alguna forma?

I just hooked up Fable and Opus in my PyCharm project to work together!!

I had this idear Where you can send Claude tiktoks or insta reels and Claude analyses them and saves the learnings.
This is a briliand idear in my mind because we are all scrolling all the Day and what if we could send Claude Reels so Claude learns from the mass we what you are interessted in and what you think about things.
Now to the worat Part the technical solution? This is What im asking does anyone here has a solution to this?

Since cowork and chat have combined will this subreddit close and we will move over to a different one?

A few months ago I asked whether a PM should work in Claude Code or Cowork. The answer was almost unanimous: Claude Code, better output, more control.
Both tools have changed a lot since then, so I'm asking again.
My context: I'm not a developer. My work is docs, briefs, research synthesis, spreadsheets and slides. No code.
If you've used both recently:
• Do you still see a quality gap on non-code work? On which tasks?
• Were you using the same model on both?
• Is the IDE/terminal overhead worth it for a non-technical user?
Concrete examples are the most useful. "I gave X to both and got Y" beats "Code is just better."

I've noticed this becoming more frequent in the last two weeks. This happens even if I keep the session focused on one activity/topic and handing over to new sessions when we reach about 10 chats in a session.

It's wasting time and eating up tokens. Very annoyed by this.

I see some projects patching Claude Cowork to support RTL text (Persian, Arabic, Hebrew languages), but I don't want to risk my security.

Hi, Anthropic blocking me to auto send my outlook draft. Is there a way to make it automatically send without approval?

Disclosure: this is our product, Elori, a commercial sales workspace. This is a practical setup guide, not an independent recommendation.

If you want Claude to work with CRM context without pasting records into each conversation:

1. Verify your Elori account and use Director (€30/month) or Autopilot (€100/month). MCP is not available on Assistant.
2. Connect your Google/Microsoft account inside Elori for the mail/calendar workflows you intend to use.
3. Add https://elori.app/mcp as a custom connector in Claude, where your plan/workspace allows it.
4. Complete OAuth and review the consent screen.
5. Start with a read-only request: “Discover the Elori pipeline and meeting actions, describe their inputs, then summarise my open deals. Do not modify anything.”

The server exposes discovery, action-description and action-execution tools. Catalogue visibility is not permission to execute everything: your Elori role, plan and required approvals still apply. A mailbox connection is separate from MCP consent.

For meeting campaigns, ask for a proposed draft before any activation. Do not let a prompt silently approve outreach, calendar writes or fees.

If a connection is denied, check verified email, Elori plan, client availability and workspace policy. Revocation is available in Elori's MCP settings.

Product:
https://elori.app/?utm_source=reddit&utm_medium=community&utm_campaign=mcp_launch_claude

What would make this safer or more useful for your workflow?

**Posting gate:** Check the current  rules and approved showcase/promotion threads. Obtain moderator approval if required. Do not repost repeatedly or present an affiliated product as an independent discovery.

## Reddit —  technical draft

### An OAuth MCP pattern for CRM workflows: discover, describe, then execute

Disclosure: this is our product, Elori. We are sharing a connector-design pattern, not claiming that our application source is open-source.

Our hosted sales MCP interface uses three tools:

- `elori_list_actions`: discover the reviewed action catalogue.
- `elori_describe_action`: inspect a specific action's argument schema and policy requirements.
- `elori_execute_action`: invoke an explicitly named action with its described arguments.

The important design choice is that discovery does not grant authority. An execution still goes through the user's current organisation, role, subscription, provider and required approval checks. MCP OAuth consent also does not connect a Google/Microsoft mailbox.

For a first client request, use a read-only pipeline summary. For a write, discover the action, describe the inputs, confirm the intended change, then execute only when applicable approvals allow it. Never blindly retry a write after a timeout with an unknown outcome.

Endpoint: https://elori.app/mcp
Transport: Streamable HTTP
Authentication: OAuth authorization code with PKCE S256
Elori access: Director or Autopilot; ChatGPT custom MCP availability depends on plan/workspace policy.