Create Workflow (Grade A)Security-tested development skill for Claude AI. Grade A. Draft or revise a profile's `/workflow` slash command — a dormant orchestration script that sequences the profile's tools into a predictable m

What it doesn't do?

macOS only at launch. Windows is planned and Linux likely follows. The Electron shell is already cross-platform, but the terminal launch and Keychain sync need ports. Profiles live on your machine, no cloud sync. Use exportProfile / importProfile to move them. No GitHub token required. ClaudeWorks tries the gh CLI first, then GITHUBTOKEN, then falls back to anonymous fetches (60 req/h). See Architecture for the fallback chain. Teams need Anthropic's experimental flag (CLAUDECODEEXPERIMENTALAGENT_TEAMS=1). The feature works today but expect behaviour to shift as the upstream matures. We don't generate or manage Claude API keys. Run claude login first. The app copies credentials from your existing login.

Asked by Dalia Haddad · Feb 20, 2026

What it does?

Each profile runs in its own CLAUDECONFIGDIR, which is Claude Code's built-in way to redirect its config root. MCP servers, skills, agents, and slash commands from profile A can't appear in profile B's session. Real per-process isolation, not config swapping. A curated plugin marketplace ships inside the app. Browse 114 upstream marketplaces and 647 featured plugins without leaving ClaudeWorks. One search bar queries 7,009 flat entries (every marketplace, plugin, skill, command, agent, and MCP server) at once. Every profile ships arbitrary shell aliases. Each one cd's to a directory and optionally auto-runs /workflow or a saved prompt. One profile can claim the bare claude command, so plain claude in any terminal lands in your default profile without the bloat of the others. More Per-profile /workflow commands (and named variants like /workflow-debug, /workflow-deploy) become real Claude Code commands in that profile's session. Variants can be scoped to specific launch directories. Multi-agent Teams (experimental, behind CLAUDECODEEXPERIMENTALAGENTTEAMS=1): compose a team from existing profiles with drag-and-drop, assign roles, pick a lead, and launch. The lead opens with a generated /start-team that spawns each teammate. Per-directory MCP management: disable individual servers inside sensitive repos while keeping them available elsewhere. Status bar builder: 17 widgets, drag to reorder, named save/load, per-profile override. Profile export / import: a self-contained JSON.

Asked by Gustav Lindberg · Feb 11, 2026

Why this exists?

I kept managing two Claude Code setups by hand, the work one with its MCP servers and skill set, the personal one with a different CLAUDE.md and different tools. Swapping meant editing ~/.claude.json and mcp.json by hand, then undoing it next session. Claude Code has no native multi-profile support, so I built this instead. Plugin caches are shared across profiles via symlinks, so you install a plugin once and updates propagate everywhere.

Asked by Ines Fernandes · Nov 16, 2025