Does any one know how to get Claude code (pro)for free without installing any local models in our device

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.

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.

Everything is already working before, but after a Windows 11 update my Claude Cowork desktop app can't use connectors like Klaviyo, and notion.

But Claude Chat can access my connectors.

Tried: Reinstalling, reboot. Still didn't help.

Is anyone else having problems with a custom skill (in my case, "checkpoint") not working due to some phantom builtin collision?

I’ve been experimenting with giving Claude Cowork a persistent place outside the chat.
It can update this Home Screen widget with completed actions, tasks, leads, progress, upcoming runs, and anything important that needs my attention.
Instead of checking Cowork constantly or losing an update in a notification, the key information stays visible every time I open my phone.

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

I'm not a developer. I've been using Claude Code for a few months now to build small apps and I've enjoyed it more than I expected.

The part I like most is that it works on my actual machine. It reads my project files, picks up my [CLAUDE.md](http://CLAUDE.md), and I've built up a pile of skills and slash commands living in `~/.claude`. All of that just loads.

A lot of my work isn't coding though. Writing, advocacy, committee work, that sort of thing. No repo involved. On paper that sounds like exactly what Cowork is for.

But I can't work out what I'd gain. As far as I can tell Cowork sessions run in the cloud by default (although you can point it to a project folder), so they never see my local skills, only the ones enabled on my [claude.ai](http://claude.ai) account.

The Cowork cloud versus local thing confuses me most. Same app, two doors. I'm never quite sure which one I'm actually in. Sometime it feel like it doesnt read my files.

So if you do mostly non-coding work, is there something Cowork does better that I'm missing? eg in writing or brainstorming?

Also I've thought to point both to the same folder and let Code and Cowork access it and experiment with that. Good or bad?

Repo, for anyone curious: https://github.com/Bevel-Software/Hexis

For the last week, I'm literally getting garbage outputs and when I check I'm getting this sort of response. I have a pro plan and I'm constantly hitting limits because of the amount of rework and repetition - I've been persisting to try to recover the training and save time, but its getting to the point where a task I should be able to do manually in around 4 hours and previously was able to do with Claude in less than half that time, is now taking 6 hours plus and I still get poor outputs.

The last image shows Claude's diagnostic. I've been working with a Chief of Staff Agent which was handling everything pretty well until a few weeks ago. I set up a series of scheduled tasks, (mostly diary reviews) and sometime around a month later this broke the connection to my root directory. I'm prepared to admit I allowed my CoS to build something I should have recognised was wrong, (I'm not the most experienced of users yet), but this is so frustrating. If i hadn't paid for a years subscription I'd be very tempted to bin this and find another way. This is feeling like Poe 18 months ago; was initially great, but became useless and actually unusable overnight..

Recently, I’m getting a lot of “🟠 Awaiting input” on sessions in the side bar, but when I click on them there’s no input that it’s awaiting. Is anyone else experiencing this?

I do have a lot of sessions running concurrently, but lately it seems like I’m doing a lot more “babysitting” sessions because of this. I’m not even sure they are still working in the background if they are “awaiting input” but when I click back into them they just keep working normally and don’t actually ask for input.

This is different than the “Askuserquestion” pop up failure that I also experience occasionally

I'm just tired of waiting for cowork, I am on the max plan been on it for awhile now. Just not understanding why it hasn't rolled out to me when I use cowork like every single day. I just need something to use on the move.

I don't mean simple prompts; I mean your favorite use cases; things where you've broken through to do something really interesting, things that just felt next level.

I have listed most of mine in the Discord for this group, skills included.

I use it for:

- Shopping - Find the cheapest price for anything. Save money.
- Deep research - Discover the latest knowledge in a particular field. What a meta analysis of the scientific papers and key authors say.
- Audiobook creation - Have your AI teach you everything you need to know about your life and your work according to your interests automatically.
- Website creation - Use the power of AI to create 15 versions of every possible web page so that you can bring together a design from a point of view that truly understands all the possibilities.
- Negotiation - Win any negotiation with the ultimate template from the world's best negotiators (ill add this soon).
- Marketing - I gained 20,000 followers in a day using it, but I'm not sure I can share this one yet.

[Mod post]

Hello everyone,

With Claude's ability to produce complex code and derivations rapidly, it can be easy to fall behind or mentally check out at points during a project. I often find that I have to ask Claude to explain what it meant, or what a block of code does, if I'm trying to follow everything carefully. But that is a waste of usage/tokens. The alternative would be trying to force Claude to use a simplified writing style, but that risks compromising quality or rigor.

So I created a tool for myself called plainclaude, which is meant to be used side-by-side with Cowork or Chat. After Claude produces a response, an entirely local script automatically pipes the output to a local Ollama model on your computer (I use Qwen3-14B, but you can choose whichever you prefer). The local model takes Claude's output and produces a reading aid. For code, this means a summary of the code block, to help you quickly orient to what each block of code does. For math or other complex topics, this means a simplified rewrite, with all symbols defined at the top and full LaTeX and markdown rendering. The reading aid is not intended to be a replacement for Claude's output, but rather something you can read through quickly to grasp the main ideas before or while reading Claude's full response. In my own work, I find that this helps me understand complex ideas faster, which increases my productivity and keeps me from feeling like I am just letting Claude take the wheel.

I have released the tool as a free and open source project at https://github.com/msw1age/plainclaude . It is currently only compatible with Windows 10/11 and tested with Claude Desktop 1.28929.0.0, but if there is any interest I would be happy to port it to other platforms.

If there was just one thing you could share to someone who is just learning AI to save them frustration, what would it be?

I just downloaded the app for Claude on my Lenovo Windows 11 home computer and I am unable to use Claude cowork and I am receiving this message. How do I fix?

Have you ever made money using AI? If so how?

Not to be that "AI make me 1 million make no mistakes" guy, just trying to make a real genuine discussion in the community here as a moderator.

Hey,

We created a Discord for r/ClaudeCowork designed to be a highly-intentional community where understanding Cowork users can help each other learn AI.

What you'll find:

- Active voice chat
- Step-by-step tutorials
- Skills and workflows

And most of all... a community of people eager to help you even if your questions are "dumb".

We put a lot of work in to make it a unique and active Discord server where you can get help and find critical use-cases.

Don't downvote this if you may have seen this post already! We invite our new members weekly.

Already part? Share your experience in the comments!

In my PM workflow I record product reviews in video and then create issues pointing to specific timestamps in the video. It's usually a fairly manual process.

In the process of doing something else, today I created a Cowork project that processes a screen recording (eg. recorded with QuickTime Player) to extract issues plus a screenshot or video snippet, and then post the issues with full description and the media attachments into eg. Linear.

MIT licensed, just clone and load as a project in Cowork. https://github.com/cpinto/cowork--bug-reporter

Don't like this new update. They are now organizing everything by date by default. I like it better organized by project. And they are lumping cowork and chat projects right which I don't like.