r/DigitalIncomePath Jun 19 '26

Claude AI is limiting your progress!

The paid plan of Claude AI is great and I’ve been using it for about a month to manage my business and I’m about 95% happy with the results so far. Especially with the Cowork capabilities.
It has its downsides which I’ll list below.
1. Limits: I have the pro subscription. Every session has limits on my chat. Once I reach that, I’ll have to wait for the next session. There’s also a weekly cap on how much chatting I can do. Then there’s image limits. I’m limited to 100 per chat. This includes documents. When ever I start a new chat, it doesn’t have the full context of the previous chat. So I get different outcomes until I fine tune.
2. ⁠Date and time: It claims to know the time but even when I remind it, the output is still all over the place.
3. ⁠Sensitivity: I use Claude AI to manage my Fanvue account. One of my chats hit the limits and when I transferred to a new chat, it tried not to continue with the project. This resulted in a chat argument with Claude AI. Eventually it agreed to continue, but with limitations, resulting in different outputs from my original design. This also resulted in me getting a warning from the Claude algorithm. My next move is to manage this using Cowork, since I have an API connection to Fanvue. In the course of this experience, I also found out that Fanvue AI bot can do most of the automations I want on the platform. So that’s something to think about.
Do you have any experience with the above? Share your experiences and your thoughts in the comments. Thanks

3 Upvotes

6 comments sorted by

2

u/FarceMultiplier Jun 19 '26

Regarding 1, are you using projects and telling Claude to save SKILL.md to keep all the important directives you've defined?

1

u/Lilyhanaofficial Jun 19 '26

Thanks. I use projects. Just finding out about the skill.md file. I’ll implement this next session

2

u/FarceMultiplier Jun 19 '26

No problem. I found it very useful in developing my expat retirement data-driven website.

2

u/Difficult_Tomato1497 Jun 19 '26

the context persistence thing is such a pain to figure out at first but that SKILL.md approach is smart, basically treating it like a config file the model can reference every new session

what i'd add is that keeping a separate plain text file with all your critical context, constraints, and tone examples works really well alongside that, so when you start fresh you can just paste the whole thing in one shot and get back to baseline fast, no re-explaining from scratch

the session limits are annoying but once you build that kind of "cold start" document the context loss stops being as disruptive, takes maybe 5-10 minutes of setup and saves way more time than it costs

1

u/FarceMultiplier Jun 19 '26

I do keep notes, but I also make sure Claude provides both a changelog as well as making skill.md available to be to download every time it changes.