docs(readme): add claude-wrapper to implementations table#26
Merged
Conversation
The implementations table listed every repo in the local-first infrastructure except claude-wrapper, which is the PATH-shim that shadows the real `claude` CLI to inject 1Password secrets and remote- control session names. Adding it for completeness so the architectural split between binary-deployment (claude-wrapper) and directory-tree- deployment (claude-config) is documented. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
claude-wrapperto the "Where the implementations live" table inREADME.md.claudeCLI to inject 1Password secrets, GitHub tokens, and remote-control session names. It deploys differently fromclaude-config(single binary symlinked into~/.local/bin/vs. directory tree symlinked into~/.claude/), so it warrants its own row.Context
Spotted while discussing whether
claude-wrapperandclaude-configshould be merged. They shouldn't — they have distinct deployment shapes and distinct blast radii — but the spec didn't reflect that the wrapper is a sibling implementation. Now it does.Notes
Pre-push codebase review surfaced an unrelated pre-existing issue in
docs/WORKFLOW-DEEP-DIVE.md:310(mislabelsclaude-wrapperas "this repo"), filed as #25 for the burndown tool. Not in scope for this PR.Test plan
markdownlintpasses🤖 Generated with Claude Code