Skip to content

Feature: Global agent definitions at ~/.multiclaude/agents/ #373

Description

@kiambogo

Right now the agent resolution order is:

  1. ~/.multiclaude/repos/<repo>/agents/ (local per-repo)
  2. <repo>/.multiclaude/agents/ (checked-in per-repo)

There's no global layer. If you maintain a personal set of customized agents (e.g. a pr-shepherd that notifies you instead of merging, a tuned worker prompt), you have to either re-apply them to every repo on init or maintain per-repo symlinks from a dotfiles manager.

Proposal

Add ~/.multiclaude/agents/ as a new global base layer in the resolution order:

~/.multiclaude/agents/                  ← global defaults (new)
~/.multiclaude/repos/<repo>/agents/     ← per-repo local overrides
<repo>/.multiclaude/agents/             ← checked-in team overrides

Same merge semantics as today: each layer appends to / overrides the layer below. A per-repo definition wins over the global one; a checked-in repo definition wins over the per-repo local one.

Why this matters

Makes dotfiles-based multiclaude configuration actually ergonomic. You symlink ~/.multiclaude/agents/ to your dotfiles once, and every new repo you init picks up your standard agents automatically — no post-init ceremony required.

Implementation

Small change to internal/agents/Reader — add a third globalAgentsDir field populated from ~/.multiclaude/agents/, read it first in ReadAllDefinitions, then layer local and repo on top.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions