Profile Editor

The core of ClaudeWorks. Every profile is configured across eight tabs.

Top bar

Everything global to the profile lives at the top of the editor:

• The name is an inline text input. Renaming the profile also renames its config directory.
• The directory dropdown picks which imported project this launch will cd into. Defaults to "None".
• Launch opens a terminal with the profile's CLAUDE_CONFIG_DIR set. A chevron menu next to it toggles --verbose or --dangerously-skip-permissions for the current launch only.
• Save writes changes to profiles.json and rebuilds the profile's config directory.
• Export writes a self-contained JSON of the profile: plugins, exclusions, aliases, workflows, MCP overrides, env vars, and settings. See Import & Export.
• Profile Overview opens a modal with enabled-item counts (Plugins, Skills, Agents, Commands, MCP Servers). Each count links to its tab.
• Copy to Clipboard copies the current profile JSON.

Info card

A collapsible card below the top bar holds:

• A description field for free-form notes.
• Tags: comma-separated labels used by the sidebar tag filter.
• Projects: imported project directories this profile is scoped to. These feed the sidebar's project filter.

Tabs at a glance

Plugins tab

The Plugins tab is the primary on/off switch for everything else. Skills, agents, commands, and plugin-provided MCP servers only appear if their plugin is enabled here.

• The star pins a plugin to the top of the list.
• Plugin group headers are collapsible, grouped by source (marketplace, local, skillfish, git).
• The per-plugin toggle is the big switch. Off means every item inside is excluded from this profile.
• Within an enabled plugin, item checkboxes let you disable specific skills, agents, or commands without disabling the whole plugin. ClaudeWorks writes a small overlay for the excluded items so the rest of the plugin stays symlinked and cache-shared.

Skills, Agents & Commands tabs

Three tabs with the same layout. Each one shows a flat list of every item of that type across currently enabled plugins.

• The search bar matches item name and parent plugin name.
• The filter has three options: All, Enabled, and Disabled.
• The sort groups by source plugin or flattens to A–Z by name.
• Group headers (when sorting by source) are collapsible and include an All / None toggle per group.
• Each row has a checkbox, the item name (with a / prefix for commands), and its source plugin. An internal badge marks items that aren't user-invocable.

MCP Servers tab

Every MCP server available to your profile surfaces here, grouped by where it comes from. You can disable servers per-profile or per-directory.

A header indicator shows which launch directory is currently selected. This affects the project-level section.

From Plugins

MCP servers declared by any currently enabled plugin. Disabling a row here disables the source plugin item itself, since plugin MCPs travel with their plugin.

User

MCP servers declared in ~/.claude.json under mcpServers. These are global to your user and appear in every profile by default. Toggle off per-profile.

Project

MCP servers declared under ~/.claude.json → projects[<directory>].mcpServers, plus any .mcp.json in the project directory. They're scoped to whichever project directory you're launching into, and disabling a row scopes the disable to that directory.

Project Items tab

When your profile has a launch directory selected, this tab surfaces every skill, agent, and command defined inside that project's .claude/ folder. You can edit them inline without leaving the app.

• The empty state ("Select a project directory") shows when no directory is selected.
• A helper card appears when a project has fewer than three items, with a quick button to open its .claude/ folder in Finder.
• The grouped browser splits items into Skills, Agents, and Commands sections. Click any row to open the inline editor.
• The inline editor has a textarea plus Open in Editor, Save (when dirty), Delete, and Close actions.

Instructions tab

Two editors side by side: one always-on, one on-demand. Plus named workflow variants if you want to ship more than one runbook from the same profile.

Always-on: CLAUDE.md

A per-profile CLAUDE.md body. Anything you write here is appended to the global CLAUDE.md that Claude reads every turn. Use it for profile-specific instructions that should always be in context.

The toolbar has three actions: Insert Prompt, Open in Editor, and Save as Prompt. Save as Prompt stores the current body as a reusable prompt.

On-demand: /workflow

A dormant body stored in <config-dir>/commands/workflow.md. It only loads into context when you type /workflow in the session. Good for runbooks you want at hand without paying the token cost every turn.

Workflow variants

Named variants become /workflow-<name> commands. Each variant can optionally be scoped to a specific launch directory, so /workflow-deploy might exist only when you launch into ~/code/api.

Settings tab

Per-profile session configuration. Anything left at its default inherits from the global value in Configure Claude → Global.

Session Behavior

• Model: Default, Opus, Sonnet, or Haiku.
• Context (shown only when Opus or Sonnet is picked): 200k or 1M.
• Effort Level: Default, Low, Medium, High, X-High, or Max.
• Voice: Default, Enabled, or Disabled.

Status Bar

Toggle Override global status bar to use a profile-specific status bar config. Build the config under Configure Claude → Status Bar.

Authentication

Toggle Use default authentication to share credentials with the default Claude Code login. Turn it off to give this profile its own separate Keychain entry.

Environment Variables

Three stacked lists:

• Inherited from global: read-only, with an Override button per row.
• Overridden in this profile: editable, with a Remove button.
• Add new: key and value inputs, with autocomplete for known Claude Code env vars.

Hooks

If global hooks are defined in ~/.claude/settings.json, they appear here with a per-hook toggle to disable them for this profile. Each row shows event: command.

Launch Configuration

The most configured section in the app.

• Set as Default Profile: makes plain claude launch this profile.
• Disable claude override (default profile only): prevents the claude alias from being installed, even though this is the default profile.
• CLI Aliases: shell aliases that launch this profile. Each alias has a name, an optional directory, and a launch action: none, /workflow, or a custom prompt. Conflict warnings surface if another profile declares the same alias name. See Aliases & Launch for the full walkthrough.
• Launch Prompt: a prompt passed via claude -p "..." when launching from the editor's Launch button. Doesn't affect alias launches, which have their own per-alias prompts.
• Launch Flags: toggles for --dangerously-skip-permissions and --verbose, plus a free-form field for custom flags.

Profile Config

Open Config Directory in Finder is a shortcut to ~/.claudeworks/profiles/<name>/.

Unsaved changes

A dirty indicator appears next to the profile name when you have unsaved changes. Switching profiles or tabs while dirty shows a confirm dialog with three options: Discard & Switch, Save & Switch, and Cancel.