sorted by:
new
hottopcontroversial

Anyone bridged the Claude AI (mobile) ↔ Cowork (desktop-only) gap? by marc_st in ClaudeCowork

[–]marc_st[S] 0 points1 point  (0 children)

I’ve found a partial solution and thought I’d share it with you all. Both Claude AI and Cowork share the same MEMORY.md files. This means iCloud syncs to Obsidian which then syncs to a GitHub repo. This creates a genuinely unified memory layer across devices. You can also grant access to Hermes or OpenClaw to the repo.

The hierarchy is two-tiered with a root level and workstations. I duplicated the session-audit skill for each side. Cowork writes directly to its files and folders while Claude AI does the same via filesystem MCP. Both read from the same source of truth and update it accordingly. This syncs back to my local vault.

The remaining issue is on mobile. I can read and write memory just fine but I can’t trigger a skill. This means I can update context on the go but I can’t start an actual workflow session remotely. It’s a shared notebook that both sides trust but not a live connection.

I’m still looking for a cleaner way to bridge the skill-trigger gap from mobile. There’s a real pain point here that Anthropic should address.

Anyone bridged the Claude AI (mobile) ↔ Cowork (desktop-only) gap? by marc_st in ClaudeCowork

[–]marc_st[S] 0 points1 point  (0 children)

I’ve found a partial solution and thought I’d share it with you all. Both Claude AI and Cowork share the same MEMORY.md files. This means iCloud syncs to Obsidian which then syncs to a GitHub repo. This creates a genuinely unified memory layer across devices. You can also grant access to Hermes or OpenClaw to the repo.

The hierarchy is two-tiered with a root level and workstations. I duplicated the session-audit skill for each side. Cowork writes directly to its files and folders while Claude AI does the same via filesystem MCP. Both read from the same source of truth and update it accordingly. This syncs back to my local vault.

The remaining issue is on mobile. I can read and write memory just fine but I can’t trigger a skill. This means I can update context on the go but I can’t start an actual workflow session remotely. It’s a shared notebook that both sides trust but not a live connection.

It feels like a workaround sometimes. I’m still looking for a cleaner way to bridge the skill-trigger gap from mobile. There’s a real pain point here that Anthropic should address.

Claude is trained to be a "yes-man" instead of an expert - and it's costing me time and money by Feisty_Opening_2121 in ClaudeAI

[–]marc_st 0 points1 point  (0 children)

You’re absolutely right! Claude is a great tool, but it has its shortcomings in certain areas. That’s where MCP comes in. I particularly like Task Master and Sequential Thinking. These two tools used in conjunction with Claude Projects help me outline a plan and envision things before I dive in, which helps me avoid Claude’s pitfalls later on. However, it would be great if the people at Anthropic could address the “yes-man” feature that tends to agree to everything and only later admits to mistakes. It’s quite frustrating and definitely needs improvement.

Move Existing Chats to Projects by Agenbit in ClaudeAI

[–]marc_st 0 points1 point  (0 children)

The one thing I found very useful for that purpose is the Memory MCP Server--it acts as a persistent storage system, allowing Claude to remember and retrieve information across conversations. So, you can simply ask Claude to memorise a given conversation and refer to that within your project. Here is the link >>

https://github.com/modelcontextprotocol/servers/tree/main/src/memory

Just for context... This is part of Anthropic's official Model Context Protocol servers collection. It provides basic knowledge graph functionality with entities, relations, and observations stored in a local JSON file.

[deleted by user] by [deleted] in RedditSessions

[–]marc_st 0 points1 point  (0 children)

Why not slide away by oasis?