Give reusable agent setup a versioned home.
The problem
Agent setup spreads across instructions and configuration files. Manual copies drift, and copying a whole runtime directory includes state that should stay local.
An explanatory exhibit
What belongs in the configuration repository?
Conceptual repository boundary with invented settings. This is not a capture of live configuration.
- 01
Versioned setup
Instructions · hooks · selected settings
- 02
Installation
Apply managed configuration
- 03
Local runtime
Credentials and session state stay here
Inspect the consequence
A reusable review skill
Versioned setup
A workflow intended for repeated use benefits from one maintained source.
A logged-in session
Machine-local state
Authentication and runtime history belong to their local runtime, outside portable setup.
What this makes possible
I collected Claude Code guidance, selected settings, hooks and skills in a configuration repository that can travel between projects and machines.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
Portable configuration source inspected. Private repository links and machine-specific state are excluded.
Research cut: 14 October 2026. Source areas below are from metaclaude. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
metaclaude holds portable instructions, base settings, hooks and reusable skills. Version control gives those working practices a history and a common place to maintain them.
The repository supplies selected setup. Credentials and runtime data keep their own local locations, so the portable artifact can be updated without copying a logged-in session.
A path through the feature
- Manage the portable setup
Keep reusable guidance and workflows in the configuration repository.
- Keep runtime state local
Apply the selected setup through its installation workflow, then check the result on each machine.
Source areas
CLAUDE.mdsettings.base.jsonskills/hooks/README.md
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
Setting up a Claude Code configuration repository
Initializing the shared Claude Code repository