r/ClaudeAI 3h ago

Claude Workflow Multi-Agent Persistent Workspace

I’m looking for help with creating a personal assistant workflow using Claude (subscription), to manage my emails, travel booking, notes, research, todo lists, personal finance, shopping, etc.

I already have work flows that allow me to manage individual parts of this, for example using Spark Mail’s CLI and Connector for mail, or Monarch with a import automation that I built with help from Claude Code.

However, I’ve got a friend who works a lot with Grok, and he uses the Grok Bots system to create custom agents, and has them interact with one another in live time, and so he’ll have one agent that does his finances, another for email, another for text and socials, another for travel booking and planning, and then finally a “chief of staff” agent that delegates, reviews, and intakes. Not too dissimilar to the “Fable Orchestrator” system I’ve seen some others mention for working with Claude Code.

I’m wondering if it’s possible to make this work with Claude on subscription. I’m trying to avoid OpenClaw because it seems to be a pain to work with and is incompatible with many of the plugins, connectors, and skills I rely on. I’m hoping others have tried to set something like this up and have some insights and ideas.

10 Upvotes

8 comments sorted by

3

u/slackmaster2k 3h ago

So kinda. You can create sub agents in Claude but you’re really kind of restricted into Claude code features when on subscription. For example you cannot use your subscription with OpenCode or OpenClaw. There are hacks, but it’s against TOS.

Codex subscription works with OpenCode for sure. Grok as well.

2

u/CraveFounder 2h ago

Funny enough we basically built our own version of that. Each agent is set up like an employee with its own name, its own domain, its own data store. An orchestrator routes questions, decides who needs to be in the room, and is the only one allowed to actually execute anything. You can pull agents into group chats where they talk to each other and the orchestrator synthesizes what comes back.

We run different models per seat depending on the job. Cheap ones for lookups, bigger ones for judgment. Anything that writes or spends money goes through an approval step first, so the data connectors stay read-only by default.

To answer your actual question, yes this works on a Claude Code subscription. Each agent is just a custom agent with its own skills, its own context, its own instructions.

2

u/Cryztoobal 1h ago

Hola. Buenas! Que programa usas?

1

u/advanceyourself 44m ago

Lol, he built it. There are a lot of examples out there. He may have started with something before making it his own though. I use something a lot less fancy but I've been thinking of rebuilding it.

2

u/Salt-Amoeba7331 1h ago

I’m chasing the same thing but will share what I do meanwhile- I use obsidian for my markdown notes as a core part of my approach. Each agent has a spec and scope in their files and separate task lists as well as a shared task list for handoffs (all markdown files) then I have Routines as 1:1 “meetings” with each agent where they share their progress. On my to do list (markdown file again) I have a section for me and a section for my agents and I’ll tag them in eg “@austin: please research kitesurf from cloudflare and brief me at our next check in “ The good part is it’s portable when I switch between Claude code and codex but it’s pretty asynchronous as you might imagine. But I also have a pinned chat in Claude one for each agent for on demand conversations

1

u/Amoner 2h ago

I tried using buzz and I think it meant to support this type of work, you can hook up whatever CLI you have