docs: research — relocate Automation Config from consumer CLAUDE.md to .agent-flow/config.toml#18
Closed
filip-ceos wants to merge 1 commit into
Closed
docs: research — relocate Automation Config from consumer CLAUDE.md to .agent-flow/config.toml#18filip-ceos wants to merge 1 commit into
filip-ceos wants to merge 1 commit into
Conversation
Findings from a 7-subagent research pass (official docs, ecosystem survey, community practices, internal drift analysis, format comparison) on where agent-flow's per-project Automation Config should live. Drafted decision: .agent-flow/config.toml (committed) + optional config.local.toml (gitignored, per-developer overrides), CLAUDE.md reduced to a pointer. Classified MAJOR; migration via deprecation window. No behavior change in this commit — research document only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Closing without merge. The research document ( |
filip-ceos
added a commit
that referenced
this pull request
Jul 6, 2026
…s migration Moves research-automation-config-location-2026-07-03.md here from the discuss/automation-config-location branch (PR #18, now closed) so the investigation that motivated the config relocation lands with the implementation instead of as a separate PR. Content unchanged — it is a point-in-time research record; the shipped decision is a hard cut (no deprecation window), which supersedes the doc's drafted-decision note. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Closing without merge. The research document ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Research document only — no behavior change, version-neutral (no plugin.json/CHANGELOG edits).
Investigates whether embedding the
## Automation Configsection (5 required + 18 optional table sections) directly in the consuming project's CLAUDE.md is best practice for Claude Code plugins, and where it should live instead. Based on 7 parallel research subagents across two rounds: official Claude Code docs, a survey of ~11 real plugins (including Anthropic's own), community best practices, neighboring ecosystems (Codex/Cursor/MCP), an internal drift analysis of this repo, and a format comparison (TOML/YAML/JSON/MD/TOON).Key findings
.taskmaster/config.json) or.claude/-namespaced files (Anthropic's hookify).userConfig/pluginConfigsis flat-scalar only — too weak for 18 structured sections.Retry Limitsandcustomization/*.toml [limits](file:line evidence in the doc).Drafted decision (for discussion)
.agent-flow/config.toml(committed, team-shared) + optional.agent-flow/config.local.toml(gitignored, per-developer overrides), CLAUDE.md reduced to a 1–2 line pointer./check-setupvalidates the config exists and is not gitignored;/onboardgains a migrate mode; deprecation window for the legacy inline format. Classified MAJOR per the Versioning Policy.Open questions are listed in §5 of the document (override reconciliation rule, local-merge semantics, schema validation, doc-count drift).
Test plan
HARNESS_JOBS=1): 233 scenarios — 232 pass, 0 fail, 1 skip🤖 Generated with Claude Code