Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
日本語の概要は準備中です。原文の説明を表示しています。
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A method for deciding when and how to delegate tasks to external LLM services. Core principle: delegate execution, retain high-level reasoning.
Delegation is on. Declining it is the step that takes a decision.
Any conjure operation, mission phase, or workflow that reaches eligible
work delegates it without being asked.
Eligible means the work is execution rather than reasoning, which the
philosophy below defines and modules/task-assessment.md classifies.
An operator who wants delegation off says so once, in one of the two
places under Declining Delegation.
This inverts the earlier framing, which listed the occasions on which to delegate and so made delegation something a caller had to remember. The occasions were correct and are now the exception list instead.
Delegation stops at the boundary the philosophy draws. Keep the work local when any of these hold:
The first is the standing exception and covers most of what Claude does.
The rest are the red flags modules/task-assessment.md already lists.
Two switches, environment over file.
| Scope | How | Effect |
|---|---|---|
| One run | CONJURE_DELEGATION=off | No provider is probed or spawned |
| One machine | "enabled": false in ~/.claude/hooks/delegation/config.json | Same, until the key changes |
CONJURE_DELEGATION accepts off, 0, false, no and their
opposites, in any case.
Setting it to an on spelling re-enables delegation that the config file
turned off, so the narrower scope wins.
A disabled delegator returns a result whose fallback_reason is
delegation_disabled and spawns nothing, so opting out costs nothing.
smart_delegate works down the registry order and returns the first
real answer.
A provider that is missing, unauthenticated, failing, or answering with
an empty stdout is recorded and the chain moves on.
When it reaches the end, it returns a result with
fallback_reason set to providers_exhausted and an attempts trail
naming what each provider did.
That result is the instruction to do the work locally. Read it, say
which providers were tried and why none answered, and then do the task
yourself.
Do not treat it as an error to report and stop on: a machine with no CLI
installed is the ordinary case for this default, not a fault.
When the operator wants providers answering rather than falling back,
modules/provider-onboarding.md carries the per-provider steps and the
failure shapes that do not look like authentication problems.
Start with make -C plugins/conjure delegate-doctor.
Delegate execution, retain reasoning. Claude handles architecture, strategy, design, and review. External LLMs perform data processing, pattern extraction, bulk operations, and summarization.
| Complexity | Context | Recommendation |
|---|---|---|
| High | Any | Keep local |
| Low | Large | Delegate |
| Low | Small | Either |
High Complexity: Architecture, design decisions, trade-offs, creative problem solving.
Low Complexity: Pattern counting, bulk extraction, boilerplate generation, summarization.
delegation-core:task-assessed)Classify the task:
modules/task-assessment.md for classification criteria.Exit Criteria: Task classified with complexity level, context size, and delegation recommendation.
delegation-core:delegation-suitability)Verify prerequisites:
modules/handoff-patterns.md for checklist.modules/cost-estimation.md.Exit Criteria: Service authenticated, quotas verified, cost justified.
delegation-core:handoff-planned)Create a delegation plan:
modules/handoff-patterns.md for request template.Exit Criteria: Delegation plan documented.
delegation-core:results-integrated)Execute and validate results:
Exit Criteria: Results validated and integrated, usage logged.
For MCP servers that don't support Dynamic Client Registration (e.g., Slack), pre-configured OAuth client credentials can be provided:
claude mcp add <server-name> --client-id <id> --client-secret <secret>
This enables delegation workflows through MCP servers that require pre-configured OAuth, expanding the range of external services available for task delegation.
As an alternative to manual OAuth setup, users can configure MCP servers directly in claude.ai at claude.ai/settings/connectors. These connectors are automatically available in Claude Code when logged in with a claude.ai account: no claude mcp add or credential management required. This provides a browser-based auth flow that may be simpler for services with complex OAuth requirements.
When delegating tasks that modify files to subagents, use isolation: worktree in the agent frontmatter to run each agent in a temporary git worktree. This prevents file conflicts when multiple delegated agents operate in parallel on overlapping paths. The worktree is auto-cleaned if no changes are made; preserved with commits if the agent produces changes.
# Agent frontmatter for isolated delegation
isolation: worktree
Conjure uses leyline infrastructure:
| Leyline Skill | Used For |
|---|---|
quota-management | Track service quotas and thresholds. |
usage-logging | Session-aware audit trails. |
service-registry | Unified service configuration. |
error-patterns | Consistent error handling. |
authentication-patterns | Auth verification. |
See modules/cost-estimation.md for leyline integration examples.
For detailed service workflows:
Skill(conjure:gemini-delegation): Gemini CLI specifics.Skill(conjure:qwen-delegation): Qwen MCP specifics.Skill(conjure:minimax-delegation): MiniMax CLI specifics.Skill(conjure:glm-delegation): GLM via the Z.ai endpoint swap.Skill(conjure:muse-delegation): Meta Muse Code CLI specifics.Skill(conjure:codex-delegation): OpenAI Codex CLI specifics.Skill(conjure:opencode-delegation): OpenCode CLI specifics.When delegating to multiple agents, choose the appropriate execution mode:
| Mode | When to Use | How It Works |
|---|---|---|
| single-session | Sequential tasks, same-file edits | Claude works through tasks in order |
| subagents | Parallel independent tasks | Agents work independently, report back |
| agent-team | Parallel coordinated tasks | Agents can communicate with each other |
See references/execution-modes.md for the selection decision
matrix, mode compatibility notes, and anti-patterns to avoid.
providers_exhausted result was reported with its attempts
trail and then completed locally, not abandoned.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
日本語の概要は準備中です。原文の説明を表示しています。
Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.
日本語の概要は準備中です。原文の説明を表示しています。
Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.
日本語の概要は準備中です。原文の説明を表示しています。
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
日本語の概要は準備中です。原文の説明を表示しています。